When I go into developer (https://tools.developer.homey.app/) and when I then go to Zigbee, Z-Wave, Setting or whatever, I get the errors like in the screenshots.
At that moment Homey is actually off-line. After a minute or two it’s back on-line.
I have the Pro 2019 with firmware 7.3.0., running 24 apps.
I have short offline times when Homey consumes too much memory. Then Homey is getting really slow and it seems he’s offline. But I’m sure he’s only too busy to answer.
Please check the memory consumption in the settinge. If the memory is full, restart Homey and keep an eye on the memory if the offline situation appears again.
Another cause could be the router.
I had problems in the past with Asus Lyra mesh. Homey tried to connect to another AP and got lost because it was too far away.
Where can I find memory consumption? If I select any of the Tools selections, I get the off-line error.
After waiting a while I try again it immediately the error pops up again.
In the Mobile App under settings - but only if you can con ect to Homey.
If that’s not possible, you could restart (PTP) and check the insights. There is a chart for the system momory usage.
That’s the Netgear mesh, right? I had some Asus Lyra as mesh router. Well, it was a first step to a mesh, but not very stable. I switched to Unifi and it’s much more stable.
WiFi could be one problem. Some ideas…
From my experiences with Asus Lyra:
Check if Homey is jumoing between the APs. Check in the routers client list if Homey is connected to an access point far away when he is not reachable.
The Lyras sometimes disconnected from the main Lyra router. (I used a Wifi mesh) This way clients connected to it were connected to its WiFi, but without internet or LAN access.
General things to check:
use a fixed WiFi channel (1, 6 or 11).
deactivate step by step some Wifi optimizations like band steering, fast roaming or similar things.
check if you can assign Homey to a fixed access point, so Netgear doesn’t use roaming for it.
So far some ideas. Good luck with your tests. It’s all about try&error.
I started with the simpelest step first. I replaced the power adapter with 2,4A one. That solved the off-line thing.
Now I only keep getting the ‘Object’ error. Everything functions normal, as far as can see.
Any thoughts?
It happens with any of the items under ‘Tools’.
Oh, and the off-line error is back again. Half a minute later or so, it’s back on-line.
The one below is comming up again too but I cannot find anything not working.
I will check the wifi settings, though I have not changed anything recently.
I didn’t add any devices recently so I will do the factory reset I think. I have the daily back-up thing from Athom. Does that mean I will not have to add all devices and flows? Will they all be installed again automatically?
I made a little mistake, you don’t have to do a factory reset prior to a full software download.
That shouldn’t affect anything of your devices, flows etc.
If that doesn’t help, you need to restore a backup when you’re going to perform a factory reset.
Almost everything is getting restored, apart from community store apps, apps you installed via CLI, and probably apps which aren’t available in the app store any longer.
This problem seems to remain unaddressed. I have tried most of the very reasonable suggestions above (permanent ip, separated 2.4/5ghz and alternative power adapter). The latter especially fixed a lot of stability issues so thanks for stressing this across posts in the forums, but it did not fix the issue discussed in this thread. This bug particularly seems to appear when I enter the z-wave network under developer tools and switch over to zigbee and quickly interchange between the two. May it be related to how homey deals (or not deals) with sleeping battery-based z-wave units? My zigbee net is large, but stable, and the z-wave one is rather small and consists of mainly router units (Fibaro plugs), but also three Fibaro battery-based sensors which regularly ‘sleep’. Hope Athom could prioritize this as it will also carry over to the new homey if left unattended. I do not have a Netgear router, but a Linksys 1900 ACS.
The same problem here still…so Athom have not resolved it yet, after nearly a year.
I wonder if it can be OS related? I’m using an old MacBook Pro running on High Sierra and Firefox. Safari 13 is now unsupported by the forum so it looks really old school.