Since the last update my hp23 reboots every exactly 2 hours.
But only between 6.00 and 24.00
And the time is
1 day 7.00,9.00,11.00 etc
Other day 6.00,8.00,10.00
Today 6.30,8.30
14.30 was a reboot. At 15.50 pulled the plug for reset. But 16.30 another reboot.
Anyone with the same problems since the last update.
Do you have a flow that runs every two hours that uses an app that might cause the issue?
Nothing on a 2 hour timer.
But the strangest to me is that even after a manual reboot. It reboots again after the initial 2 hour scheme.
And why doesn’t it continue in the middle of the night.
When did this issue start?
Did you perhaps transfer from an older Homey to your current Homey Pro 2023, before you updated to the latest firmware? If so, and if you restored a backup, your issue might be similar as mentioned in this post:
You might want to report your issue to Athom, via: Support | Homey.
Really strange, I got HP23 and running latest FW. No automatic reboots. I transferred from a HP19.
I am running Beta FW also, so I do think I have tested similar to the Stable release for some time.
I do suggest the same as @SunBeech proposes, report it to Athom.
It started 5 or 6 days ago after updating to 12.4.2 rc8. But even after updating to stable it continues
@Martin_Sla , I do not experience the same behavior . Have your tried a hard reboot? Pull the power cord, and power it up again. A couple of seconds should be enough.
Edit: I forgot that you stated it in your first post. You should report the behavior to Athom.
I put my house in “sleep” mode and rebooted my internet modem. And for now it doesnt reboot.
If I wake up tomorrow and it starts it reboot sequence. I have to go through all my flows to search for flows that has the if/and everyone sleeps card in it.
I found it.
It was a really old flow from when the hp2016 had poor wifi internet. That rebooted the homey when it didn’t see internet for a amount of time.
Since the last update the http_get cards in logic are broken.
But thanks everyone for confirming it was not a firmware problem.
And just one of my own flow.
Hmm, easy to overlook if you have many flows.
It confirms my thoughts to put logging in my flows or at least annouce what it does through the timeline.
