- Platform information:
- Hardware: Raspberry Pi 3
- OS: Raspbian
- Java Runtime Environment: which java platform is used and what version
- openHAB version: 2.4.0
I’ve recently set up an Aeotec Multisensor 6 on battery power, via an Aeotec Z-Stick, and want to use it as a motion sensor to trigger (Philips Hue) lights.
So far I’m a little disappointed by the delay between motion happening and the lights coming on. I get that it’s doing a lot (detect motion, inform controller, inform OpenHAB, trigger rule, send command to Hue Bridge, turn on lights), and it’s pretty mindblowing that it works as quickly as it does, BUT, it’s so much slower than my existing Philips Hue motion sensors that I’m hoping there’s some configuration or something that I can change to make it snappier. As it is, I’ve usually traversed the area I want to be lit before the lights actually come on!
When I walk towards it, there seems to be a variable delay (up to say 5 seconds) before I see the green LED come on. I assume that the green LED is telling me that it’s detected motion and is sending the ‘MotionAlarm = ON’, after seeing the LED, the lights come on pretty much instantly, so I assume that the majority of the delay is in the sensor.
I guess my main question is - is there any way to make the sensor detect motion more quickly? It’s currently battery-powered, but I wouldn’t rule out using mains power if that’s the issue. I’d prefer to stick with batteries if possible though (and I don’t see why it wouldn’t be possible, as the battery-powered Hue motion sensors I have work fine, and their batteries are still reporting 100% after several months).
Alternatively any tips and tricks from others with a similar setup would be appreciated. My goal is for the lights to come on as soon as possible when I walk into the area covered by the sensor.