New Aeotec Door/Window Sensor 7 not in Database yet?

[Bruce_Osborne]

@chris or @sihui any suggestions!

[chris (Chris Jackson)]

I’ve not read through all the messages here to understand what the issue is, but I can comment on the last message -:

@calevans

when I try to add the device, it keeps coming up as “Device Unknown”.

Please post the properties that are discovered for the device - or the XML file that is created for the device (from the userdata/zwave folder). There are 2 reasons why this can happen (I think it will show these reasons in PaperUI when the device shows as unknown?).

1. The device isn’t in the database
2. The device isn’t fully discovered

If it’s the second one, then you need to wake up the device a few times so that it is discovered. Otherwise, please post a debug log showing the inclusion.

[calevans]

Hi @chris !

Ok, it’s been a while since I’ve done this but I think I got what you needed. Attached is a portion of my openhab.log and the network_db66087b__node_33.xml file. There was no node_33.xml file.

Also, yes, PaperUI tells me that the problem is one of the two but it does not state WHICH of the two it is.

Thanks for your help.

Cheers!
=C=

network_db66087b__node_33.xml (12.5 KB) zwave.log (413.7 KB)

[Bruce_Osborne]

Thanks.
That is what I meant when I said the file ENDS WITH … I did not know your network id number.

[Bruce_Osborne]

@sihui @chris I think I see the issue. This looks like the sensor. I think we need to add a reference 0102:0007 to recognize this particular device.
It looks like it was not completed.

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1065

EDIT: Pasting the xml file did not work so I will try to update some manually.

[jwiseman (Mr. Wiseman (OH 4.2 Snapshot on Pi4))]

Hi @calevans,

Once you get yours up and running with this new device; I plan to roll it out in my house. I currently don’t have any door sensors but have a lot of other Aeotec zWave stuff in the house.

LMK when your is working

Best, Jay

[calevans]

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=

[Bruce_Osborne]

@sihui I updated & submitted for review.

[ffr (F.)]

I am really looking forward to have this sensor working as well.
Key points for me are

• secure inclusion
• tilt sensor functionality

When both of these features work, then this will be the sensor I was looking for over the last months.

[sihui]

@Bruce_Osborne

I think we need to add a reference 0102:0007

@Bruce_Osborne

I updated & submitted for review

Done.

[calevans]

Do we have an eta on the release of the binding with the update in it?

Cheers!
=C=

[Bruce_Osborne]

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.

Zigbee and zwave manual install script

A number of people have run into trouble performing manual installs of the Zigbee and Z-Wave bindings. A manual install (dropping the jar into addons) is rarely needed, but some people prefer a manual install over apt-get, or want to use a stable OH release with a recent Zigbee or Z-Wave binding. Here is a script that will hopefully make it easier to install, upgrade, and uninstall these bindings, and prevent some of the common issues. Who would benefit from this script: Anyone wanting to tes…

[calevans]

@Bruce_Osborne

This script is the easy way to add it to OH, in my experience.

Zigbee and Z-Wave manual install script Tutorials & Examples

Did the trick.
Thank you to all who helped.

Cheers!
=C=

[omatzyo]

Are you getting notifications from this device? I have a few and they are not reporting the contact changing.

[ffr (F.)]

Sounds great.
My two questions: Did you use secure inclusion? Have you tested the tilt functionality yet?

[calevans]

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=

[omatzyo]

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?

[calevans]

@omatzyo

@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=

[omatzyo]

I see that. Good luck! Thanks for doing all the legwork to get this going.

[calevans]

@Bruce_Osborne

The updated binding is here.

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=