I’ve been experimenting with my Fibaro motion sensor setup and noticed a delay in light automation that’s been a bit frustrating. Let me walk through what I’ve observed and what I’ve tried to resolve it.
The Setup:
- Motion Sensor: Fibaro FGMS001
- Light: Fibaro Dimmer 2
- Z-Wave Controller: Aeotec Z-Stick 7
- Z-Wave Software: zwavejs2mqtt
- Home Assistant: Installed on a NUC with SSD
The Issue:
When the motion sensor is triggered, there’s a noticeable 2-3 second delay before the light turns on. However, turning the light on/off manually or using the automation to turn it off after 5 minutes works instantly. This inconsistency is puzzling, especially since the distance between the sensor and the controller is minimal, and the system is otherwise responsive.
Troubleshooting Steps:
- Healing Node: I tried healing the node to ensure there were no communication issues.
- Removing and Re-adding the Sensor: I removed the sensor as insecure and re-added it, but the delay persisted.
- Testing Automation Manually: Running the automation manually yielded the same delay, confirming it’s not a trigger-specific issue.
- Component Check: All components are functioning correctly, as verified through the Z-Wave network.
Potential Causes and Questions:
- Is this delay normal for Fibaro motion sensors?
- Could the delay be related to the sensor’s firmware or configuration?
- Are there any settings in zwavejs2mqtt that might affect automation response times?
Seeking Input:
I’d appreciate any insights or suggestions from the community. Have others experienced similar delays with Fibaro sensors? Are there specific settings or configurations that can help reduce or eliminate this delay? Your experiences and advice would be invaluable!
Looking forward to hearing from you all!