I’ve been experimenting with integrating my Fibaro motion sensor into Home Assistant to automate my desk lamp. The setup seems straightforward: detect motion and turn on the light. However, I’ve noticed a significant delay in the response time—anywhere from 2 to 10 seconds. At times, the automation doesn’t trigger at all, leaving the lamp off even when motion is detected. This is quite frustrating, especially since the motion sensor itself reacts almost instantly, as indicated by its LED light.
I’ve already adjusted the sensitivity settings to the maximum and reduced the number of pulses required to trigger the sensor, but this hasn’t resolved the issue. From the logs, it appears that the system processes the motion detection within 1-2 seconds, but there are cases where the delay is much longer or the trigger fails completely. My apartment is relatively small, and all devices are within a 72m² area, so I assumed the Z-Wave network would be robust. However, it seems like there might be some latency or interference affecting the automation.
I’ve also checked the Raspberry Pi’s performance, and it doesn’t seem to be under any significant load, so that shouldn’t be the bottleneck. The USB Z-Wave controller is functioning correctly, but I’m considering checking the signal strength of the Z-Wave network to ensure there are no communication issues.
Has anyone else experienced similar delays with Z-Wave devices? Are there any best practices or troubleshooting steps I can follow to optimize the response time? I’d love to hear from anyone who has successfully resolved similar issues or has insights into how Z-Wave latency can be minimized in a small setup like mine. Thanks in advance for your help!