What happened to the native support for the ecolink zwave motion sensor? It's missing from my hub, which is causing me problems, I must've clicked save on a device, hadn't notice the device type had changed to the aeon device that is first in the list. Of course everything stopped working attached to that motion sensor.
Did I miss that it's deprecated in the notes?
its been gone for some time, it was replaced with the generic zwave motion
I installed a new one on 2018-08-26 14:47:41 CDT, at which time I would've been on 113. It was discovered as Ecolink Z-Wave Motion Sensor
Maybe I'm crazy, but I think it had to have been removed in 114.
Trivial, I guess, the new driver works, I was just surprise
could be, i was looking at the notes in the driver
After seeing this post I checked on my Ecolink's. Just noticed they all have Aeon Home Energy meter assigned to them. I know they had the Ecolink driver before. Hmm. Changing them to generic zwave motion
It doesn't assign it unless you hit save, but since there is no longer a match it just populates the first one in the list.
We'll do a better job in the future about including these in the release notes.
Is the generic driver properly reporting battery status for everyone else?
Yes, mine are.
What model do you have?
I have a mixture of the originals and the plus
I have the Ecolink PIR zwave motion sensor and although it will turn to active when there is motion, it turns to inactive after about 5 seconds. Is this normal behaviour for this sensor? I am also having trouble with it working with my Motion Lighting app. It will sometimes trigger the lights to come on but they will not go off when it is inactive.
If you have the jumper on the test setting, I believe it is 15 seconds to reset. It sounds like you might have a problem with your smart app logic, if you see the motion going inactive in the driver properties screen.
Can you post a picture or details on which smart app you're using and how you have it configured to turn on and off the lights based on this motion.
These are slowest to re-trigger sensors I have. Mine are 2 years old and take 4 to 5 minutes to go inactive. My Fibaros and Aeotecs will re-trigger in 15 to 30 seconds.
Not exactly true. Open it up and put the jumper on the test prongs.
Here is the Motion Lighting App that I am using. I am just starting with simple things to see how things go.
Try disabling the delay off per mode setting and moving those off settings to Additional Sensors, Lights-Off and Off options.
Ya unfortunately it does disable pet detection. I wish those settings were separately configurable, I think that's an oversight.
There is a jumper on both Test and PET1. @doug I changed the app to what you have and the lights still don't turn off.
Duel jumpers? Is pet setting working in conjunction with the 5 second reset?
Can you affect the lights via their property page? Turn them on and off digitally I mean?
Otherwise, I haven't a clue, probably should contact support and see what they can dig up.
Download the Hubitat app
