That was interesting to read that there had been some updates to the binding of this device as well.
I installed one of these just about the same time that you guys were discussing that setting the door sensor parameter to Binary would work. That helped me getting this thing working back then.
Today I’m installing a new one and when I did like the previous time set the parameter to send binary and then set up a switch for the channel, the door didn’t work. (The channel had even suggested creating a contact but I manually chose a switch instead )
Anyhow just before I got to this thread. I was doing trial and error and ended up with the parameter as Send notification and the item type as Contact. Now the door started to respond.
Then I got to reading this whole thread once more including your newer posts in it.
Right now what I did was also delete for my previous door sensor, I deleted the items, the thing and the xml file.
And now I’m waiting for it get fully initialized again. I hope it wasn’t a misstake to delete it, since it sits on a door fairly far from the controller. (not within the specified 1meter which is good for initializing this device).
I’m going to try to get it into the Send notfication mode like it should be. Although it has worked the whole time before.
I’ll report back here with how it goes. Always good to have this info on record for others who come later I guess.
Btw, I’ve too been thinking about these General Alarm channels. What are they good for? Maybe I should look for a seperate topic on that.
Got it working now.
So in order to move from a Binary switch over to a Door Contact I had to do the following steps.
Delete the Items
Delete the Thing
Delete the xml file
Power down the Openhab solution
Move the controller within 1 meter of the door where the Door Sensor i sat on
Start up openhab
Set the controller to Include mode and add the node
Wake it up a few times until fully initialized
Change the Parameter to “Notification report”
Wake it up again for it to take affect
Create new items (this time it should be a Door Contact)
12 Test that its working. Now I could power down and move back the controller to its usual location
I’m running on a Rpi. Thinking about getting a PiJuice when they become available again. It would be nice to be able to move around the controller for times like this.
Hi all.
I don’t know if this is the right place to ask, but since all expertise in Sensative seems to be gathered here…
I have a Z-stick that I’ve previously used openzwave for, so all inclusions are already done, I’m “only” changing the software I’m using. This worked like a charm for all devices in my house except for one, a Sensative Strip. For the other devices I got items in my smarthome inbox which I just acknowledged and everything was ok, but the Strip never show up. I tried opening and closing the door and I see in the log that the controller is receiving stuff (log snippet here: http://pastebin.com/dH5FhBAZ). What I’m reacting over in the log is the “Node is DEAD. Dropping message.”. It seems pretty clear to me the node isn’t dead since it’s sending…
Anyway, I tried to find the little round magnet, don’t know where I put it. Will any magnet do? And will it do any good?
I’ve had this issue also a couple of times (node was marked as dead). You should wake it up several times manually (an open/close is NO wakeup!) using the magnet. I think any magnet will do the job. You can easily check this when you put a magnet near the round edge of the strip. Then the LED on the other end of the strip should flash. For a correct wakeup you must do this three times in max. 10 seconds!! And you need to wakeup the device several times (sometimes up to 10 times).
And, nearly most important: You have to use a quite recent version of the zwave binding. On which version are you currently?
I’m on the latest version (2.0.0). It has showed up now (without me doing anything at all) but it says “The device initialisation is not complete”, guess I’ll need to try that magnet trick
Yes. It only wakes up once a day if you don’t do anything else. And so it can take some days until the initialisation is fully completed. For whatever reason one wakeup is not enough to get the device initialised. So go get a magnet.
The sensative Strip takes a long time to initialize completely.
I had it lying on my desk for days (to play with, without actually opening the door to my garden), together with my Razbian device.
The battery indicator was not updated until after a few days, now showing 100%, which is correct for a new device.
I had to awakw he device several times, before connecting for the first time.
Ok. After finding a magnet and fiddling around with it it’s now recognized correctly. It doesn’t notice me opening the door though which makes it kinda worthless. This worked before (when I was using openzwave) so I know the hardware is positioned correctly. It also shows 100% for the battery, which I doubt since it’s over a year old (I got it november 2015). Anything anyone else recognizes?
Btw, the swedish manual says that “Om någon försöker manipulera Strips med en annan magnet, skickas en
alarmsignal (Tamper) till din Z-Wave controller.” which translates to “If anyone tries to manipulate Strips with another magnet a alarm signal (Tamper) will be sent to your Z-Wave controller”. The english manual doesn’t say the same thing. I tried manipulating it with another magnet whilst speaking swedish though and I got no alarm signal…
Make sure that the notification type is set to use ‘notifications’ and not the ‘binary sensor’ - this is the default value, but if you’ve used it with other software you might have changed it.
It still reports 100% battery though. If that’s true after more than one year it would mean the battery lasting at least a hundred years. Guess I won’t live long enough to know if that’s the case
Same for me and mine is also about a year old. For sure this device is special in many ways. But battery operated zwave devices tend to not report the battery status a 100% correct. Often it’s stays high at the beginning of the lifecycle and then drops quite fast.
And as this strip has come to market about a year ago, we don’t have any long term experiences.
I didn’t get my Strip connected to my OH2 z-wave network. I’m using the z-Wave Bundle Version 2.1.0.201702121957 (Snapshot Version)
Also I’m Using the “Z-Wave ZME_UZB1 Me USB Stick”. Can this be the Problem? Should I use a different stick?
I activate the inclusion mode and wake up the sensor. But it never gets connected. I tried at least 50 times to connect the sensor with my network. I’m very good at waking up the strip sensor with the magnet now.
I activated the Debug for the z-wave binding and didn’t see anything (no communication).
Updating the ‘Inclusion Mode Timeout’ to value greater then 30 seconds doesn’t change anything on the USB stick. The stick is only for a maximum for 30 second in Inclusion Mode.
Do you get a debug message that the inclusion has started when you activate the inclusion mode?
30 seconds should be enough, so no need to set a longer timeframe.
Have you already included other zwave devices? Do they work properly? If not, it the UZB stick installed properly? I don’t think that the stick in general has a problem with the sensative strip. But maybe it’s not working at all?
How long is the distance between stick and strip? Inclusion should happen in close proximity to the device.
Just to double-check how to get this to work with OH2.0. Config parameter 1 set to “notification report” and item created as a Contact, not as a Switch? Then it should work?
Glad I found this thread, I also fight with the strips and don’t get them to show open/close in the BasicUI Default Home sitemap anymore.
While a lot has been written about HABmin configuration settings here - can someone provide a working items file for the strips and ideally a sample rule.
Would be highly appreciated.
)
But battery operated zwave devices tend to not report the battery status a 100% correct. Often it’s stays high at the beginning of the lifecycle and then drops quite fast.