ZWAVE Unknown Device Aeotec Door Window Sensor Gen 7?

Add-ons Bindings
1

Hi,
I included my Aeotec Door Window Sensor Gen 7, but it is shown as unknown device.
Here is the debug log:

2020-09-03 07:08:54.778 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 0A 04 30 03 FF 0B 38 

2020-09-03 07:08:54.780 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 04 30 03 FF 0B 

2020-09-03 07:08:54.781 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=10, callback=0, payload=00 0A 04 30 03 FF 0B 

2020-09-03 07:08:54.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2020-09-03 07:08:54.786 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Application Command Request (ALIVE:VERSION)

2020-09-03 07:08:54.787 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0

2020-09-03 07:08:54.787 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 10: SECURITY not supported

2020-09-03 07:08:54.788 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 10: Received COMMAND_CLASS_SENSOR_BINARY V0 SENSOR_BINARY_REPORT

2020-09-03 07:08:54.788 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 10: Sensor Binary report, type=Unknown, value=255

2020-09-03 07:08:54.789 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent

2020-09-03 07:08:54.790 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255

2020-09-03 07:08:54.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Commands processed 1.

2020-09-03 07:08:54.792 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 10: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@cedd37d.

2020-09-03 07:08:54.793 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2020-09-03 07:08:54.793 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2020-09-03 07:08:54.794 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2020-09-03 07:08:54.794 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

@chris What is the Problem here ? Can you please help ?
Regards
Jörg

2

What version of OpenHAB? Battery powered devices need to be woken up many times to complete binding discovery.

The Z-Wave log viewer may help.

3

Thanks for your hints…
I did the wakeup manual about 40 times… this happens when I do a “wakeup” to node 11

image
image1191Ă—281 19.1 KB

It is now node 11, because I resettet the device, before in the first post it was node 10

4

From this, it doesn’t look like the device is woken up? Are you sure that this is really happening? Maybe it’s just not in this part of the log, but for sure there is no wakeup here…

1 Like
5

That is what I also thought :expressionless:
If I press the “wakeup” button it only says node 11 is updated. But no wakeup…
I did this about 40 times…I think i will send it back…

6

Sometimes the instructions aren’t clear (or even correct!) and I’ve seen comments where the manual requires (for example) a button to be pressed twice, but people find it needs to be pressed 3 times - or held down, or something. You might want to try a few other things to see if you get the wakeup notification in the log.

2 Likes