With the one log that was sent me, it appears that the issue could be related to battery devices and reporting. What happens is that the sensors send a wake up to HS, then HS checks to see if any of the sensor devices need to be polled (the polling value is set in the device properties). If so, it then tries to poll the sensor for the values. In the case of some sensors, like the Aeon motion sensor, there are up to 4 devices that need to be polled. If by chance the sensor goes back to sleep, HS will fail attempting to send to the devices and this could take a long time on a big network (30 seconds or so with the default timeout). I can re-create a delay here pretty easily with the Aeon sensor. If you have a Gen 6 sensor, you don't want to poll any of the devices as it has the ability to send updates on its own, fyi.
To test this theory, can you go into the Z-wave config page (click on the plugin name on the plugins page) and disable polling. This will disable all polling when a device wakes up. See if the delays are still there.
I am looking at aborting the wake up processing if the commands start to fail.
To test this theory, can you go into the Z-wave config page (click on the plugin name on the plugins page) and disable polling. This will disable all polling when a device wakes up. See if the delays are still there.
I am looking at aborting the wake up processing if the commands start to fail.
Comment