Homey Pro 2019 not connecting

My Homey Pro 2019 is not connecting to homey services and app.
For some weeks I have not been able to connect to my Homey Pro 2019 via the App on my wifi or via my.homey.app.

Automations are running so the Homey has been functioning in that way. Just unable to connect in any way. Today I followed the instructions in the q&a section of the homey website. Turned the homey upside down and tried to add it as new in the app. It goes until I can select the wifi and password, after that the app stops and says it cannot connect to the wifi.
I can see that it connect to the network, first on Ip like 10.199.189.1 then on an DHCP-assigned IP.
But still no go.

Tried using my phone as a hotspot, the same result. Can see homey as a client but no connection.

The ring starts spinning blue after putting in the wifi and password, then after some time it starts pulsating yellow again.

Any ideas from the community on how to get out of this loop. Really missing a physical reset button..

After trying the “Add new Homey” and restarting the Homey. It connect to the network, network reports Good signal strength, but still no app och my.homey.app.

Consistant a couple of Kbps traffic up and down according to router.

What happens if you connect to it through its IP address from a regular browser? If you see something like {"homeyId":"XXX","homeyVersion":"12.5.0"}, then the issue is not with your Homey but with the convoluted way of letting apps connect to Homey (which is an issue that has existed for many years and Athom apparently doesn’t know how to fix).

Does your internet router have a feature called “DNS rebinding protection”? If so, try either disabling it or (better, but not always possible) make an exception for the homeylocal.com domain.

Also, if you use something like PiHole or Adguard in your home network, the Homey apps might have issues with these.

1 Like

He used his phone as a hotspot, so you can probably rule out router, network or ISP related issues…

The homey does not respond to requests via http, or https on the IP.

This is very strange, by the way. Homey only works with DHCP so it cannot assign itself an IP-address until it receives one over DHCP. It’s also strange that it uses a .1 address, as that’s typically reserved for gateways.

Assuming you don’t have separate networks (VLAN, IoT, guest, etc) or services (PiHole, Adguard) that might be causing this, it’s beginning to sound like a hardware issue.

Have you tried a different power supply and cable?

Today it suddenly after another round of re-start started to work for a while again. Let’s see what happens going forward.

Yes, it was a strange IP that was assigned, but that what I could see in by ubiquity network tool. I have assigned as static assignment in the DHCP so that it get the same IP-address every time it connects.
I do a different VLAN for my IOT devices such as the Homey, have had the same setup for a long time. The only thing I now changed was that I added a A record in my local DNS for homeylocal.com to the staticly assigned IP-address of the homey.

Let’s see what happens.