I love All the Aeotech stuff I have. When I get these up and running I will most likely replace the Sensitiv strips I currently have with the new Door 7’s. Better solution and a field serviceable battery. 
Now if I could jsut get my hands on a Doorbell 6.
Cheers!
=C=
I am really looking forward to have this sensor working as well.
Key points for me are
When both of these features work, then this will be the sensor I was looking for over the last months.
Done.
Do we have an eta on the release of the binding with the update in it?
Cheers!
=C=
The updated binding is here.
https://ci.openhab.org/job/openHAB2-Bundles/org.openhab.addons.bundles%24org.openhab.binding.zwave/
This script is the easy way to add it to OH, in my experience.
Did the trick. 
Thank you to all who helped.
Cheers!
=C=
Are you getting notifications from this device? I have a few and they are not reporting the contact changing.
Sounds great.
My two questions: Did you use secure inclusion? Have you tested the tilt functionality yet?
We are having a discussion about the security of the device over here Aeotec Door/Window Sensor 7 "SECURITY not supported"
No, I’ve not tested tilt. Right now I just have the sensor laying on my desk trying to get it to work with open/close before I move on to anything else.
Cheers!
=C=
I have included a few of these (not secure) but the tilt nor the magnet seem to be triggering any of the channels. I am getting battery level at least. The LED indicates that it is transmitting.
@calevans have you had any luck?
No, but I’m still working through other issues over on the other thread.
I’m not that interested in the tilt sensor, jsut the standard open/close.
Cheers!
=C=
I see that. Good luck! Thanks for doing all the legwork to get this going.
Hi @Bruce_Osborne!
Ok, I’ve got the latest binding 2.5.0.201908062233 but things still aren’t working.
1: Whenever I include the device on my network, I immediately get two devices, one recognized and one not.
2: I build out items in my items file to pair up with the recognized device. it says it reads the items file. I put the ZWave binding into debug log mode and I get the following for NODE 35. (The recognized one)
2019-08-07 18:26:25.394 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Device initialisation complete.
2019-08-07 18:26:58.524 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Channel zwave:device:d1f60367:node35:sensor_binary linked - polling started.
2019-08-07 18:26:58.529 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Channel zwave:device:d1f60367:node35:battery-level linked - polling started.
2019-08-07 18:26:58.528 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Channel zwave:device:d1f60367:node35:alarm_access linked - polling started.
2019-08-07 18:26:58.536 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Channel zwave:device:d1f60367:node35:battery-level linked - polling started.
2019-08-07 18:28:15.479 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 35: Device discovery completed
2019-08-07 18:28:15.494 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 35: Device discovery resolved to thingType zwave:aeotec_zwa008_00_000
So it LOOKS to me like it is working. However, when I either open or close the switch (move the magnet away or closer) nothing reports in the log.
I went in via HABMin and tried to set the Lifeline because it is currently empty, that reports:
2019-08-07 18:48:42.563 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update received
2019-08-07 18:48:42.570 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update set group_1 to [controller] (ArrayList)
2019-08-07 18:48:42.573 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Association 1 consolidated to [controller]
2019-08-07 18:48:42.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Unknown association group 1
I tried the same via PaperUI and got this
2019-08-07 18:59:30.481 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update received
2019-08-07 18:59:30.489 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored binding_cmdrepollperiod to 1500 (BigDecimal)
2019-08-07 18:59:30.492 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_10_2 to 0 (BigDecimal)
2019-08-07 18:59:30.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored group_4 to null (null)
2019-08-07 18:59:30.499 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update set group_1 to [controller] (ArrayList)
2019-08-07 18:59:30.503 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Association 1 consolidated to [controller]
2019-08-07 18:59:30.506 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Unknown association group 1
2019-08-07 18:59:30.509 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored group_3 to null (null)
2019-08-07 18:59:30.513 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored group_2 to null (null)
2019-08-07 18:59:30.516 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update set wakeup_node to null (null)
2019-08-07 18:59:30.519 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Error converting wakeup value null
2019-08-07 18:59:30.522 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_11_2 to 0 (BigDecimal)
2019-08-07 18:59:30.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_12_1 to 1 (BigDecimal)
2019-08-07 18:59:30.529 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_13_1 to 0 (BigDecimal)
2019-08-07 18:59:30.532 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_14_1 to 0 (BigDecimal)
2019-08-07 18:59:30.535 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored action_failed to false (Boolean)
2019-08-07 18:59:30.538 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored wakeup_interval to 0 (BigDecimal)
2019-08-07 18:59:30.541 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored action_remove to false (Boolean)
2019-08-07 18:59:30.543 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored binding_pollperiod to 86400 (BigDecimal)
2019-08-07 18:59:30.546 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored action_heal to false (Boolean)
2019-08-07 18:59:30.549 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_1_1 to 0 (BigDecimal)
2019-08-07 18:59:30.552 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_2_1 to 0 (BigDecimal)
2019-08-07 18:59:30.555 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_7_1 to 255 (BigDecimal)
2019-08-07 18:59:30.558 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_8_1 to 0 (BigDecimal)
2019-08-07 18:59:30.561 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_9_2 to 0 (BigDecimal)
2019-08-07 18:59:30.563 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_3_1 to 7 (BigDecimal)
2019-08-07 18:59:30.566 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_4_1 to 0 (BigDecimal)
2019-08-07 18:59:30.569 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_5_1 to 0 (BigDecimal)
2019-08-07 18:59:30.571 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored node_id to 35 (BigDecimal)
2019-08-07 18:59:30.574 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Configuration update ignored config_6_1 to 2 (BigDecimal)
I’m not sure if any of that helps show what is going on.
This is the first time I’ve used a multi-sensor switch so there is a good possibility that I am doing something wrong. Any help or pointing me in the right direction would be greatly appreciated.
Cheers!
=C=
I’ve gone over the entry in the ZWave Database and compared it against the technical manual and everything seems correct.
To my untrained eye, the problem SEEMS to stem from the fact that I can’t associate it with the controller.
I could be wrong but that just sticks out to me.
Cheers!
=C=
You mention nothing reported in the log when activating the sensor.
Do you have an item defined linked to that thing channel? If not there would be nothing in the log.
Yes
The sensor is NODE 35 on my system.
I have this in my opening.items file
/*
* Aeoteec Door/Window Sensor 7
*/
Contact Test_T1_Binary "Test #1 Binary" (outsideDoors, openings) { channel="zwave:device:d1f60367:node35:sensor_binary" }
Switch Test_T1_Alarm_Access "Test #1 Alarm" { channel="zwave:device:d1f60367:node35:alarm_access" }
Switch Test_T1_Alarm_Burglar "Test #1 Burgler" { channel="zwave:device:d1f60367:node35:alarm_burglar" }
Number Test_T1_Battery "Test 1 Battery [%d %%]" { channel="zwave:device:d1f60367:node35:battery-level" }
The device is correct, I copied it from the Things page.
The items show up in PaperUI when I go into Control and find the switch. But they do not respond when I move the magnet and trigger the switch.
Cheers!
=C=
Has a debug log during inclusion been posted?
The sensor_binary channel needs to be a Switch itemtype, not a Contact itemtype.