Aeotec TriSensor (ZWA005) motion not working

Jacob_Weigand · August 2, 2019, 3:20pm

Item: Aeotec TriSensor, Z-Wave Plus S2 Motion, Temperature, Light Sensor, 3-in 1

I have successfully paired this device with Openhab. The temperature, luminance, and battery level work perfectly. Openhab doesn’t like the motion sensor though. Items linked to this channel never change from UNDEF.

I have turned on the ZWave debugging log and I can see that the motion sensor is being reported. A value of 255 is set when there is motion and 0 when there is none. I think this might be the root of the issue. Openhab expects this to be a switch (On/Off) value and not a numeric one.

2019-08-02 09:55:00.607 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 7: Sensor Binary report, type=Motion, value=255

2019-08-02 09:55:02.889 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION

2019-08-02 09:55:02.891 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 7: Sensor Binary report, type=Motion, value=255

2019-08-02 09:55:04.040 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION

2019-08-02 09:55:04.042 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 7: Sensor Binary report, type=Motion, value=255

2019-08-02 09:55:33.427 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION

2019-08-02 09:55:33.430 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 7: Sensor Binary report, type=Motion, value=0

2019-08-02 09:55:34.608 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION

2019-08-02 09:55:34.610 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 7: Sensor Binary report, type=Motion, value=0

The only options I have in the device configuration is “0x00” or “0xFF” aka 0 and 255 in hex for my triggered and cleared options. I am not sure how to get what I am seeing in the ZWave logs to translate properly to On and Off in the device’s channel.

I don’t know how channels are defined/created when adding ZWave devices (Some Database?), but I think something needs to be updated for this device. Can someone point in the direction of documentation to fix this myself or who to talk to about getting this fixed?

chris · August 2, 2019, 4:09pm

Please can you provide the log and I will take a look.

I think it looks ok, but it is here if you want to check. The database guide is here.

Jacob_Weigand · August 2, 2019, 4:14pm

Here is some more of my logs.

2019-08-02 11:06:46.779 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-08-02 11:06:46.783 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-08-02 11:06:46.700 [vent.ItemStateChangedEvent] - zwave_serial_zstick_b66250fb_serial_sof changed from 13560 to 13561

2019-08-02 11:10:53.891 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0C 00 04 08 07 06 31 05 01 2A 03 2A C8 

2019-08-02 11:10:53.914 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=8, payload=08 07 06 31 05 01 2A 03 2A 

2019-08-02 11:10:53.920 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=8, payload=08 07 06 31 05 01 2A 03 2A 

2019-08-02 11:10:53.933 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2019-08-02 11:10:53.936 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)

2019-08-02 11:10:53.941 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false

2019-08-02 11:10:53.944 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0

2019-08-02 11:10:53.948 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL

2019-08-02 11:10:53.951 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_SENSOR_MULTILEVEL V7 SENSOR_MULTILEVEL_REPORT

2019-08-02 11:10:53.956 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 7: Sensor Type = Temperature(1), Scale = 1

2019-08-02 11:10:53.959 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 7: Sensor Value = 81

2019-08-02 11:10:53.964 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2019-08-02 11:10:53.967 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 81

2019-08-02 11:10:53.973 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:b66250fb:node7:sensor_temperature to 81 °F [QuantityType]

2019-08-02 11:10:53.986 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.

2019-08-02 11:10:53.992 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1b91640.
2019-08-02 11:10:55.100 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)

2019-08-02 11:10:55.104 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false

2019-08-02 11:10:55.108 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_SENSOR_MULTILEVEL, endpoint 0

2019-08-02 11:10:55.121 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_SENSOR_MULTILEVEL

2019-08-02 11:10:55.125 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_SENSOR_MULTILEVEL V7 SENSOR_MULTILEVEL_REPORT

2019-08-02 11:10:55.129 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 7: Sensor Type = Temperature(1), Scale = 1

2019-08-02 11:10:55.133 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 7: Sensor Value = 81

2019-08-02 11:10:55.136 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent

2019-08-02 11:10:55.138 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_MULTILEVEL, value = 81

2019-08-02 11:10:55.141 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:b66250fb:node7:sensor_temperature to 81 °F [QuantityType]

2019-08-02 11:10:55.148 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.

2019-08-02 11:10:55.150 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@f6f905.

2019-08-02 11:10:55.153 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-02 11:10:55.156 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-02 11:10:55.158 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-08-02 11:10:55.160 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-08-02 11:10:55.061 [vent.ItemStateChangedEvent] - zwave_serial_zstick_b66250fb_serial_sof changed from 13562 to 13563
2019-08-02 11:12:52.239 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2019-08-02 11:12:52.242 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)

2019-08-02 11:12:52.245 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false

2019-08-02 11:12:52.248 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_BASIC, endpoint 0

2019-08-02 11:12:52.252 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_BASIC

2019-08-02 11:12:52.255 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_BASIC V0 BASIC_SET

2019-08-02 11:12:52.258 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 7: Basic report, value = 0

2019-08-02 11:12:52.260 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveCommandClassValueEvent

2019-08-02 11:12:52.263 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_BASIC, value = 0

2019-08-02 11:12:52.266 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.

2019-08-02 11:12:52.268 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@16c1d28.

2019-08-02 11:12:52.270 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-02 11:12:52.272 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-02 11:12:52.275 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-08-02 11:12:52.277 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-08-02 11:12:52.252 [vent.ItemStateChangedEvent] - zwave_serial_zstick_b66250fb_serial_sof changed from 13569 to 13570

2019-08-02 11:12:54.709 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 08 07 04 30 03 FF 0C 3A 

2019-08-02 11:12:54.728 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=8, payload=08 07 04 30 03 FF 0C 

2019-08-02 11:12:54.734 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=7, callback=8, payload=08 07 04 30 03 FF 0C 

2019-08-02 11:12:54.738 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null

2019-08-02 11:12:54.741 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Application Command Request (ALIVE:DONE)

2019-08-02 11:12:54.745 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: resetResendCount initComplete=true isDead=false

2019-08-02 11:12:54.749 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0

2019-08-02 11:12:54.753 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 7: SECURITY NOT required on COMMAND_CLASS_SENSOR_BINARY

2019-08-02 11:12:54.757 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 7: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT

2019-08-02 11:12:54.761 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 12

2019-08-02 11:12:54.764 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is MOTION

2019-08-02 11:12:54.768 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 7: Sensor Binary report, type=Motion, value=255

2019-08-02 11:12:54.772 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent

2019-08-02 11:12:54.775 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 255

2019-08-02 11:12:54.777 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Commands processed 1.

2019-08-02 11:12:54.779 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 7: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@dd414e.

2019-08-02 11:12:54.781 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-02 11:12:54.783 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-08-02 11:12:54.785 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2019-08-02 11:12:54.787 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

2019-08-02 11:12:54.720 [vent.ItemStateChangedEvent] - zwave_serial_zstick_b66250fb_serial_sof changed from 13570 to 13571

Is this enough or are you looking for something more specific?

chris · August 2, 2019, 4:23pm

The device isn’t sending the ALARMs that the binding is expecting - I’m not sure if this is something that you have disabled? The ALARM messages are normally the ones used as they are more modern than the BINARY_SENSOR messages.

Maybe by enabling the BINARY_SENSOR, the device has disabled ALARM - I’m not sure.

Jacob_Weigand · August 2, 2019, 4:48pm

@chris I don’t see any kind of setting to disable the ALARM. This is my configuration

chris · August 2, 2019, 4:52pm

As I suggested, maybe it is disabled when you enable the BINAR_SENSOR? Try disabling the Binary Sensor and see if it instead sends the Alarm. This defaults to disabled, and I suspect most people using this device don’t change this - the idea should be it works without having to make too many changes to configuration.

Jacob_Weigand · August 2, 2019, 5:02pm

@chris Thank you so very much. That was exactly the issue. I changed the Binary Sensor to Disabled and it is now working as expected.

chris · August 2, 2019, 10:13pm

I have changed the name of this parameter with the intention of avoiding confusion about how this works…

For others coming across this thread, the binding requires this parameter to be set to the default which is to send the Alarm / Notification reports.

Lukas_1st · September 22, 2019, 12:14am

Hi,

I try to add this sensor to my z-wave network but without success. Maybe you have the same problems and you know solution. To the point, I have successfully paired this device with my network (and I have got Online status). But I have not received any data from the sensors of this device (neither from motion sensor nor from temperature). I have tried to wakeup the device to pressing the action button and in log I see that transmition beetwen controller and device is canceled after each atempt. At the end system has marked node as dead and has changed status of the item to offline - not communicate with controller.

Do you have any idea what could be wrong? I checked the firmware version, it is 2.15.

chris · September 22, 2019, 9:11am

Please provide the log.

Lukas_1st · September 22, 2019, 10:40am

Here is my log node12.txt (88.9 KB)
We are talking about node 12.

Lukas_1st · September 23, 2019, 9:58am

I have noticed that in the 1st Association Group (Lifeline) I do not have a controller assigned. And I cannot to change it because every time I get communication error with the controller. I have got two devices and each of them works (more precisely does not work) in the same way.

chris · September 23, 2019, 1:58pm

If you are using the 2.5 SNAPSHOT then it will be defined. There is a bug in the UI that may cause this to look like it’s not defined.

Lukas_1st · September 23, 2019, 5:37pm

Ok, but I understand there is no connection with my problem. Have you checked the log? Do you have any idea what could be wrong?

chris · September 23, 2019, 5:43pm

Ok, sorry, but i was only responding to your question.

Yes, but it’s quite short so it’s hard really to know what is happening.

Not really. From the log it looks like the device goes to sleep but the binding is busy doing other things. The log is very short, and only contains a single transaction so it’s hard to know what is happening since this issue should resolve itself on the next wake.

Lukas_1st · September 23, 2019, 6:09pm

So, maybe I will send you longer log. Before I will try to wake up the device a couple times. But I have already checked the log and I have not noticed any communication beetween the device and the controller (after these atempts). It is weird because LED indicates the device transmites something.

chris · September 23, 2019, 6:15pm

Yes, please wake it a number of times over a period of a few minutes.

But there is communication from the device in the log .

Eg -:

Lukas_1st · September 23, 2019, 10:09pm

Maybe I should more precise I have not noticed any communication which has been initiated by the device without manual waking up.

chris · September 23, 2019, 10:11pm

Ok, that might just mean that the wakeup period is not been set. This can only be set by initially manually waking the device. I see the binding trying to set this in the log, but it is not acknowledged.

Lukas_1st · September 24, 2019, 5:17pm

Here is the new log openhab_log.txt (429.6 KB). I have waked up device a couple times and I have not received any response. This sensor supports S2, maybe this is the cause all these communication problems. What do you think?