Homey Down?

Just got a Homey Pro Mini. Worked for about a day, now I can’t load new apps, update the system, and use the cloud to log in. Doesn’t seem like my Homey Pro Mini can connect to the Homey servers?

Anyways, when Homey is trying to update through the iOS app, it always fails with a timeout error.

I looked at my DNS logs and the Homey app is trying to goto ota-api.homeypro.com which when I goto that domain, it says the domain is for sale for $8,595.

Sounds like there is an issue here. Is anyone else able to update their Homey Pro Mini through the iOS app?

UPDATE: forget the part about the domain being down and for sale on ota-api.homeypro.com - I typed in the wrong domain name tld. how embarrassing . . .

Users can’t help when used domains appear to be for sale, please report to Athom Support:

However, it’s odd it did work for a day.
Did you already try to open the app when your phone is connected to mobile data only (wifi = off)?

Are you sure ? It shall be https://ota-api.homeypro.net

2 Likes

holy moly. how embarrassing . . . you are correct, it is .net …. which seems to work.

Any idea on why it won’t update on my side? I get a timeout error when trying to update the system through the iOS app.

and when I try and install any app, it says Homey Offline.

I tried turning off wifi on my phone and connecting through mobile data only and then the app just says it “Cannot connect to Homey Pro Mini”. works fine when I’m on wifi though, and I’m able to control my devices.

Have you tried to power cycle/reboot the Homey?

Have you done anything with your routing/internet/VLANs/Wifi settings in the meantime on your AP/router ?

yes, several times.

The only thing I did on the Homey was set it up, it upgraded to the latest version, I added a thread device and installed HomeKit Controller app. I added a HomeKit light, which only worked for a minute before it would no longer control it, so I decided to try and add my Honeywell thermostats, which I tried to download the app and that’s when I found out I couldn’t download apps anymore. That’s when I tried to update and cloud login as well.

So I figured maybe the device can’t reach just the public internet anymore since I’m able to reach it locally with no problem. So the only real thing I did was install HomeKit Controller before all this started, and wondering if that messed up some network settings, so I uninstalled it. Did a couple of reboots since then and Homey still won’t talk to the outside world.

Was trying to ssh into the box and try find out something from the command line, but it also won’t install the ssh sandbox either. I assume because it can’t reach the internet to download it. Not sure if there is another way in or not.

Think I should just reflash the device and see what happens?

OK, so after a couple of times setting homey back to factory settings, it turns out it was my static ip I put in my DHCP server.

So I had my static IP set to 192.168.1.50 and that’s when Homey Pro Mini was not able to access the internet anymore. I decided to remove the static IP and Homey Pro Mini was now able to access the internet. I set it back to 192.168.1.50 and it failed again. Next, I set it to 192.168.1.81 and everything is still working.

I have NO IDEA what is going on here with my networking setup, and I can’t figure it out. But at least I know Homey Pro Mini now works with the new IP address and I’ll just keep in the back of my head never to use 192.168.1.50 for anything in the future. :rofl:

Just a thought - Typically routers use the first or last 100-ish numbers in your subnet (192.168.1.x) for dynamic assignment to your devices. You often can configure this range the router may use for dynamic assignments. When assigning fixed/reserved IP addresses to devices, you should stay outside of that range. Otherwise you may be assigning a fixed IP address that is already in use/assigned by the router to another device.

Yeah, its really wierd. I have my DHCP range set from 192.168.1.150 - 251.

I have also wondered, like you, that I had already assigned 192.168.1.50 to another device. I don’t have anything in my router settings, but I guess it is possible that I set it manually on another device, but nothing is pinging on that address now.

OK I finally figured it out.

Turns out, on my router, I had ARP Spoofing turned on from a while back. I had binded an old device MAC address to 192.168.1.50 and that was still enabled even though I got rid of that device.

That’s why the router was blocking it since the Homey Pro Mini MAC address didn’t match the one I had in the router config. I deleted the ARP spoofing entry, and tested it out by setting the Homey Pro Mini to 192.168.1.50 address and everything is now working fine.

Thanks everyone for helping me troubleshoot!

1 Like