It sounds like it hasn’t completed the update of the device, or the device itself is broken.
If you look at the manual for the device, it’ll tell you how to wake it. Battery powered devices can only be contacted when they’re awake, which they’ll do on a schedule (possibly only once a day), but you can manually wake them.
As soon as you wake it, in the Z-Wave control panel in HA (Configuration -> Z-Wave) use the Refresh Node option for that node (you may want to get that all prepared, so you just have to hit the Refresh Node button). Wait a minute then look at the Entities of this node drop down, just underneath.
It mentions holding the z-wave button for 6 seconds and releasing after 8, but I can’t tell whether this will wake the device or ‘abort waking’. But will give it a try.
Reading the manual, you’ve got 8 seconds after manually waking it before it goes back to sleep. You wake it by holding the button for 6 seconds.
That section is simply explaining that if it wakes itself, it stays awake for 10 minutes, except when it is either (2) told to go to sleep, or (1) you trigger a manual wake.
oh ok, great! Where can I see that change? So far I’ve been triggering the sensor (open/close door) and have been checking the OZW logs, seen a Basic report, and thought I was defeated because nothing was changing on my dashboard.
Presumably though I can write some code which triggers something when that change occurs that you’re talking about, but I can’t see where that change occurs.
Even when I open/close the door, these values all stay the same on the dashboard:
(I removed / re-added the zwave gear, hence Node 4 has changed to Node 2)
Hmmmm, are none of the other sensor. values changing either?
Now, that it’s reporting as always “on” suggests that the magnet isn’t close enough to the sensor to trigger the sensor. If you manually place the magnet against the sensor, does it trigger then? If that doesn’t trigger then there’s some form of fault with the device (from a failure of the sensor hardware, to something as stupid as the magnet being installed the wrong way around).
… and on that screen, certainly nothing changes when I trigger the sensor, if that’s where I’m meant to be checking for change.
Re. magnet distance from sensor - I’m yet to install the sensor in the door so this is just triggering it by holding the magnet and sensor together in my hands. I can see from the consequent red lights that the triggering is occurring.
every time I do this triggering (putting the magnet up to the sensor, then removing), it shows up in the OZW logs (as basic report) but I don’t see any trace of change elsewhere.
I don’t know how to check the Report Type setting as such - what I have done is set the Config Parameter to 1 (Sensor Binary Report Toggle), but this yields no change in the OZW logs, and when I trigger the sensor, I get the same as usual (treated as Basic report, as per my last screenshot).
If I sent the Config Parameter to 121, with Config Value = Sensor Binary Report, this DOES yield a change in the OZW logs as follows:
Thanks for the help in discord!
Just to close this off for future viewers, the reason why my Report Type wasn’t changing from Basic to Binary was because I hadn’t woken the device before doing so. I found the manual for the device online, it said I need to hold the button down for 6 seconds to wake the device up for a few minutes, and that did the trick.
@alltherage…
Did you ever get this working with events showing in Hassio?
I have the ZW089 returning binary sensor reports (after setting parameter 121) however the old and new values are always the same?!. I suspect this is the reason why they’re not showing up in Hassio Logbook or History.
E.g. note the old and new values are both true in the second line below:
2017-09-06 13:00:10.924 Info, Node011, Received SensorBinary report: Sensor:54 State=On
2017-09-06 13:00:10.924 Detail, Node011, Refreshed Value: old value=true, new value=true, type=bool
2017-09-06 13:00:10.924 Detail, Node011, Changes to this value are not verified
2017-09-06 13:00:10.924 Detail, Node011, Expected reply and command class was received
2017-09-06 13:00:10.924 Detail, Node011, Message transaction complete
I also tried changing config parameter “1: Sensor Binary Report Toggle” but that changes both new and old values to false…
Thanks for this @alltherage
So in the end I removed the sensor from the door, played with it a bit (and everything worked) and then remounted it to the door frame, and it all seems to work fine now? I don’t know if it was misaligned (hard to see how though)? Either way, thanks for the reply, you inspired me to try further and get it working!
Guys I have spent literally hours and hours trying to get my Aeotec Recessed Door Sensors to work to no avail. Finally stumbled upon this post via a link from another post and now all is working perfectly!
I’m having the same exact problem as you mentioned but I can’t seem to get this to work. I’ve tried everything mentioned here … the sensor won’t get out of sleep mode.
Hi in the end the issue was that I wasn’t having success in changing my sensor to a binary one because my sensor was always asleep when I was trying to implement the change.
I woke the sensor by holding the button on it for 6 seconds, then changed it to binary immediately afterwards and this time it stuck! Basically you need to wake the device before doing anything to it.
I was messing with this for the last 6 hours and between a few threads I was able to get the sensor into a mode that reported many variables rather than one sensor. I think I pressed the tiny button for like 20 seconds, then restarted HA. I also tried setting 121 to 4, or 8. Neither of those worked. Set parameter 121 to 16. With that, the “binary_sensor.aeotec_recessed_door_sensor_gen5_sensor” went from always on to changing with the magnet. Then I could get that info into an if/then/else setup in the configuration.yaml so I could make clean sense of the sensor in Lovelace. Ask if you’ve got questions, but 16 is the answer I found somewhere kind of unrelated. Second post by the taco.
