Homey pro 26 goes offline most nights

Most nights arround 9:30pm Aust EST, Homey goes offline.

The LED ring is still rainbow. It is connected via the ethernet power cable. It has been stable for weeks. My router app shows it is offline and I cannot get it back online via this app. The only way to fix is by disconecting power for 30 seconds then reconnecting. The firmware and software are up to date.

Any help greatly appriciated.

Thanks in advance.

Jeff

Is it always around the same time? Maybe some device (f.e. your router) is running automatic updates and Homey somehow doesn’t reconnect properly? When Homey goes offline, can you still access other devices in your network?

Not the exact same time, but close. Nothing else is dropping off and I can’t see any thing running on the router.

Have you also tried disconnecting only the Ethernet cable for 30 seconds when it drops offline?

No, I have not tried that. I will give it a go next dropout.

What will that prove? If it comes back, how can I fix it permenantly.

Thanks

Jeff

Another check (if you did not do that already) could be to have a look via the Insight monitoring if you see any drops or spikes in the Memory or CPU of the device around that time.
You could also check if any app is having spikes around that time there as well.

Perhaps that can give a clue what is going on.

Do you have multiple activities at 21:30 that were started simultaneously by flows?

No. No flows at all around the time.

Do you have a cloud backup subscription? If so, have you enabled automatic backups? If so, have you checked what time the automatic backups are created?

In order for backups to be created, a certain amount of free storage space must be available. If there isn’t enough free storage space, problems may occur during a backup.

No cloud backup. I am intending on doing the manual backups to a laptop.

Checked the insight, no clues everything looks very stable.

9:36 went offline again. Tried disconnecting the Ethernet cable for 30 seconds, did nothing. Took numerous long power offs to get it back online tonight.

Still a mystery. Very open to any further ideas on what could be causing this.

Thanks in advance.

Jeff

Just a thought (not that likely): could it be that the IP lease of your Homey (assigned by your router) expires after a day, but is not properly refreshed, causing the Homey to lose its IP?

Not sure whether you have assigned/reserved a fixed IP in your router’s DHCP server for your Homey. If not, you might want to try that and restart your Homey after making that reservation.

Thanks, but I have Homey on an assigned IP.

Hi all,

Homey support got back to me with the solution. My logs showed a heap of apps were all trying to update at the same time. 9:30 Australia time.

I realized I didn’t use all the apps so got rid of half of them and no crash tonight.

Thank you to everyone that tried to help and Homey support.

Experiencing frequent overnight disconnects (matches the pattern in this thread). Made recent network changes that seemed to fix it — dedicated 5GHz channel, DHCP-reserved static IP, and AP lock — and it was stable for a bit, but the disconnects came back.

This morning I tried a full power cycle to recover it. On boot the LED ring goes red (breathing), then transitions normally to rainbow — but it stays offline afterward, both in-app and on the network. Not even a cold boot brings it back online.

Wondering if this is a known issue with 13.3.0 specifically, or if anyone’s found a fix beyond repeated power cycling. Happy to share router/AP logs if useful.

Did you try this?

Source: What the LED Ring animations on Homey Pro mean.

Homey support fixed my issue. From my logs they noticed about 6 apps all at 9:30pm trying to update.
I deleted 3 and have not had the problem again.

It’s Homey itself that schedules and performs app updates, so basically they’re saying that Homey is broken?

Thank for the tip. Tried it but didn’t work unfortunately.
In setup mode it wants to connect to a wifi network but it can’t do so any more. (keeps asking if the pw is correct eventhough it is…)