Ok, received a brand new C-8. Did a cloud restore from my old C-8 (first resetting the Zwave/Zigbee radios). The restore finished and it seems like my ZWave devices are working as expected on the new HE. Old HE is unplugged. Impressed that worked.
However,
Still NO schedules are working. I made a fresh rule to trigger in 10 minutes. 10 minutes went by and didn't trigger.
I guess I have to either start completely over or switch to another platform. No clue why HE is such trash. It must be something within my config/backup.
That's odd, never seen that happen following a migration/restore. I have seen schedules not working due to a database corruption, but that is very rare. Could you please run a Soft Reset when you have a chance? Also, please send me the MAC address so we can check the engineering logs after the hub is back online.
FYI ALL - BobbyD solved my problem. There was a hung job - invisible to the UI. All the soft resets, restores, etc. in the world wouldn't have fixed the problem. The job was hung for about a year. BobbyD tells me job status will be added in future releases. No other way to see it.
Once cleared out, everything started working again.
The end points to remove a bad schedule that otherwise may prevent the scheduler to start have been introduced in 2.3.4 release. However rare this may be, the hung schedule for the app or driver is not easily identifiable by the user, so our engineers will add a warning in the log (past logs) to indicate which app/driver may have a bad schedule so that the user can take the corrective action of removing it, without the need to reach out to us.
It seems to me that a more obvious warning should be given. How about using the Alert area to also alert someone? Could it be made a hub setting that could be exposed by this app by @thebearmay ?
