[zwave] Difficulties getting devolo motion sensor to work

Dominik_Bernhardt · June 10, 2018, 7:34pm

I tried to include a Devolo motion sensor (MT02647) into my openhab installation. I can easily include the sensor via paper UI and I also get reports for temperature and luminance. However the binary sensor item never triggers.
The motion detector seems to work correctly as I always get a temperature, luminance and battery report when I walk by the sensor.

Any ideas? Any experience with this device?

I’m using openhab 2.2.0 snapshot Build #988

Dominik

mueslee · June 10, 2018, 7:38pm

first of all i would try to move to openHAB 2.3 and give it a try again
of course this is only possible if you don’t have any reason to stick to the snapshot

Dominik_Bernhardt · June 10, 2018, 7:40pm

I’m a little hesitant to move to 2.3 as I would also need to move to the knx 2 binding. But I will give it a try with a test. Openhab is running in a docker container anyhow.

5iver · June 10, 2018, 7:42pm

Update OH to 2.3 release or 2.4 snapshot. You might try the 2.4 snapshot zwave binding, but it probably will not work with the version of OH that you’re running.

Dominik_Bernhardt · June 11, 2018, 6:45pm

I updated to 2.3 and I get the same behavior
The z-wave device works and reports battery, temperature and luminance when I walk by the sensor but no reaction of the binary_sensor.

chris · June 11, 2018, 7:02pm

What is shown in the debug logs? The first thing to work out is if the device is sending data, but the binding isn’t processing it, or, if the device just isn’t sending anything…

Once we know this, we can look at how to solve the problem…

Dominik_Bernhardt · June 11, 2018, 8:09pm

Below is the debug output. Node 9 is the motion sensor. According to this log output the channel and the associated item should be set to on. However the item is never updated.

The associated item looks like this:

Contact carport_motion_sensor “Carport Bewegungsmelder” (g_persist_sensordata) {channel=“zwave:device:3847a844:node9:sensor_binary”}

 2018-06-11 22:04:28.483 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Application Command Request (ALIVE:DETAILS)
2018-06-11 22:04:28.484 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Incoming command class MULTI_CMD
2018-06-11 22:04:28.484 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Received Multi-Command Request
2018-06-11 22:04:28.484 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Incoming command class BATTERY
2018-06-11 22:04:28.484 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Calling handleApplicationCommandRequest.
2018-06-11 22:04:28.484 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 9: Received Battery Request
2018-06-11 22:04:28.484 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 9: Battery report value = 100
2018-06-11 22:04:28.484 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-06-11 22:04:28.485 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-06-11 22:04:28.485 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2018-06-11 22:04:28.486 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:3847a844:node9:battery-level to 100 [DecimalType]
2018-06-11 22:04:28.487 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Incoming command class SENSOR_BINARY
2018-06-11 22:04:28.487 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Calling handleApplicationCommandRequest.
2018-06-11 22:04:28.487 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 9: Received SENSOR_BINARY command V2
2018-06-11 22:04:28.487 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12
2018-06-11 22:04:28.487 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION
2018-06-11 22:04:28.487 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 9: Sensor Binary report, type=Motion, value=255
2018-06-11 22:04:28.487 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2018-06-11 22:04:28.488 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2018-06-11 22:04:28.488 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2018-06-11 22:04:28.488 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:3847a844:node9:sensor_binary to ON [OnOffType]
2018-06-11 22:04:28.488 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Incoming command class SENSOR_MULTILEVEL
2018-06-11 22:04:28.489 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Calling handleApplicationCommandRequest.
2018-06-11 22:04:28.489 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
2018-06-11 22:04:28.490 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Sensor Multi Level REPORT received
2018-06-11 22:04:28.490 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Sensor Type = Luminance(3), Scale = 0
2018-06-11 22:04:28.490 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Sensor Value = 3
2018-06-11 22:04:28.490 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2018-06-11 22:04:28.490 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2018-06-11 22:04:28.491 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 3
2018-06-11 22:04:28.491 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:3847a844:node9:sensor_luminance to 3 [DecimalType]
2018-06-11 22:04:28.493 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Incoming command class SENSOR_MULTILEVEL
2018-06-11 22:04:28.495 [DEBUG] [dclass.ZWaveMultiCommandCommandClass] - NODE 9: Calling handleApplicationCommandRequest.
2018-06-11 22:04:28.495 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V5
2018-06-11 22:04:28.496 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Sensor Multi Level REPORT received
2018-06-11 22:04:28.496 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Sensor Type = Temperature(1), Scale = 1
2018-06-11 22:04:28.496 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 9: Sensor Value = 71
2018-06-11 22:04:28.496 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
2018-06-11 22:04:28.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2018-06-11 22:04:28.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 71
2018-06-11 22:04:28.497 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 9: Sensor is reporting scale 1, requiring conversion to 0. Value is now 71.
2018-06-11 22:04:28.497 [DEBUG] [converter.ZWaveCommandClassConverter] - Converted temperature from 71F to 21.7C
2018-06-11 22:04:28.497 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Updating channel state zwave:device:3847a844:node9:sensor_temperature to 21.7 [DecimalType]
2018-06-11 22:04:28.498 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 11: Transaction not completed: node address inconsistent.  lastSent=11, incoming=255
2018-06-11 22:04:39.355 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 0A 0A 32 02 21 74 00 00 1E 6B 00 00 FB 
2018-06-11 22:04:39.356 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-06-11 22:04:39.356 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 0A 0A 32 02 21 74 00 00 1E 6B 00 00 FB 
2018-06-11 22:04:39.356 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 0A 0A 32 02 21 74 00 00 1E 6B 00 00 FB 
2018-06-11 22:04:39.357 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 0A 0A 32 02 21 74 00 00 1E 6B 00 00

chris · June 11, 2018, 8:15pm

Can you please paste the log with code fences rather than as a quote (or whatever). This has screwed up the formatting. Easiest way is to use the </> button to format - unfortunately I can’t edit your post as there are now extra > characters on each line…

Dominik_Bernhardt · June 11, 2018, 8:18pm

Thanks for the hint. I have updated the post.

chris · June 11, 2018, 8:25pm

Thanks .

According to the log, it does seem to be updating (see above). At least, it is receiving an ON state. Maybe the device doesn’t send an OFF, or maybe the binding isn’t processing the OFF properly? I’d suggest to check the logs to see which one it is…