Ecolink Tilt-zwave2 No longer working

Duggem · July 5, 2021, 8:25pm

I’ve also restarted OH and get the same results.

chris · July 5, 2021, 9:07pm

It looks like the configuration was updated to 255 - how does the device now report?

Duggem · July 5, 2021, 9:17pm

2021-07-05 17:14:28.060 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2021-07-05 17:14:28.060 [DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 174: Transaction COMPLETED
2021-07-05 17:14:28.060 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Response processed after 81ms
2021-07-05 17:14:28.061 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: TID 174: Transaction completed
2021-07-05 17:14:28.061 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: notifyTransactionResponse TID:174 DONE
2021-07-05 17:14:28.062 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2021-07-05 17:14:28.062 [DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 174: Transaction event listener: DONE: DONE -> 
2021-07-05 17:14:28.062 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2021-07-05 17:14:28.062 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2021-07-05 17:14:28.063 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Went to sleep COMPLETE
2021-07-05 17:14:44.414 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 18 03 30 03 FF B1 00 96 
2021-07-05 17:14:44.415 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 FF B1 00 
2021-07-05 17:14:44.416 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 FF B1 00 
2021-07-05 17:14:44.416 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2021-07-05 17:14:44.417 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2021-07-05 17:14:44.417 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2021-07-05 17:14:44.417 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2021-07-05 17:14:44.418 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2021-07-05 17:14:44.418 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2021-07-05 17:14:44.418 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Unknown, value=255
2021-07-05 17:14:44.418 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2021-07-05 17:14:44.419 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2021-07-05 17:14:44.419 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2021-07-05 17:14:44.419 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@115427d.
2021-07-05 17:14:44.420 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-07-05 17:14:44.420 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-07-05 17:14:44.420 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2021-07-05 17:14:44.420 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2021-07-05 17:14:52.799 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0B 00 04 00 18 03 30 03 00 B1 00 69 
2021-07-05 17:14:52.800 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 00 B1 00 
2021-07-05 17:14:52.801 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 00 B1 00 
2021-07-05 17:14:52.801 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2021-07-05 17:14:52.801 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2021-07-05 17:14:52.802 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2021-07-05 17:14:52.802 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2021-07-05 17:14:52.802 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2021-07-05 17:14:52.803 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2021-07-05 17:14:52.803 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Unknown, value=0
2021-07-05 17:14:52.803 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2021-07-05 17:14:52.803 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2021-07-05 17:14:52.804 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2021-07-05 17:14:52.804 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@854799.
2021-07-05 17:14:52.804 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-07-05 17:14:52.804 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2021-07-05 17:14:52.805 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2021-07-05 17:14:52.805 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

nh905 · May 30, 2022, 7:38pm

Have there been any developments on this issue? I recently installed an Openhabian system on a Raspberry Pi 3 - OpenHAB version 3.2.0 and ZWave Binding 3.2.0. I am using an Aeotec Z-Stick Gen5. Since I do not have any switched Z-Wave devices yet, I installed an Aeotoc Range Extender 7. My first real Z-Wave devices are a pair of Ecolink TILTSWAVE2 sensors. I was successfully able to include them - I accepted all the defaults. I am seeing battery readings. Tilting the sensor generates “Sensor Binary report, type=Unknown, value=0/255” debug entries but the Door State continues to show NULL. I opened the sensor cover which caused OpenHAB to set the Tamper Alarm to Alarm and the Door State to Open, but subsequent tilts are not reflected in the Door State.

I have updated Configuration Parameter 2 to 255 and opened the sensor cover to pick up the change. I have restarted OpenHAB. Sensor tilts are still not showing up in the OpenHAB events.log. I found the .xml file associated with the node and will compare it to the .xml files posted earlier but am not sure whether I can safely make changes to my .xml file or what changes are required. I have also reviewed Z-Wave Garage Door Tilt Sensor - Deprecated Point? but am none the wiser.

If more information is required to resolve this issue, should I post additional information hear or start a new topic? I am happy to test and collect any required documentation.

apella12 · May 30, 2022, 10:12pm

Reading this a couple of times I can’t tell if people gave up or they made it work. The crux of the issue is that newer devices use Notifications (alarm), not the binary sensor to report OPEN/Close. The question bounced back and forth was whether the device would send the Notification, not the Binary, if parameter 2 was changed. I would read that if param 2 = 0 the binary would not be sent, just the Notification.

Post a debug level with Parameter 2 at 255 and do an open/close. Then have parameter 2 at zero (you will need to open the device and press the lever to wake and accept - no need to have the binding on Debug mode for this), then do another open/close in Debug.

To ensure we are talking about the same device, on the UI page for the device, expand the thing properties and provide the type/ID pair. I’m guessing it is 0001:0003.

Bob

nh905 · May 30, 2022, 11:28pm

@apella12 thanks for responding to quickly! The manufacturerRef=0001:0003.

Triggered sensor tilt and then back again with Parameter 2 (Sensor Binary Reports) set to 255.

2022-05-30 19:14:14.842 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 04 03 30 03 FF 39
2022-05-30 19:14:14.845 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 FF
2022-05-30 19:14:14.846 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 FF
2022-05-30 19:14:14.848 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-05-30 19:14:14.849 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DONE)
2022-05-30 19:14:14.850 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2022-05-30 19:14:14.851 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2022-05-30 19:14:14.852 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2022-05-30 19:14:14.853 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2022-05-30 19:14:14.854 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 4: Sensor Binary report, type=Unknown, value=255
2022-05-30 19:14:14.855 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2022-05-30 19:14:14.855 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2022-05-30 19:14:14.856 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2022-05-30 19:14:14.857 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@45cd5b.
2022-05-30 19:14:14.858 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:14:14.859 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:14:14.859 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-05-30 19:14:14.860 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-05-30 19:14:19.562 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 04 03 30 03 00 C6
2022-05-30 19:14:19.567 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 00
2022-05-30 19:14:19.568 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 00
2022-05-30 19:14:19.570 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-05-30 19:14:19.571 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DONE)
2022-05-30 19:14:19.573 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2022-05-30 19:14:19.574 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2022-05-30 19:14:19.576 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2022-05-30 19:14:19.577 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2022-05-30 19:14:19.579 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 4: Sensor Binary report, type=Unknown, value=0
2022-05-30 19:14:19.580 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2022-05-30 19:14:19.581 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2022-05-30 19:14:19.582 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2022-05-30 19:14:19.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1e27d55.
2022-05-30 19:14:19.584 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:14:19.586 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:14:19.586 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-05-30 19:14:19.588 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-05-30 19:14:19.695 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 04 03 30 03 00 C6
2022-05-30 19:14:19.697 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 00
2022-05-30 19:14:19.699 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 00
2022-05-30 19:14:19.701 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-05-30 19:14:19.702 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DONE)
2022-05-30 19:14:19.704 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2022-05-30 19:14:19.706 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2022-05-30 19:14:19.707 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2022-05-30 19:14:19.709 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2022-05-30 19:14:19.710 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 4: Sensor Binary report, type=Unknown, value=0
2022-05-30 19:14:19.712 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2022-05-30 19:14:19.713 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2022-05-30 19:14:19.714 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2022-05-30 19:14:19.715 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1c88a34.
2022-05-30 19:14:19.715 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:14:19.716 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:14:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-05-30 19:14:19.717 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Changed Parameter 2 to 0:

2022-05-30 19:15:58.479 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update received
2022-05-30 19:15:58.494 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update ignored config_1_1 to 0 (BigDecimal)
2022-05-30 19:15:58.496 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Configuration update set config_2_1 to 0 (BigDecimal)
2022-05-30 19:15:58.498 [DEBUG] [class.ZWaveConfigurationCommandClass] - NODE 4: Creating new message for application command CONFIGURATION_SET

Tilted the sensor and then back again:

2022-05-30 19:22:37.547 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 04 03 30 03 FF 39
2022-05-30 19:22:37.550 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 FF
2022-05-30 19:22:37.551 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 FF
2022-05-30 19:22:37.552 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-05-30 19:22:37.553 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DONE)
2022-05-30 19:22:37.554 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2022-05-30 19:22:37.555 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2022-05-30 19:22:37.556 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2022-05-30 19:22:37.556 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2022-05-30 19:22:37.557 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 4: Sensor Binary report, type=Unknown, value=255
2022-05-30 19:22:37.558 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2022-05-30 19:22:37.559 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2022-05-30 19:22:37.559 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2022-05-30 19:22:37.560 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@33c1cf.
2022-05-30 19:22:37.561 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:22:37.562 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:22:37.562 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-05-30 19:22:37.563 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2022-05-30 19:22:39.399 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 04 03 30 03 00 C6
2022-05-30 19:22:39.402 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 00
2022-05-30 19:22:39.405 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=4, callback=0, payload=00 04 03 30 03 00
2022-05-30 19:22:39.406 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-05-30 19:22:39.407 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Application Command Request (ALIVE:DONE)
2022-05-30 19:22:39.407 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: resetResendCount initComplete=true isDead=false
2022-05-30 19:22:39.409 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2022-05-30 19:22:39.410 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 4: SECURITY not supported
2022-05-30 19:22:39.410 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 4: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2022-05-30 19:22:39.411 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 4: Sensor Binary report, type=Unknown, value=0
2022-05-30 19:22:39.412 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2022-05-30 19:22:39.413 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2022-05-30 19:22:39.414 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Commands processed 1.
2022-05-30 19:22:39.415 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 4: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1c2907f.
2022-05-30 19:22:39.415 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:22:39.416 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2022-05-30 19:22:39.417 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2022-05-30 19:22:39.417 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.

Nothing related in events.log other than a ConfigStatusInfo type=PENDING around the time I opened the cover on the sensor.

mhilbush · May 30, 2022, 11:47pm

Normally, right after this line

2022-05-30 19:22:37.559 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255

You would expect to see the binding report that it’s updating the channel. Something like this from my log file.

2022-05-29 11:45:54.867 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 26: Updating channel state zwave:device:e56f8b2a43:node26:sensor_binary to ON [OnOffType]

This suggests to me that possibly the sensor_binary channel is not linked to an item, because I think the binding only updates the channel if there’s an item linked to it…

You should be able see in MainUI whether or not the channel is linked to an item.

mhilbush · May 30, 2022, 11:57pm

BTW, I should add that I have one of these sensors and it has always worked. I stopped using it only because I was unhappy with the false reports that would occur whenever the wind blew hard against my garage door…

apella12 · May 31, 2022, 12:06am

It does appear to me that the device only provides a binary sensor report regardless of param 2 setting.

Second, changes to your xml file will not make a difference. What could need to be changed is the xml in the Zwave binding that is generated by the DB. I do not like making DB changes on the devices I do not own without some testing. And I’m confused why @mhilbush device works. The only difference seems to be his was done by textual configuration (see above). That said there is one line in the binding XML for the device that looks odd, maybe that is a problem. I could also try to change the xml in the binding to match the eco window door sensor, but both would require you to either modify a .jar or use maven to compile a binding? Do you feel either is possible? Also trying the textual configuration might be an option, but I have no experience there.

You can let me know in the morning (for me).

Bob

nh905 · May 31, 2022, 2:09pm

@mhilbush all three channels are linked to items. The odd thing is that when I triggered the Tamper Alarm, the Door State also changed from NULL to OPEN. It looks like the Zwave binding is ignoring SENSOR_BINARY and mapping the ALARM to both Tamper Alarm and Door State channels.

nh905 · May 31, 2022, 2:14pm

@apella12 I have searched for a definitive TILTZWAVE2 manual with no success. The ZWAVE Database entry for the v2 sensor links to the 2.5 manual which may explain the confusion.

I would rather avoid going the textual configuration route. I will read up on what it takes to modify the .jar file or recompile using Maven but expect it is something I can manage.

chips · May 31, 2022, 3:44pm

@nh905 I think you are on the right track! First a disclaimer: I only have an academic interest in this getting resolved. I’ve used this tilt sensor successfully for many years under openHAB v1, v2, and v3, but last month I moved it to Home Assistant (which I’m thrilled with). Also this thread it getting pretty long, and I made some comments above which I believe are still accurate, so I’ll be repeating some of them here.

I have used the Ecolink Tilt-Zwave2 successfully for many years.
I had the same exact issues and symptoms as described in this discussion when I upgraded to OH3.
The changes referred to above seem to have been made based on the assumption that the Tilt-Zwave2 provides the alarm command class for the door sensor. It does not.
Perhaps these changes were valid for other versions of this device, but they are not valid for this one.
This device has a tamper alarm (activated by opening the case) that has nothing to do with the open/closed door sensor.
The database is wrong. It references (and seems to rely on) the “Updated Manual” Tilt-ZWave-Plus-Manual-R1-04-021816kgs.pdf which is not for this device. The manual is for product type 4 (see bottom page 4). This discussion is about is product type 1, not product type 4.
I speculate that at some point TILTZWAVE2 (product type 1) was erroneously updated to reflect the characteristics from the manual for TILT-ZWAVE2.5-ECO (product type 4).

Last year when I saw this thread was going nowhere, I reverted the XML for this device and it worked great. These are the notes I made at the time:

Garage door not working because tiltzwave2_0_0.xml was changed six months ago by some misguided soul that seemd to think that the tamper alarm and door open were the same thing and made both of them an alarm. Reverted to the old version from github using:

$ jar -uf org.openhab.binding.zwave-3.0.1.jar OH-INF/thing/eco/tiltzwave2_0_0.xml

Copied .jar file to /usr/share/openhab/addons (next to .kar addons file) and it automagically loaded. Removed Thing and re-added it

I’m not necessarily recommending this approach to others. I’m only providing this information as a datapoint of what kept my system happy and hope it points you in the right direction for a real fix (updating the database or whatever).

apella12 · May 31, 2022, 5:45pm

Here are two different XML versions. The last digit (1 or 2) was just so I could keep them separate. They will need to be changed to “0” prior to merging (They need to overwrite the file that is in there now). It would be great to be able to run the same tests as above with each modified jar. For reference the current XML
tiltzwave2_0_0.xml (4.4 KB)

This XML was changed to use the Binary like the window/door 2.0 device. (I had the 2.5 eco versions of both the tilt and the door and configuration-wise they were identical so this should work)
tiltzwave2_0_1.xml (4.3 KB)
This version removed a property that looked odd and still tries to use the more modern Notification process. I’d be more comfortable with this fix, if it works.
tiltzwave2_0_2.xml (4.3 KB)

Since @chips basically outlined the jar modification command that might be the easiest path. This is an old thread, but has more detail (note replace ESH-INF with OH-INF like @chips did)

I’d grab the latest binding from here. Do the mods then follow the steps here to uninstall the UI binding and add to the Addons folder.

Good luck

Bob

chris · May 31, 2022, 7:57pm

I guess it’s not “wrong” as there seems to be two versions - so it seems to be correct for one version, and incompatible with the other - we need to have two database entries to resolve it.

Do these two versions have different version numbers? They should do - so we should be able to add both to the database which would solve the issue - but we need to know how to identify the two versions…

apella12 · May 31, 2022, 9:54pm

Since you are back I have a question re this line in the DB xml for the Tilt 2.0. Could this potentially be suppressing the device from sending the Notification (Alarm)? One of my XML’s above took it out (to see what would happen). But it is easier to just ask.

<property name="commandClass:COMMAND_CLASS_ALARM">getSupported=false</property>

Bob

chris · May 31, 2022, 9:56pm

No - changing the XML will not impact what the device does. If the device isn’t sending data, then it’s a device configuration issue most likely.

apella12 · May 31, 2022, 10:04pm

@nh905 Based this

Your task is cut in half, just try the first xml. assuming that works (I expect it to) we’ll have to figure out how to get two entries in the DB.

Bob

apella12 · May 31, 2022, 10:15pm

Thanks. I tried to follow isSupported logic (for version 2) in the Alarm CC but could not, so just figured it might be worth a try (with a willing tester) to keep the rest of the DB for the device as is. With my limited knowledge, it is a little unusual to see that line. It’s not in any of the other Eco devices I checked.

Anyway thanks again

Bob

nh905 · June 1, 2022, 8:16pm

@chips thanks for the confirmation and the streamlined instructions - I read the full instructions and got lost in the weeds.

@apella12 I decided to stick with the current binding to avoid making too many changes at once. I created a newbinding folder, created the OH-INF/thing/eco subfolder structure, and saved your first XML file as tiltzwave2_0_0.xml. I returned to the newbinding folder, copied over the current org.openhab.binding.zwave-3.2.0.jar, then ran

jar -uf org.openhab.binding.zwave-3.2.0.jar OH-INF/thing/eco/tiltzwave2_0_0.xml

I unpacked the updated .jar file and verified that the tiltzwave2_0_0.xml matches your first XML file. It looks like you moved sensor_door before alarm_tamper, changed the sensor_door label and OpenClosedType, and deleted the following later in the XML:

<property name="commandClass:COMMAND_CLASS_ALARM">getSupported=false</property>

To install the modified binding and pick up the new XML definition (updated 2022/06/02 based on Bob’s input and testing):

uninstall the current Z-Wave binding (follow steps to add the Z-Wave Binding but click on REMOVE)
copy the modified Zwave binding in the addons folder (for me, /usr/share/openhab/addons)
wait for OpenHAB to automatically install the modified Zwave binding
in Things, find the tilt sensor, and “Delete Thing” at bottom of screen
remove the tilt sensor battery
in Things, click on the Add button, select the Z-Wave binding, and click on Scan to enter inclusion mode
install tilt sensor battery to include the sensor
wait for the tilt sensor to appear in the Inbox
add the sensor (the existing channels and item links were still defined)
set up Z-Wwave debug logging
tilt the sensor

apella12 · June 1, 2022, 9:25pm

Sounds right.

I didn’t have to move the sensor door, but was trying to visually line up with the 2.0 window/door.

Bob

edit: Fine to stick with the 3.2 binding. The 3.3 snapshot has some enhancements re: battery device inclusion that could help, but understand trying to mimimize change here.

edit 2: Read the steps too quickly last night. You most likely will have to go into karaf to;
feature:install openhab-transport-serial
I like to add before I drop the binding in the addons folder, to avoid an error message. (The feature is added automatically when the binding is installed via UI, but not when dropped in.

Also run both options on parameter 2 in debug mode.

Thanks for your efforts on this.