I can't be 100% certain that nightlyCleanupJob is responsible but this always starts somewhere after 2:00 AM and continues until a bit after 3:00 AM and nightlyCleanupJob is set to run at 2:15 AM so it is the smoking gun.
Every night for most of an hour my hub isn't dealing with ZWave devices in any sort of reasonable time period. It can sometimes take 2 minutes for it to actually trigger a zwave device from the time it was switched on the dashboard (or directly from the device page). The worst part is it stores up all the requests and triggers them later. (I finally had time tonight to confirm that Zigbee devices weren't affected.)
- This is actually a safety concern: There are multiple devices controlled with zwave momentary switches like the main access gate, garage doors, etc. A momentary switch is always activated to ON so multiple queued key presses is like pressing the gate/garage button at random. I've had the gate try to close on us as we go through it. I've come home to find the gate partially open. Plus the access lights are on zwave switches and backing into a long driveway under a huge oak tree at night is like backing into a blackhole.
This may have been happening for a long time but in the last year I've been having to go pickup my wife in the early morning hours and it is very often during this time period.
My zwave mesh is setup so there are no devices that require multiple hops to be reached. Any devices that would need to go through a repeater are on a different hub. The momentary switches for the gate and garages are 12 feet from the hub with nothing to interfere with radio between them.
What can be done to troubleshoot or chase down what is causing this? I'm surprised I couldn't find a way to list what commands are waiting in queue. I was also very surprised that I couldn't find any posts referencing "nightlyCleanupJob" except a single one that included it in a list of every scheduled job in the hub.
This has to be fixed or I'll have to scrap this system.
