Problems with Aeotec Door/Window Sensor 7

Setup, Configuration and Use Beginners
1

Hi,

I have a problem including my Aeotec Door/Window Sensor 7 into OpenHab.
I have 3 of the same sensors. One I managed to include and works properly (despite Habmin showing node in initialising state).

The other two sensors I can include and the inclusion seems to go through but Openhab never receives any events from them.
I am running Openhab on Ubuntu 18.04 with UZB controller.

The only difference between the working and non-working thing I can see is the two attributes which don’t exist on the node that does not work - picture below

image
image1418×711 78 KB

I’ve done a bunch of inclusions and removals with no success. Below is a debug log of my latest attempt to re-add the sensor. Any help appreciated. Thanks!

2020-03-20 22:15:51.713 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 20: Device discovery completed
2020-03-20 22:15:51.714 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 20: Device discovery resolved to thingType zwave:aeotec_zwa008_00_000
2020-03-20 22:15:51.716 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:1682213b:node20’ to inbox.
2020-03-20 22:16:35.475 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:1682213b:node20.
2020-03-20 22:16:35.477 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Controller status changed to ONLINE.
2020-03-20 22:16:35.479 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Controller is ONLINE. Starting device initialisation.
2020-03-20 22:16:35.488 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating node properties.
2020-03-20 22:16:35.494 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating node properties. MAN=881
2020-03-20 22:16:35.495 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Updating node properties. MAN=881. SET. Was 881
2020-03-20 22:16:35.497 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Properties synchronised
2020-03-20 22:16:35.504 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Configuration synchronised
2020-03-20 22:16:35.510 [DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
2020-03-20 22:16:35.512 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising Thing Node…
2020-03-20 22:16:35.513 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:1682213b:node20:sensor_binary for OnOffType
2020-03-20 22:16:35.514 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:1682213b:node20:sensor_binary for OnOffType
2020-03-20 22:16:35.516 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:1682213b:node20:scene_number for DecimalType
2020-03-20 22:16:35.517 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:1682213b:node20:scene_number for DecimalType
2020-03-20 22:16:35.519 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:1682213b:node20:sensor_door for OpenClosedType
2020-03-20 22:16:35.521 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:1682213b:node20:sensor_door for OpenClosedType
2020-03-20 22:16:35.523 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:1682213b:node20:alarm_burglar for OnOffType
2020-03-20 22:16:35.524 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:1682213b:node20:alarm_burglar for OnOffType
2020-03-20 22:16:35.526 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising cmd channel zwave:device:1682213b:node20:battery-level for PercentType
2020-03-20 22:16:35.527 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising state channel zwave:device:1682213b:node20:battery-level for PercentType
2020-03-20 22:16:35.529 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Polling initialised at 1800 seconds - start in 66600 milliseconds.
2020-03-20 22:16:35.530 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Device initialisation complete.

2

It’s hard to really comment without a proper log of what’s happening, but I could guess that you haven’t woken the device up.

This is a battery device so you will need to wake it up so that the binding can initialise it fully. There will be a specific button, or button sequence that does this - check the device manual to see how to do it.

3

Hi Chris,

Thanks for quick reply! You are probably right as I see in openhab.log this (ignore the node number change as I re-added it again)

2020-03-20 23:30:50.626 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Polling initialised at 1800 seconds - start in 1500 milliseconds.
2020-03-20 23:30:52.126 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Polling…
2020-03-20 23:30:52.127 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 21: Polling deferred until initialisation complete

I can see how to wake device in the manual - its single click on the only button. Is there anything I need to do in OH to get the binding to initialise it once woken?

Thanks again,

Regards,
Miso

4

Unfiltered debug logs are needed for troubleshooting.
I have seen some manuals wrong where the device took a triple click to wake up instead of a single click. That was a different brand of sensor though.

5

No - the binding just needs to receive the wakeup notification from the device.

6

Hi,

As a new user I can’t attach documents. So I have uploaded log to google drive and made it available here:

It should include everything from the inclusion on. The node in question is 21. Node 3 is inactive as its not currently connected. Node 7 is the other aeotec sensor working fine.

Hope this gives more information. I keep trying waking the sensor but no solution so far…

Thanks!

7

Hi,

After many wakeups I’ve got device working now! Thanks for pointing me in the right direction!

Regards,

Miso

1 Like
8

How much time can pass after include and the wakeup?

I have 5 of these devices. 3 of them are there with 21, 21, 24 Properties.
(I guess even the 2 with 21 are not fully initialized but do have channels, so I can work with)

other two are includes as “unknown devices”. I knew the stuff with wakeup button (on all of them) but did not help (inclueded them and pressed the wakeup ca 30 times with 2 seconds pause directly 1m away from the controller)

Generall question (I guess the answer is NO): Has OpenHAB to be in inclusion mode for that wakeUp stuff?

I waited for one “nightly heal” of the controller but nothing get better.
Both stay with 12 and 15 Properties and “unknown”. Even retrieing wakeup them the next morning several times.

Offtoptic: You are talking about exclusion and inclusion again… Is there a working exclusion NOW in openHAB 3.2.0
Release Build ?

And if so, will the counter be decremented or will I get a number of gaps in these attempts?