I wonder if anyone has tried these new (to the US) door & window sensors:
New Door/Window Sensor
- 465 Views
- Last Post 03 March 2017
nelis249
posted this
18 February 2017
I'll try one, though I call BS on their battery claim, "Built-in battery that lasts up to 10 years". 'Up to' is subjective. I'll look for their fine print similar to "***battery last up for 10 years if product remains in the box"
I have a couple of the Aeon Labs Recessed Door Sensors an those batteries under normal door open/close usage (1 or 2 times a day) last about a year or so, and those are far larger batteries.
I'll give you a report in a few days, and 9.97 years from now when I have to change the battery.
nelis249
posted this
20 February 2017
Alright I have the device linked to the zwave controller. It appears Axial is going to need an update for it to work. I've tried all different device types (alarm, binary sensor, motion sensor, etc..). It appears the device is registered as a new class (07). Zentools doesn't even know what it is (see screen shot).
@rscott
Here's the info I'm getting in the logs. Anything I can do to gather more data to assist?
Contact open:
2/19/2017 8:27:59 PM: Unprocessed parameter Zensor_Net_Source_Node_ID, value=0 from node 39 alarm_report
2/19/2017 8:27:59 PM: parameter ZWave_Alarm_Type, value=6 from node 39 alarm_report
2/19/2017 8:27:59 PM: zwave_alarm_type set with value of 6 from value 6
2/19/2017 8:27:59 PM: parameter ZWave_Alarm_Event, value=22 from node 39 alarm_report
2/19/2017 8:27:59 PM: Unprocessed parameter Number_of_Event_Parameters, value=0 from node 39 alarm_report
Contact closed:
2/19/2017 8:32:35 PM: Unprocessed parameter Zensor_Net_Source_Node_ID, value=0 from node 39 alarm_report
2/19/2017 8:32:35 PM: parameter ZWave_Alarm_Type, value=6 from node 39 alarm_report
2/19/2017 8:32:35 PM: zwave_alarm_type set with value of 6 from value 6
2/19/2017 8:32:35 PM: parameter ZWave_Alarm_Event, value=23 from node 39 alarm_report
2/19/2017 8:32:35 PM: Unprocessed parameter Number_of_Event_Parameters, value=0 from node 39 alarm_report
Opinion, seems like good sensor. It's pretty thin and will easily fit above doors. I'm hope this can work.
rscott
posted this
20 February 2017
Could you verify that the USB stick is configured as part of association group 1 on the sensor, then turn on the audit for that node, restart and then do the open/close again to see if there are any additional reports being sent from it?
nelis249
posted this
22 February 2017
- Last edited 22 February 2017
Hm odd. I can't load the associations on the USB stick or any device for that matter. I keep getting:
"The controller did not respond to the associated device request. Please verify that your device is awake and within range".
Of course the USB stick controller is awake. The log just says "Retrieving device associations for 1 and group 1...". I proceeded when the audit checked on the new node (the strip device). Attached is the new log data.
This forum isn't allowing attachment of .txt or .log or .zips. here's the logs.
*****Open:
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: ALARM_REPORT
Version: 1
Data: 00,00,{113 5 0 0 0 255 6 22 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: ALARM_REPORT
Version: 2
Data: 00,00,0,On,Access Control,16,00,,{113 5 0 0 0 255 6 22 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Unprocessed parameter Zensor_Net_Source_Node_ID, value=0 from node 39 alarm_report
2/21/2017 9:40:35 PM: parameter ZWave_Alarm_Type, value=6 from node 39 alarm_report
2/21/2017 9:40:35 PM: zwave_alarm_type set with value of 6 from value 6
2/21/2017 9:40:35 PM: parameter ZWave_Alarm_Event, value=22 from node 39 alarm_report
2/21/2017 9:40:35 PM: Unprocessed parameter Number_of_Event_Parameters, value=0 from node 39 alarm_report
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 3
Data: 00,00,00,On,Access Control,16,0,0,false,,00,{113 5 0 0 0 255 6 22 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 4
Data: 00,00,00,On,Access Control,16,0,0,false,,00,{113 5 0 0 0 255 6 22 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 5
Data: 00,00,00,On,Access Control,16,0,0,false,,00,{113 5 0 0 0 255 6 22 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 6
Data: 00,00,00,On,Access Control,16,0,0,false,,00,{113 5 0 0 0 255 6 22 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 7
Data: 00,00,00,On,Access Control,16,0,0,false,,00,{113 5 0 0 0 255 6 22 0 0 }
Received: 2/21/2017 9:40:35 PM
******Close:
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: ALARM_REPORT
Version: 1
Data: 00,00,{113 5 0 0 0 255 6 23 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: ALARM_REPORT
Version: 2
Data: 00,00,0,On,Access Control,17,00,,{113 5 0 0 0 255 6 23 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Unprocessed parameter Zensor_Net_Source_Node_ID, value=0 from node 39 alarm_report
2/21/2017 9:40:35 PM: parameter ZWave_Alarm_Type, value=6 from node 39 alarm_report
2/21/2017 9:40:35 PM: zwave_alarm_type set with value of 6 from value 6
2/21/2017 9:40:35 PM: parameter ZWave_Alarm_Event, value=23 from node 39 alarm_report
2/21/2017 9:40:35 PM: Unprocessed parameter Number_of_Event_Parameters, value=0 from node 39 alarm_report
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 3
Data: 00,00,00,On,Access Control,17,0,0,false,,00,{113 5 0 0 0 255 6 23 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 4
Data: 00,00,00,On,Access Control,17,0,0,false,,00,{113 5 0 0 0 255 6 23 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 5
Data: 00,00,00,On,Access Control,17,0,0,false,,00,{113 5 0 0 0 255 6 23 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 6
Data: 00,00,00,On,Access Control,17,0,0,false,,00,{113 5 0 0 0 255 6 23 0 0 }
Received: 2/21/2017 9:40:35 PM
2/21/2017 9:40:35 PM: Node Audit:
Node: 39
Command: NOTIFICATION_REPORT
Version: 7
Data: 00,00,00,On,Access Control,17,0,0,false,,00,{113 5 0 0 0 255 6 23 0 0 }
Received: 2/21/2017 9:40:35 PM
rscott
posted this
23 February 2017
Hm odd. I can't load the associations on the USB stick or any device for that matter. I keep getting:
"The controller did not respond to the associated device request. Please verify that your device is awake and within range".
Of course the USB stick controller is awake. The log just says "Retrieving device associations for 1 and group 1...". I proceeded when the audit checked on the new node (the strip device). Attached is the new log data.
Do you get the same result if you click on the sensor, wake it up, then click associations? If you can get that loaded up and make sure your USB stick has a check mark too, that would be great.
nelis249
posted this
24 February 2017
Yea I get the same error on any device when I click assiciations. I also know that I've done associations before because I've done that with my Aeon multisensors. I fired up zentools, it's not showing associations either. I'm wondering if my Aeon USB stick has gone bad. If you open zentools, select the control, click the association tab on the right pane, does it show anything on your setup?
rscott
posted this
24 February 2017
You'll want to select the device (not the USB stick), then click associations. My USB stick also doesn't respond to associations, but a good majority of my devices do if I wake them up before hand.
nelis249
posted this
25 February 2017
Yea none of my 3 sensors are responding to association request. They are all function perfectly though, triggers immediately, Axial responsive.
Is there any info other than the log data from above I can get for you on the new sensor type?
rscott
posted this
25 February 2017
According to the manual, you can set the device to send a binary_report. You can do this by setting param #1 to a value of 0. Here are the steps:
1) Click the device and the params button
2) Wake it up (see the manual, it involves the magnet)
3) Enter 1 and then retrieve the value
4) When it shows the value, change it to 0 and hit save/set.
nelis249
posted this
26 February 2017
Sweet that worked. For anyone else that uses this sensor, it seems to only stay awake for 5 seconds or so. When trying to set the parameter to 0 I had to do a few times as I was expecting it to stay away fora longer period of time.
rscott
posted this
27 February 2017
@nelis249,
Glad that did the trick for you. Would you mind updating the device library with any info you find pertitent to the use of the sensor with Axial Server? You can do this double clicking the device and going to manufacturer info (you'll need to wake it though).
nelis249
posted this
03 March 2017
Yea no problem. I think Axial still needs an update though. In this binary mode it doesn't have reporting features like battery percentage. It also has a tamper feature which I don't care about, but others might, that too is disabled in this mode.
I must say its by far better than the Aeon door sensor I have which requires drilling holes. I had zero issues sticking in between a door and door jam. I can see this sensor taking off, especially if the battery life claim is even 50% of what they quote.
joe6602
posted this
03 March 2017
Thanks both of you for all the effort on this. I want to use these in my system.
