I’ve been diving into the world of smart lighting and automation with Philips Hue Motion Sensors paired with a ConBee II stick on my Raspberry Pi 4 running Home Assistant and Node-RED. It’s been an exciting journey, but I’ve hit a snag that I’m eager to overcome. The sensors are supposed to detect motion almost instantly, turning on the lights as we enter a room, but instead, there’s a frustrating 1-2 second delay. This might seem minor, but in a space as large as mine—with almost 50 Hue downlights acting as routers—it’s noticeable enough to be a nuisance.
I’ve spent hours troubleshooting, considering every angle. Could it be the sensors themselves waking up from sleep mode? Or perhaps something with the Zigbee network quality? The ConBee is connected via an USB extension cable, placed high up and away from other hardware, so physical placement shouldn’t be an issue. All devices show green neighbor lines in deCONZ, indicating good network health. I’ve also timed my Node-RED automations, and they’re clean with no added delay there. So, the culprit must lie elsewhere.
I’ve heard that sometimes the firmware or configuration settings can play a role. Maybe a tweak in deCONZ or Home Assistant could help. I’m also considering if the Raspberry Pi’s processing power is a limiting factor compared to a more robust system. Upgrading to an Intel NUC might be a future solution, but I’d prefer to optimize what I have first.
If anyone out there has faced and conquered this delay, I’d love to hear your strategies. Have you adjusted any settings in deCONZ or Home Assistant? Did firmware updates make a difference? Any insights would be invaluable as I continue this quest for seamless automation. Let’s keep the conversation going and help each other refine our smart homes!