This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed
Homey doesn't want to connect to Airport Extreme
Just received my Homey, tried to connect it to my Airport Extreme with WPA2 but somehow it doesn't want to connect. After a couple of reboots (power on/off) the Homey still says how to setup but connecting to the HomeySetup wifi isn't possible anymore (still available but can't join). Any tricks on howto do a full reset or force it to connect to the wifi via a CLI?
This discussion has been closed.
Comments
My former Netgear AP had the ability to give each network/Ghz mode its own name.
I named them;
- MarcoF24Ghz
- MarcoF5Ghz
Worked greatI'm experiencing issue now after it connected to my network it started to update and then restarted, now it will not come online and I cannot get it into recovery.
Setup proofs to be a real pain in the ass if you ask me. @Emile a hardware recovery / reset button would be really usefull.
When I put Homey upside down to fast after powering on the led ling becomes purple (downloading update?) and stays that way until I pull the plug. If I wait a little bit longer the led ring keeps spinning orange and eventually will turn solid red.
Is there asnyone out there that received a Homey today and that was able to connect it to WiFi?
If your Homey is turning red after plugging it in, you have bricked your homey. This could be caused by unplugging Homey while it was installing an update. If this is the case, you'll need to contact support at support@athom.com for further assistance.
(Aruba Instant, iap-105's, single ssid for both bands, band steering prefer 5 Ghz, minimal transmit rate 24Mbps on both bands)
Disabled band steering, beamforming & 5Ghz alltogether leaving 2.4Ghz only. Didn't help....
EDIT:
After a few more attempts, my homey got connected
I set up a hotspot on my cellphone (Motorola Moto G 2015) with SSID homey, password 10 charactters lowecase, letters only. With that hotspot, setup worked.It is now updating (purple ring), so the result of it all is still unknown :-)
For troubleshooting purposes, the things i can think of are the following:
1. DNS. In my network, the central DNS server (dnsmasq) uses OpenDNS as the upstream DNS servers. I don't use the Ziggo DNS servers.
2. I use pihole for adblocking centrally on my network (dnsmasq-kind-of-hostsfile-setup)
3. I use a number of bloclists blocking access to known malware hosts, C*C servers, et cetera. If necessary, i can post the sources i se to create the central blocklist.
Wild guess: options 2 and 3 are specific to my situation. Which leaves the question: anyone else using OpenDNS and having issues setting up WiFi with the homey?
Edit: I use the DNS servers provided by my provider (UPC/Ziggo). So it's probably unrelated to this issue.
Edit 2: Up and running on Android AP. Now looking for a way to switch to regular wifi network.
Android AP is working, iOS not.
After successful connection and setup, i shut down the AP on the android phone and powered up my regular network.
Then, i waited a while (5 minutes or so) to see if the homey would automatically detect that the network was gone so it could reconnect. It didn't. Finally, i unplugged the homey and plugged it back in. It boots up fine but as you may have guessed: the my.athom.com page (opened in a new tab on Chrome) shows that my homey is offline.
What's interesting is that the 'old' tab that previously showed my.athom.com now shows the following URL: http://192.168.43.181/manager/zones/
That ip i cannot ping from my home network. Which is normal, because it is a IETF-RESERVED-ADDRESS-BLOCK.
Do any of you guys block access to DNS servers other than your own on your router/firewall? I do, and when disabling this firewall rule my homey suddenly connects. It appears the homey has a dns resolver hard-coded in the software somewhere. Or not, let's re-enable the rule and take a look at the logs :-)
See for yourself. The source IP 10.0.0.8 is the static IP of the homey:
Have reset the homey and re-ran the installation procedure. Both times it said it couldn't connect to the wifi network (voice), but in fact, it did. Both tomes the ring turned to 'rainbow' (which in my account is the setting) after waiting some more. And in the app, the homey turns up as online.
So basically, for users of homey the solution is roughly as follows, as it appears: If you block google DNS, unblock it for homey to work. If you don't actively block google DNS, wait a little while (max 5 minutes or so) before giving up after the devices tells you it cannot connect to your wifi network.
For the homey developers: please remove the hard-coded DNS servers from your source code and let the default DNS servers on the customer's network do the resolving. It's simply not done to force your device to use hardcoded DNS servers (or any hardcoded ip's for that matter), but you can certainly not force your customers to use Google's data-mining DNS servers. Privacy is a thing in 2016....