SENSATIVE Strips Compatablility

dustycanderson · June 20, 2017

Good evening everyone,

I have been reading posts on UDI forums for a couple of years now but this is my first post, so please forgive the ignorance.

I purchased a couple of the SENSATIVE Strips (http://www.sensative.com/ ) and have been have issues getting them to work correctly with the ISY. They register the Notify Sensor for the battery life and the Binary Sensor whether it is on or off. The issue is after it is included the binary sensor will not change state. I contacted Sensative and the stated the ISY is not compatible with Strips in their current parameter setting and one parameter will need to be changed. They did say that the ISY programmers are going to make the ISY compatible shortly.

Whenever I try to change the parameter it errors out.

Has anyone else gotten these strips to work and if so a little help would be much appreciated.

Jimbo.Automates · June 20, 2017

The device has to be awake when you try to change the param, is there a way to wake up the device and have it stay awake? And if there is you will need to change the ISY setting to not automatically put devices back from sleep. There is also a post from Chris on how to set params via the rest interface which can be easier.

There is another post on here about adding support, but I don't think UDI responded. But I think it's a common issue we have seen with other devices that Chris said will be fixed.

Sent from my Nexus 6P using Tapatalk

dustycanderson · June 20, 2017

Thanks for the advice Jimbo. I have manually woken the device and tried to change the parameter numerous times, but I have not shut of the auto sleep function yet nor have I tried to change the parameters through rest yet. I will need to look into that a little bit. Thanks for the advice.

Sent from my SAMSUNG-SM-G930A using Tapatalk

Michel Kohanim · June 20, 2017

Hi dustycanderson ,

We did have an exchange with Sensative and it will be included in 5.0.11 release.

With kind regards,

Michel

ggdowski · June 20, 2017

This looks like a nice device.

dustycanderson · June 23, 2017

Update on SENSATIVE.

I have updated my firmware to 5.0.10 and am still having the same issue. I'm still unable to change the parameters on the device even after shutting off the Auto Sleep setting, and manually waking the device. I may just have to wait until 5.0.11 version arrives. I have not tried REST to change parameters. (Might be a little to involved for me at this time.)

The funny thing is everything includes; like notify sensor for battery, binary sensor for open/closed, and tamper alarm, but the binary sensor will not change state.

Any other advice would be great otherwise I may just wait until 5.0.11 version arrives. Does anyone have an estimation on when 5.0.11 will be available?

G W · June 23, 2017

I'm smiling, Michel, I'm smiling.

Sent from my Nexus 6P using Tapatalk

dustycanderson · June 23, 2017

Thanks for the advice Gary!

Sent from my SAMSUNG-SM-G930A using Tapatalk

jtara92101 · June 24, 2017

Showing results for sensitive

Search instead for sensative

Aside: I hate it when companies name themselves such as they make themselves unsearchable.

"Cute" mis-spelling, AND a generic term!

I am working on a project that uses the Abomination Known As Parse. I am working diligently to remove said abomination. (Actually, it's a rewrite.) Of course, Parse has absolutely nothing to do with parsing.

Sometimes a news event will suddenly make a company unsearchable. It's a good idea to consider if that might happen with your company name.

There is nothing "hidden" about these. Traditional screw-in magnetic sensors/magnets that are drilled and filled are hidden.

Sure, they are "hidden" from the outside. Once somebody walks through the door, though, they will set-off the "something valuable may be kept in here" red light in the brains of some individuals.

G W · June 24, 2017

Thanks for the advice Gary!

Sent from my SAMSUNG-SM-G930A using Tapatalk

It's not advice. It's a message to Michel. I was hoping for a release this weekend but I guessed wrong.

Sent from my Nexus 6P using Tapatalk

lilyoyo1 · June 24, 2017

There is nothing "hidden" about these. Traditional screw-in magnetic sensors/magnets that are drilled and filled are hidden.

Sure, they are "hidden" from the outside. Once somebody walks through the door, though, they will set-off the "something valuable may be kept in here" red light in the brains of some individuals.

Actually they are "hidden" based off the definition of hidden. They are out of sight and concealed when the door is closed just like the magnetic sensors you reference. According to your logic, even the magnetic ones are not hidden since a person could still see the outline of the hole should they know what to look for.

Not only that, should someone be breaking in, see them, and assume something valuable may be kept; it's to late. Whatever it triggers would have already been triggered. Besides, if they are already entering, they've already determined something valuable is hidden there.

I've seen these on Amazon but havent jumped on it yet. I have a sliding closet door in one of my bedrooms that this would be perfect on. Let us know know how it works once the ISY supports it.

Michel Kohanim · June 25, 2017

Hi dustycanderson, we do have this working at both UDI and Sensative. Only the parameter must be configured. In either case, this is already fixed in 5.0.11.

Hi Gary, I will relay your smile to Chris. Or, you can do it yourself!

Hi jtara92101, would you be kind enough to post unrelated topics to the Coffee Shop section?

With kind regards,

Michel

dustycanderson · June 26, 2017

Thanks for the update Michel. Maybe I am missing something but I can not seem to change the parameters on the Sensative strip in version 5.0.10. I have tried waking it and turning off the auto sleep setting. If you have any advice for me on the best way to change the parameter I would appreciate it. I was told by Sensative that Parameter 1 needs to be set to 0.

After waking the device I have tried to change the parameter by,

Parameter number 1

Parameter size 1

Parameter Value 0

and it always errors out.

If 5.0.11 is coming out soon then I will not worry about changing the parameter.

paulbates · June 26, 2017

Thanks for the update Michel. Maybe I am missing something but I can not seem to change the parameters on the Sensative strip in version 5.0.10.

...

If 5.0.11 is coming out soon then I will not worry about changing the parameter.

Hi Dusty

New requirements / fixes are released in the next version, so you can try this and test it in 5.0.11 when its released. Michel's comments about having tested this in 5.0.11 together with sensative are very encouraging.

UDI has an unwritten policy of code quality over date commitments, so we'll have to be patient as the all of the fixes and changes for 5.0.11, including this one, are completed and internally tested.

Paul

Michel Kohanim · June 26, 2017

Hi dustycanderson,

Let me make sure you are saving the correct parameter/value/size. I'll get back to you shortly.

With kind regards,

Michel

dustycanderson · June 26, 2017

I received an update from Sensative earlier today that I will try either tonight or tomorrow.

Below is the update I recieved;

Hello Dustin

I read (what i assume is) your forum post: http://forum.universal-devices.com/topic/21987-sensative-strips-compatablility/. Your parameters are correct; Parameter number = 1, Parameter size = 1, Parameter value = 0. I instead suspect that you are missing the timings for when Strips is awake.

The ISY 994izw doesn't seem to allow queuing of commands, i.e. setting a change in configuration parameters and having it automatically sent whenever the device later wakes up. Instead, the configuration change is sent as soon as you press the "set" button. This means that Strips needs to be awake that time.

Waking Strips up isn't that straightforward either. Once the manual wake up pattern is complete, Strips will send tamper followed ~1sec later by NIF (Node Information Frame) which signifies that Strips is awake. The time window is quite short though, as Strips doesn't stay awake for long.

I found that the best timing was to: Perform the manual wake up pattern (take note of the LED indications). Once you REMOVE the magnet a third time, wait for 3 seconds. Then immediately press the "set" button for configuration settings.

Applying the settings in a gateway which doesn't queue user commands can be tricky, but it is doable. Let me know how it goes. If necessary we can set up a Skype meeting where i show you how i change the settings.

dustycanderson · June 26, 2017

Update... Success!!! The above works for changing the parameter and now the strip works. Thanks for all the help.

Sent from my SAMSUNG-SM-G930A using Tapatalk

sbenton9291 · July 2, 2017

Hi All,

I wanted to provide an update for those of us not yet running 5.X.X. I am currently running v4.6.2 on my ISY and following the instructions provided by dustycanderson above I was able to get my sensitive strips to work as intended. These are awesome devices that are much more appealing to use than the giant battery powered warts that have been available until now.

Thanks everyone above for figuring this out.

Jimbo.Automates · March 11, 2018

On 6/20/2017 at 8:51 AM, Michel Kohanim said:

Hi dustycanderson ,

We did have an exchange with Sensative and it will be included in 5.0.11 release.

With kind regards,

Michel

Michel,

Do we still need to change parameters? I just remembered to grab mine out of the box and try again, it was already included but not being used, and I'll I see in the log is:

Sat 03/10/2018 07:06:27 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0616] Unrecognized Event 0x16 [000000FF06160000] ACK,AUTO,EXPLORE From=0x27
Sat 03/10/2018 07:06:27 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0616] Unrecognized Event 0x16 [000000FF06160000] ACK,AUTO,EXPLORE From=0x27
Sat 03/10/2018 07:06:35 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0617] Unrecognized Event 0x17 [000000FF06170000] ACK,AUTO,EXPLORE From=0x27
Sat 03/10/2018 07:06:38 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0616] Unrecognized Event 0x16 [000000FF06160000] ACK,AUTO,EXPLORE From=0x27

I'm on 5.0.12.

- Jim

Michel Kohanim · March 11, 2018

Hi Jimbo,

I have asked for clarification from Chris.

With kind regards,

Michel

Bumbershoot · March 11, 2018

I've never seen or heard of these devices before, but they appear to be exactly what I need for a couple of door applications. I appreciate the tip-off on these!

Chris Jahn · March 12, 2018

On 3/10/2018 at 7:24 PM, Jimbo said:

Michel,

Do we still need to change parameters? I just remembered to grab mine out of the box and try again, it was already included but not being used, and I'll I see in the log is:

Sat 03/10/2018 07:06:27 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0616] Unrecognized Event 0x16 [000000FF06160000] ACK,AUTO,EXPLORE From=0x27
Sat 03/10/2018 07:06:27 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0616] Unrecognized Event 0x16 [000000FF06160000] ACK,AUTO,EXPLORE From=0x27
Sat 03/10/2018 07:06:35 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0617] Unrecognized Event 0x17 [000000FF06170000] ACK,AUTO,EXPLORE From=0x27
Sat 03/10/2018 07:06:38 PM : [ZWAVE-RX ZW039_1] [71/05] Alarm Report [0616] Unrecognized Event 0x16 [000000FF06160000] ACK,AUTO,EXPLORE From=0x27

I'm on 5.0.12.

- Jim

Hi Jim,

We had some success testing these a few weeks back, but I'll have to take a look regarding these specific messages. I've opened a bug report and hopefully we can get this resolved soon.

Jimbo.Automates · March 12, 2018

15 minutes ago, Chris Jahn said:

Hi Jim,

We had some success testing these a few weeks back, but I'll have to take a look regarding these specific messages. I've opened a bug report and hopefully we can get this resolved soon.

Thanks Chris. Should I exclude and re-include it? It was included with a much older 5.x version, not sure which one.

Bumbershoot · March 13, 2018

ISY firmware 5.0.12.

I just received one of these little devices in the mail. The ISY included it quickly and easily, and it installed three nodes: Notify Sensor, Tamper Code Alarm 1 and Binary Sensor 1.

it does appear that parameter 1 does need to be to 0 to get it to work. I did this prior to mounting it on my door, while it was sitting with me on my desk, so that was a cinch to do. Below are some snips from the event log:

Tue 03/13/2018 14:51:35 : Z-Wave device detected, retrieving info 5
Tue 03/13/2018 14:51:35 : Adding Z-Wave devices stopped
Tue 03/13/2018 14:51:35 : Device 15 of type 4.7.1 included into Z-Wave network
Tue 03/13/2018 14:51:36 : Adding ISY node(s) for new Z-Wave device 15 type 4.7.1
Tue 03/13/2018 14:51:37 : Adding additional nodes for new Z-Wave device 15
Tue 03/13/2018 14:51:37 :   ...addNodes(uid=15,ZWAVEPLUS_INFO,cc=94,ver=0,sec=F)
Tue 03/13/2018 14:51:37 :   ...addNodes(uid=15,VERSION,cc=134,ver=0,sec=F)
Tue 03/13/2018 14:51:37 :   ...addNodes(uid=15,MANUFACTURER_SPECIFIC,cc=114,ver=0,sec=F)
Tue 03/13/2018 14:51:37 :   ...addNodes(uid=15,SENSOR_BINARY,cc=48,ver=0,sec=F)
Tue 03/13/2018 14:51:38 : [ZW-ADD 15.0] ZW015_104 ST ctl=T vte=1.0.114 agi=0.0.0 grp=1 nt=104.48 cc=3.78 uom=0 prec=127
Tue 03/13/2018 14:51:38 :   ...addNodes(uid=15,CONFIGURATION,cc=112,ver=0,sec=F)
Tue 03/13/2018 14:51:38 :   ...addNodes(uid=15,NOTIFICATION,cc=113,ver=0,sec=F)
Tue 03/13/2018 14:51:40 :   ...addNodes(uid=15,DEVICE_RESET_LOCALLY,cc=90,ver=0,sec=F)
Tue 03/13/2018 14:51:40 :   ...addNodes(uid=15,ASSOCIATION,cc=133,ver=0,sec=F)
Tue 03/13/2018 14:51:40 :   ...addNodes(uid=15,ASSOCIATION_GROUP_INFO,cc=89,ver=0,sec=F)
Tue 03/13/2018 14:51:40 :   ...addNodes(uid=15,BATTERY,cc=128,ver=0,sec=F)
Tue 03/13/2018 14:51:40 :   ...addNodes(uid=15,WAKE_UP,cc=132,ver=0,sec=F)
Tue 03/13/2018 14:51:41 :   ...addNodes(uid=15,POWERLEVEL,cc=115,ver=0,sec=F)
Tue 03/13/2018 14:51:41 : Initializing ISY as wakeup target for new Z-Wave device 15.0
Tue 03/13/2018 14:51:42 : [ZWAVE-INIT    15] Assigning Wakeup to ISY (id=1), Interval 86400 seconds
Tue 03/13/2018 14:51:42 : [   ZW015_104]       ST   0 (uom=78 prec=0)
Tue 03/13/2018 14:51:42 : [     ZW015_1]   BATLVL 100 (uom=51 prec=0)
Tue 03/13/2018 14:52:20 : [ZW-ADD 15.0] ZW015_173 ST ctl=F vte=3.0.130 agi=0.0.0 grp=1 nt=173.113 cc=5.78 uom=0 prec=127
Tue 03/13/2018 14:52:20 : [   ZW015_173]       ST 100 (uom=78 prec=0)
Tue 03/13/2018 14:52:20 : [   ZW015_173]      DON 100 (uom=78 prec=0)
Tue 03/13/2018 14:52:45 : [   ZW015_173]      DON 100 (uom=78 prec=0)
Tue 03/13/2018 14:53:50 : [ZWAVE-WAKEUP  15] Force writes to ZW015_1
Tue 03/13/2018 14:55:59 : [   ZW015_173]      DON 100 (uom=78 prec=0)
Tue 03/13/2018 14:56:24 : [   ZW015_104]       ST 100 (uom=78 prec=0)
Tue 03/13/2018 14:56:24 : [   ZW015_104]      DON 100 (uom=78 prec=0)
Tue 03/13/2018 14:57:18 : [   ZW015_104]       ST   0 (uom=78 prec=0)
Tue 03/13/2018 14:57:18 : [   ZW015_104]      DOF   0 (uom=78 prec=0)

Tue 03/13/2018 15:11:28 : [ZW-SHOW         ] ----------------------------------------------
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ] ZW 015 Notify Sensor
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ] ZW015_1 uid=15 type=4.7.1 mid=410 tid=3 pid=3
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ] Association Group ID 1
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x5E  V2   ZWAVEPLUS_INFO
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x86  V2   VERSION
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x72  V1   MANUFACTURER_SPECIFIC
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x30  V1   SENSOR_BINARY
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x70  V1   CONFIGURATION
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x71  V4   NOTIFICATION
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x5A  V1   DEVICE_RESET_LOCALLY
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x85  V2   ASSOCIATION
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x59  V1   ASSOCIATION_GROUP_INFO
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x80  V1   BATTERY
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x84  V2   WAKE_UP
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ]    -  x73  V1   POWERLEVEL
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ] - Secure
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ] 
Tue 03/13/2018 15:11:28 : [ZW-SHOW         ] ----------------------------------------------

The Mrs. approves that's it's invisible.

Bumbershoot · March 22, 2018

For anyone interested in these, it might be good to know that these strips don't wakeup and populate the "status" field across reboots, so if this is data you'll need prior to the door/window being opened or closed after an ISY reboot, you'll need to take alternative actions. I simply run a program that populates a variable (both "Value" and "Init" fields) when the door opens/closes. I then have programs check the value of the variable instead of status of the device. This will allow for data persistence across reboots.

Master External Door Status - [ID 00FA][Parent 0013]

If
        'Devices / dirMasterBedroom / Master External Door Sensor / Master External Door' Status is On
 
Then
        $s.MasterExternalDoor  = 1
        $s.MasterExternalDoor Init To 1
 
Else
        $s.MasterExternalDoor  = 0
        $s.MasterExternalDoor Init To 0

Sign In

SENSATIVE Strips Compatablility

Recommended Posts

dustycanderson

Jimbo.Automates

dustycanderson

Michel Kohanim

ggdowski

dustycanderson

G W

dustycanderson

jtara92101

G W

lilyoyo1

Michel Kohanim

dustycanderson

paulbates

Michel Kohanim

dustycanderson

dustycanderson

sbenton9291

Jimbo.Automates

Michel Kohanim

Bumbershoot

Chris Jahn

Jimbo.Automates

Bumbershoot

Bumbershoot

Archived

Recently Browsing

Who's Online (See full list)

Forum Statistics

Browse

Activity