Here’s my sensor. I found that the sensative strips sometimes report 255. Never got a good answer from the company on why they report 255. So here’s my workaround.
friendly_name: Family Room Door
value_template: >-
{% if is_state("sensor.doorsensor_access_control_16_9", "22") %}
open
{% else %}
closed
{% endif %}Like many Z Wave devices, they come in Basic mode by default. You’ll need to switch them to Binary to get the binary device operating. You do that by waking them up, then setting parameter 112 to 0 (it’s more obvious to do using ozwcp, but it’s just as achievable using the HA dashboard).
Alternatively, @homehacker’s solution works if you leave it in basic mode - that’s how I left it for my initial setup.
I think I might have also left them in Basic mode so I can query the sensors and get their battery status.
Binary mode still reports the battery level for me:
battery_level: 100
I’m using your above example with a binary sensor value template, but it only displays as ‘off’, however using the templates developer tool it displays the expected string.
Here’s the exact entry in my sensors.yaml file.
- platform: template
sensors:
door_16:
friendly_name: Family Room Door
value_template: >-
{% if is_state("sensor.doorsensor_access_control_16_9", "22") %}
open
{% else %}
closed
{% endif %}
Also, if you look in the developer’s “states” window, you should see (in my case), sensor_door_16 closed.
As sensor or binary_sensor?
As binary_sensor.doorsensor_sensor_16_0
I had to do it this way:
sensor: # binary_sensor did not work
- platform: template
sensors:
door_entrance:
value_template: >
{% if is_state("sensor.sensative_strips_access_control_13_9", "22") %}
open
{% else %}
closed
{% endif %}Correct. In configuration.yaml you need to specify sensor as you have. I created a separate sensors.yaml file, which is why you don’t see in the first line, “sensor:” in my example above.
I had/have this exact same situation (except my Strips reports 254 - are you sure it was 255?) not only with this sensor, but with Fibaro FGK-101 as well. I got an answer from Sensative - thread also contains more information about when the value changes in my case.
Note that if you are using access_control, using the logic if 22 → open, else closed the “closed” rule also covers value 255 so the door might be open and HA shows it as closed. Same thing if you restart HA, you can’t know the door state before it is first opened/closed.
Sorry, it probably reported 254, just my mistake.
There could very well be an issue when HA restarts, I just haven’t seen it yet.
Hi !
@Tinkerer, what’s your method to switch your sensor to Binary ?
How do you do to set parameter form 112 to 0 ?
thank you !!
As you said, by setting parameter 112 to 0 
Two ways to do that, you can use the OZW control panel, or from within HA itself. From within HA you use the Services menu, select zwave and then set_config_parameter. Then you enter the following, changing the node ID from 99 to the ID of your own strip.
{
"node_id": 99,
"parameter": 112,
"value": 0,
"size": 1
}Mine was only showing up in the dev-state menu as zwave.__3 and the zwcfg*.xml file in .homeassistant had an entry for node 3, but it was basically generic blank info. I woke the sensor quite a few times before it showed up correctly in the openzwave control panel. I switched it to binary sensor as described above and hit save. After several restarts and waking it several more times and verifying that it had been saved in openzwave control panel as a binary sensor, I replaced the info for node 3 in the .homeassistant/zwcfg*.xml file with the info for node 3 from the open-zwave-controlpanel/zwcfg*.xml file. My HA now includes 7 entries including the binary sensor I want to see, but…
Now the strip is blinking 5 times to indicate it’s not connecting. In openzwave control panel I no longer see anything in the log when I wake the sensor. I’ve put 7 hours into this and I’ve hit a point where I have no clue what to try next, lol! Node 2 is an Ecolink Garage Door Tilt sensor and it’s still working, fwiw.
When you added it using OZWCP, you wake it up until the Manufacturer name correctly shows up in OZWCP. That is when you are done. After you are done, you would need to either have a symbolic link linking the zwcfg*.xml file from the OpenZwave directory to the /home/homeassistant/.homeassistant/ directory or copy the file from the OZWCP directory to the /home/homeassistant/.homeassistant/ directory so that the file stays in sync between OpenZwave and HA and so that you don’t have to edit the file manually. You would then be able to rename devices to understandable names and locations in OpenZwave, click on Save stop OZWCP, start HA and then your names would show up…
Thanks! For anyone finding this in the future… I had to remove the Strip from the Z stick, reset the strip, and add it again to the Z stick (all a couple times) along with copying that file but it’s all working now as node 5 instead of node 3. Once I got the manufacturer to display in openzwave control panel I did also switch it to a binary sensor and then hit save. Threads on this sensor sure make it look like the binary sensor setting in openzwave is easier to deal with. I had to wake the node 2 sensor because I somehow removed the info for it in the process. When both sensors showed up correctly I hit save and then copied that ozwcp*.xml file to /.homeassistant and everything is showing up in the front end and working properly.
Hi Veggie,
I installed my Sensative Strip a couple of days ago as well. It was not easy (had to reset it twice - and the strip reset method definitely does not work), but it is finally working.
I tried to switch to binary senor (within OZWCP) which again led to the Strip reporting faulty connection to the Zwave USB Stick. After a final reset, I left it to sensor (not binary sensor) and it is working without an issue.
For the others, the best way the include it or exclude it in OZWCP is to use the command of the stick and use the wake-up procedure from the strip immediately thereafter.
Mine only worked for a day and now the last couple days it only reports correctly intermittently and sometimes gives the 5 blinks. I thought Tinkerer was saying that using the drop down menu in OZWCP to change it to a binary sensor would be the same as set_config_parameter, but it looks like you’re saying I should start over and leave it as default settings in OZWCP, instead changing settings in HA.
Questions:
set_config_parameter looks like the best solution…
set parameter 112 like Tinkerer above Why isn't Sensative Strip Appearing? ?
or
parameter 1 like larstobi here Door sensors change state by themselves ?
To clarify, does “use the command of the stick and use the wake-up procedure from the strip immediately thereafter” just mean remove the the zstick and long press two seconds to get the orange blinks in order to exclude and or tap in order to get the blue blinks for inclusion? (then obviously do the round magnet on top of round end three times to wake the Strip) or are you using OZWCP for that?
Hi,
There is no configuration parameter no. “112” as far as I can read in the manual. If you want binary_reporting, you should probably follow the instructions from the user manual, which specifies parameter no. 1.
To answer your 2nd question (the 5 blinks) indicate from reading the manual that there is a communications problem:
5 short: Error. ex. communication with controller failed
This could mean that there is no range. Have you placed the strip on a metal frame? Is it too far to the next mains powered z-wave device (acting as mesh repeater)?
Hope that helps! 
Update: Also, about the OZWCP vs HA configuration, I have had problems with the security key when switching between OZWCP and HA, so I prefer to do all my configuration from within HA. You mileage may vary.