I have been using this sensor this way with ST and no problems. I never looked at it before because I wasn't having any problems. I can turn the lights on using their property page. for some reason this Motion Lighting will not turn the lights off. I might try a Webcore piston to see if they turn off that way. BTW, I have contacted support about this and they were looking into it but I haven't heard from them in a couple of days.
No problems, sure, but does it help with pet detection?
I'm no longer using Motion Lighting, but I tried it out when it first came out. It was pretty reliable, but I did have a few issues here or there such as what you're mentioning. One more thing you could watch, check out the subscriptions and scheduled events.
On the App List page, find the blue i (info) icon to the far right of the application in the list and click it.
Then look for your motion sensors and make sure there are subscriptions to the inactive events.
At the bottom of the page, if the motion sensor has gone inactive and you expect an event in two or so minutes it'll be listed under scheduled jobs.
From what I heard, support has found some logs that indicate the problem lies with the bulb driver, not the app or the ecolink. hope you can find resolution.
Thanks! Bobby from support is looking at it now. Looks like there are never any Scheduled Jobs. BTW. my webcore piston worked fine and the lights turned on with motion and off when motion stopped.
1 Like
The generic driver for my ecolink motion detectors always reports 100% for battery status. I don’t think it’s actually working. However, everything else with the sensor works fine. Is there a way to fix the battery status reporting?
Agree, I've been keeping an eye on this for some time. The battery reporting no longer seems to work with these. Can that be fixed in the generic driver or maybe go back to the built in specific driver?
Same on battery status. I brought this up last year but it wasn’t a priority. Maybe @mike.maxwell can take a second look.
