I have a couple of sensative strips that I have used with the old zwave integration without issues. However, with zwave JS they always appear sleeping. I have tried changing to binary report with no luck.
I have even tried adding brand new strips. The add just fine but do not report open/close and are always in sleep state.
Any input?
I have the exact problem. It always reports a closed position, and always seem to be asleep. Anyone knows of a fix for this?
Maybe some routing issue in the Z-Wave network? Seems like a frequent issue:
mine show open/close only if I’m close enough to the z-wave dongle.
(when you say “asleep”, is that an “official” state I can check somewhere in the logs/setting, or just a description of the situation?)
Hi all,
Any updates on this? Anybody got it to work?
thank you
I have a couple, they work without issues on zwavejs.
Of course they spend 99.9% of their time asleep, like all battery powered zwave nodes, but that’s perfectly normal:
They wake up every 24h for about one second to report in:
They do report their open / close state (binary sensor) immediately. They stay asleep during that time, which is normal behavior. I did not notice any range difference on them between zwavejs and ozw 1.4 I was using before.
Thx HeylmAlex for your input, I kept on searching. In case anybody finds it helpfull, here is my solution
Zwave JS changed the binary sensor to sth like binary_sensor.strips_mazw_access_control_window_door_is_open_…
so my old namings did not change their state in the UI
Strange that the UI did not give an entity_not_found error. It wrongly made me assume that they were working just fine
Hello, I’m trying to use Sensitive Strip but they stay always asleep and I don’t know hot to correct this. Can you help me?
#sensative #third-party #configuration
Thanks, can I ask you if your sensative strips connects directly to your z-wave dongle, or to other z-wave devices? my issue is that they don’t seem to want to connect to (closer) z-wave repeaters (fibaro dimmers in my case), but only want to connect to the main dongle, which is however too far away…
They’re directly connected to the dongle without repeaters in between.
hey there, thanks for the info. I noticed too that the sensor now created a binary_sensor like you stated: binary_sensor.strips_mazw_access_control_window_door_is_open_
I am also struggling with the Sensative Strips, my setup is as following:
I could pair the Strips directly to the Aeotec Stick but they are always asleep (even when I move the magnet to rounded edge, simulating that a door is being closed). they are also correctly reported to Home Assistant.
I tried the following things:
Nothing helped. I wonder if it is an issue with the Z-Wave plugin somehow or the Strips itself. Has anyone the same setup and success using them?
You need to change the notification type to “[1] Notification report (Default)”. Afterwards wake up the strip and it will report the state correctly.
If you want to stay with your current configuration you’ll need to activate the “Any”-entity of the sensor on Home Assistant. This will show the window’s state as a binary sensor. Where true equals closed and false means opened
oh yeah, that did the trick! you made my day 
Any suggestions for waking the strips? I have tried following https://sensative.com/article/strips-guard-700-for-z-wave-manual/ and https://sensative.com/article/how-to-manually-wake-up-strips/ but nothing works. They just stay asleep. I want to wake the strip in order to change config to binary mode.
Lovely product when it works but they are an absolute pain to work with. They should have made the device 1 cm longer and included a recessed pressure sensitive area to manipulate inclusion, exclusion, reset and configs.
