I noticed lately I get delayed automations especially when it comes to light with motion detection where sometimes light won't turn on for 4 or 5 seconds or even longer after motion is detected. This usually happen when hub has been on for few days
Rebooting hub or power cycling it fixes the issue and automation becomes instant
Is there a way to schedule reboot of the hub like sometimes during the night or something
I appreciate your assistance
You should not have to, and it's not recommended. It's better to find the issue. But if you want to, you can do it like this with a switch and @ogiewon HTTP as switch. There's other ways to do it in RM too. I was using this for a short time, but I found and fixed my issue so it's disabled.
what could be the issue? network or what? I'm not sure how to troubleshoot
Disable custom code to start. No need to uninstall. Disable is instant and easy. From there you can re-enable to see when the issue occurs. Yes this can take a while. Sometimes weeks. Better than living with the issue and rebooting.
How to disable is at the bottom of each doc.
Look also for orphaned Zigbee devices you no longer have paired with HE, and if there are any, delete them and give the hub an overnight database cleanup.
If you find orphans in the Z-Wave devices list, exclude those devices if they are available.
Also have a look at scene transitions. Too many transitions or too many light bulbs transitioning at once slowed down my Hub to a halt...
Check your system events. It will show when the hub rebooted
I'd like to also suggest that after you do a reboot, you "turn off" the zwave radio for a few minutes. (Post "disabled", to the zwave settings page.)
(Thank you: @SmartHomePrimer )
I don't see any reboot event on system events, something is wrong I believe in the rule
how do you accomplish that inside the rule?
You forgot the port 8080
As part of the Action of a rule, the following command executes a reboot (after a 5 minute delay):