Ecolink Tilt-zwave2 No longer working

tsmarks · September 27, 2020, 6:12pm

Yes, I have changed param 2 - “Sensor Binary Reports” to “Not Sent”. I have also tried setting param 1 to “Not Sent”

mhilbush · September 27, 2020, 10:02pm

FWIW, I’m running build 2.5.7 build 171. My item is defined like this.

Contact GarageDoor_Tilt_Sensor "Garage Door Status [MAP(door.map):%s]" { channel="zwave:device:zstick:node24:sensor_door" }

Config Parameter 1 is set to Not Sent

Config Parameter 2 is set to Sent

The device is running firmware v 2.0.

In the event log, I’m getting open and closed events.

2020-09-22 12:07:05.101 [vent.ItemStateChangedEvent] - GarageDoor_Tilt_Sensor changed from CLOSED to OPEN
2020-09-22 12:07:59.757 [vent.ItemStateChangedEvent] - GarageDoor_Tilt_Sensor changed from OPEN to CLOSED
2020-09-22 16:16:00.234 [vent.ItemStateChangedEvent] - GarageDoor_Tilt_Sensor changed from CLOSED to OPEN
2020-09-22 16:18:09.477 [vent.ItemStateChangedEvent] - GarageDoor_Tilt_Sensor changed from OPEN to CLOSED
2020-09-22 18:01:59.359 [vent.ItemStateChangedEvent] - GarageDoor_Tilt_Sensor changed from CLOSED to OPEN
2020-09-22 21:11:38.187 [vent.ItemStateChangedEvent] - GarageDoor_Tilt_Sensor changed from OPEN to CLOSED
2020-09-22 21:13:33.964 [vent.ItemStateChangedEvent] - GarageDoor_Tilt_Sensor changed from CLOSED to OPEN

mhilbush · September 27, 2020, 10:59pm

I upgraded to 2.5.10 build 237. I’m still getting open and close events.

mhilbush · September 27, 2020, 11:20pm

Here’s the open event

2020-09-27 18:55:05.482 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 18 03 30 03 FF 25
2020-09-27 18:55:05.482 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 FF
2020-09-27 18:55:05.483 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 FF
2020-09-27 18:55:05.483 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - lastTransaction null
2020-09-27 18:55:05.483 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:REQUEST_NIF)
2020-09-27 18:55:05.483 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2020-09-27 18:55:05.483 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2020-09-27 18:55:05.483 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2020-09-27 18:55:05.483 [DEBUG] [rotocol.commandclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Unknown, value=255
2020-09-27 18:55:05.483 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2020-09-27 18:55:05.483 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=255
2020-09-27 18:55:05.483 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Updating channel state zwave:device:zstick:node24:sensor_door to OPEN [OpenClosedType]
2020-09-27 18:55:05.484 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2020-09-27 18:55:05.484 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@4320173c.

And the close event

2020-09-27 18:56:00.945 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 18 03 30 03 00 DA
2020-09-27 18:56:00.945 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 00
2020-09-27 18:56:00.946 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=24, callback=0, payload=00 18 03 30 03 00
2020-09-27 18:56:00.946 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - lastTransaction TID 503: [WAIT_REQUEST] priority=NonceResponse, requiresResponse=true, callback: 88
2020-09-27 18:56:00.946 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:REQUEST_NIF)
2020-09-27 18:56:00.946 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2020-09-27 18:56:00.946 [DEBUG] [.openhab.binding.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2020-09-27 18:56:00.946 [DEBUG] [e.internal.protocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2020-09-27 18:56:00.946 [DEBUG] [rotocol.commandclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Unknown, value=0
2020-09-27 18:56:00.946 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2020-09-27 18:56:00.946 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_SENSOR_BINARY, value=0
2020-09-27 18:56:00.946 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 24: Updating channel state zwave:device:zstick:node24:sensor_door to CLOSED [OpenClosedType]
2020-09-27 18:56:00.946 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2020-09-27 18:56:00.947 [DEBUG] [ng.zwave.internal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@1597741a.

chris · September 28, 2020, 10:04am

I’m not sure why the database has changed, but it seems from Marks logs that it is also now incorrect, and it probably needs to be changed back. I will see if I can sort this out over the next day or two.

mhilbush · September 28, 2020, 11:38am

Ah, I see. The database has sensor_door associated with COMMAND_CLASS_ALARM_V1. But the device sends COMMAND_CLASS_SENSOR_BINARY.

Looks like the database change was very recent.

chris · September 28, 2020, 12:28pm

Yes, I don’t WHEN it happened, but I don’t know WHY

tsmarks · October 6, 2020, 3:38pm

I can now verify the battery level does change, even if the other values do not.

So it makes a good z-wave enabled CR123A battery tester!

tsmarks · November 5, 2020, 2:14am

Just upgraded to 2.5.10, but no changes.
@chris Any luck with sorting out the changes in the Database?

W_A · December 29, 2020, 12:35am

Having the same issue. Is there any update/workaround?

chris · December 29, 2020, 9:13am

What exactly is your issue, and what have your tried? What version of the bindings are you using and what is in the log?

W_A · December 29, 2020, 8:15pm

Hi, Same issue as described by @tsmarks. Sensor worked in the past, but now “Door State [Deprecated]” does not get any updates.

Sensor sends COMMAND_CLASS_SENSOR_BINARY (values 0/255 when door is closed/open)

2020-12-29 15:00:22.033 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2020-12-29 15:00:22.033 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2020-12-29 15:00:22.033 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2020-12-29 15:00:22.033 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2020-12-29 15:00:22.033 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2020-12-29 15:00:22.033 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Unknown, value=255
2020-12-29 15:00:22.033 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2020-12-29 15:00:22.033 [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
2020-12-29 15:00:22.033 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2020-12-29 15:00:22.033 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@10fde9f7.

2020-12-29 15:00:24.455 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2020-12-29 15:00:24.455 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2020-12-29 15:00:24.455 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2020-12-29 15:00:24.455 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2020-12-29 15:00:24.455 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_SENSOR_BINARY V1 SENSOR_BINARY_REPORT
2020-12-29 15:00:24.455 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 24: Sensor Binary report, type=Unknown, value=0
2020-12-29 15:00:24.455 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2020-12-29 15:00:24.455 [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
2020-12-29 15:00:24.456 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2020-12-29 15:00:24.456 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@3d569239.

As per this topic and

it looks like openHAB expects COMMAND_CLASS_ALARM instead.

For reference this captures tampering (opening and closing the sensor cover):

2020-12-29 15:00:34.089 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2020-12-29 15:00:34.089 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2020-12-29 15:00:34.090 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2020-12-29 15:00:34.090 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2020-12-29 15:00:34.090 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 24: Received COMMAND_CLASS_ALARM V2 NOTIFICATION_REPORT
2020-12-29 15:00:34.090 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: ALARM report - 0 = 255
2020-12-29 15:00:34.090 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 24: Alarm Type = BURGLAR (0)
2020-12-29 15:00:34.090 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2020-12-29 15:00:34.090 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2020-12-29 15:00:34.090 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter processing ALARM
2020-12-29 15:00:34.090 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Updating channel state zwave:device:6d394c00:node24:alarm_tamper to ON [OnOffType]
2020-12-29 15:00:34.090 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 24: Alarm converter processing ALARM
2020-12-29 15:00:34.090 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Updating channel state zwave:device:6d394c00:node24:sensor_door to OPEN [OpenClosedType]
2020-12-29 15:00:34.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2020-12-29 15:00:34.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@218d0dec.
2020-12-29 15:00:41.234 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Application Command Request (ALIVE:DONE)
2020-12-29 15:00:41.234 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2020-12-29 15:00:41.234 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Is awake with 0 messages in the queue
2020-12-29 15:00:41.234 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Start sleep timer at 1000ms
2020-12-29 15:00:41.234 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveNodeStatusEvent
2020-12-29 15:00:41.236 [DEBUG] [ve.internal.protocol.ZWaveController] - NODE 24: Node Status event - Node is AWAKE
2020-12-29 15:00:41.236 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Commands processed 1.
2020-12-29 15:00:41.236 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@31325ddb.
2020-12-29 15:00:41.734 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: WakeupTimerTask 0 Messages waiting, state DONE
2020-12-29 15:00:42.235 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: WakeupTimerTask 0 Messages waiting, state DONE
2020-12-29 15:00:42.235 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: No more messages, go back to sleep
2020-12-29 15:00:42.235 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 24: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2020-12-29 15:00:42.235 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: SECURITY not supported
2020-12-29 15:00:42.235 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Command Class COMMAND_CLASS_WAKE_UP is NOT required to be secured
2020-12-29 15:00:42.235 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: sendTransaction org.openhab.binding.zwave.internal.protocol.transaction.ZWaveCommandClassTransactionPayload@2074441a
2020-12-29 15:00:42.236 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Bump transaction 949 priority from Immediate to Immediate
2020-12-29 15:00:42.236 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Adding to device queue
2020-12-29 15:00:42.236 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Added 949 to queue - size 2
2020-12-29 15:00:42.237 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 24: Sending REQUEST Message = 01 09 00 13 18 02 84 08 25 87 D1
2020-12-29 15:00:42.245 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 24: sentData successfully placed on stack.
2020-12-29 15:00:42.245 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: TID 949: Transaction not completed
2020-12-29 15:00:42.263 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 24: SendData Request. CallBack ID = 135, Status = Transmission complete and ACK received(0)
2020-12-29 15:00:42.263 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: resetResendCount initComplete=true isDead=false
2020-12-29 15:00:42.263 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: Response processed after 26ms
2020-12-29 15:00:42.263 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: TID 949: Transaction completed
2020-12-29 15:00:42.263 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 24: notifyTransactionResponse TID:949 DONE
2020-12-29 15:00:42.263 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 24: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2020-12-29 15:00:42.264 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 24: Went to sleep COMPLETE

chris · December 30, 2020, 8:36am

Yes, I normally use the notification commands and it seems that this is working.

Note: Please use code fences to format logs - or format using the </> button. It makes reading and processing logs much much easier.

W_A · December 31, 2020, 5:43am

Sensor sends:

COMMAND_CLASS_SENSOR_BINARY - for door state change
COMMAND_CLASS_ALARM - for tampering

When openHAB receives:

COMMAND_CLASS_SENSOR_BINARY - ignores it, instead of updating sensor_door as per value 0/255
COMMAND_CLASS_ALARM - updates both sensor_door & alarm_tamper

Linking both sensor_door & alarm_tamper with COMMAND_CLASS_ALARM is visible in the database and logs and possibly the explanation why OH ignores doors being opened or closed.

Juergen_Pechmann · December 31, 2020, 1:36pm

Hi,
I have the same issue with OH3.0.0 and Z-Wave-Device MT02648 Door/Window Contact

Received COMMAND_CLASS_SENSOR_BINARY V0 SENSOR_BINARY_REPORT
Sensor Binary report, type=Unknown, value=0

and channel (Sensor_door Contact) ignore the change of value 0/255.

sihui · December 31, 2020, 3:29pm

We are talking here about a different device, please open a new topic.

tsmarks · January 6, 2021, 10:18pm

Binding 2.5.11 same problem.

Thanks

tsmarks · January 10, 2021, 6:21pm

@chris is there any reason we can’t use the code from the 2.5.4 version that worked and paste that back in the database? Was there a large structure change?

chips · March 5, 2021, 5:05pm

I have used the Ecolink Tilt-Zwave2 successfully for many years.
I am having the same exact issues and symptoms as described in this discussion since upgrading to OH3. It’s no longer functional.
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 on this one.
This device has a tamper alarm (activated by opening the case) that has nothing to do with the open/closed door sensor.

I highly recommend reverting to the old version.

chris · March 6, 2021, 10:00am

Why?

The binding uses the ALARM commands - as discussed above. These are more informative than the older style commands, and probably you need to change a config to send these commands instead of the old commands.

Strange - according to the database, it does. So either you have a different device, or the database is wrong. Maybe you can help with information to resolve this?