Ecolink dwzwave2.5 door contact

zwave
Tags: #<Tag:0x00007f1e57d2fd58>
(Scott Hogan) #1

I’m trying to get my garage door sensors working again. My laptop fell asleep and I lost all of my zwave things. It had been working pretty flawlessly for about 6 months. I recreated/imported all of my zwave things, but can’t get my ecolink dwzwave2.5 sensors to work. There are two actually node 35 and 36. I ended up exluding and re-including with no success. Help appreciated. Items file snipped below the log.

Log snippet:
2019-04-27 14:05:40.730 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2019-04-27 14:05:40.730 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-04-27 14:05:40.730 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-04-27 14:05:40.914 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0A 00 04 00 24 04 30 03 00 FF 1D
2019-04-27 14:05:40.916 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=36, callback=0, payload=00 24 04 30 03 00 FF
2019-04-27 14:05:40.916 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=36, callback=0, payload=00 24 04 30 03 00 FF
2019-04-27 14:05:40.917 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-04-27 14:05:40.918 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Application Command Request (ALIVE:DONE)
2019-04-27 14:05:40.918 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 36: resetResendCount initComplete=true isDead=false
2019-04-27 14:05:40.918 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 36: Incoming command class COMMAND_CLASS_SENSOR_BINARY, endpoint 0
2019-04-27 14:05:40.919 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 36: SECURITY not supported
2019-04-27 14:05:40.919 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 36: Received COMMAND_CLASS_SENSOR_BINARY V2 SENSOR_BINARY_REPORT
2019-04-27 14:05:40.919 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Processing Sensor Type 255
2019-04-27 14:05:40.920 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - Sensor Type is null
2019-04-27 14:05:40.920 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 36: Sensor Binary report, type=Unknown, value=0
2019-04-27 14:05:40.920 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 36: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2019-04-27 14:05:40.921 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 36: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SENSOR_BINARY, value = 0
2019-04-27 14:05:40.921 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 36: Updating channel state zwave:device:9305b102:node36:sensor_binary to OFF [OnOffType]
2019-04-27 14:05:40.922 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Commands processed 1.
2019-04-27 14:05:40.924 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 36: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@304e3587.
2019-04-27 14:05:40.924 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-04-27 14:05:40.924 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-04-27 14:05:40.924 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-04-27 14:05:40.924 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-04-27 14:05:41.719 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 00 23 0B 71 05 00 00 00 FF 06 17 00 00 00 58
2019-04-27 14:05:41.721 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=35, callback=0, payload=00 23 0B 71 05 00 00 00 FF 06 17 00 00 00
2019-04-27 14:05:41.721 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=35, callback=0, payload=00 23 0B 71 05 00 00 00 FF 06 17 00 00 00
2019-04-27 14:05:41.722 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2019-04-27 14:05:41.722 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 35: Application Command Request (ALIVE:DONE)
2019-04-27 14:05:41.722 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 35: resetResendCount initComplete=true isDead=false
2019-04-27 14:05:41.723 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 35: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-04-27 14:05:41.723 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 35: SECURITY not supported
2019-04-27 14:05:41.723 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 35: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT
2019-04-27 14:05:41.724 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 35: NOTIFICATION report - 0 = 0, event=23, status=255, plen=0
2019-04-27 14:05:41.724 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 35: Alarm Type = ACCESS_CONTROL (0)
2019-04-27 14:05:41.725 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-04-27 14:05:41.725 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2019-04-27 14:05:41.725 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter processing NOTIFICATION
2019-04-27 14:05:41.726 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter NOTIFICATION event is 23, type OnOffType
2019-04-27 14:05:41.726 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter processing NOTIFICATION
2019-04-27 14:05:41.727 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter NOTIFICATION event is 23, type OnOffType
2019-04-27 14:05:41.727 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter processing NOTIFICATION
2019-04-27 14:05:41.727 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter NOTIFICATION event is 23, type OnOffType
2019-04-27 14:05:41.728 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 35: Commands processed 1.
2019-04-27 14:05:41.728 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 35: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@24162930.
2019-04-27 14:05:41.728 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-04-27 14:05:41.729 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-04-27 14:05:41.729 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2019-04-27 14:05:41.729 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
2019-04-27 14:05:42.068 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 37: Polling…

Items file snippet:
/*********************************************** Z Wave Sensors ******************************************/
Contact Garage_Door_Contact_Small “Little Garage Door (36) [%s]” (Garage) {channel = “zwave:device:9305b102:node36:sensor_binary”}
Contact Kitchen_PIR_Switch “Kitchen PIR[%s]” (Occupancy) {channel = “zwave:device:9305b102:node21:sensor_binary”}
Number Kitchen_RH “Kitchen Humidity [%s]” (Thermostat,RH) {channel = “zwave:device:9305b102:node21:sensor_relhumidity”}
Number Kitchen_Temp “Kitchen Temp [%.1f]” (Thermostat) {channel = “zwave:device:9305b102:node21:sensor_temperature”}
Number Kitchen_Lum “Kitchen Light Level [%.1f]” (Thermostat) {channel = “zwave:device:9305b102:node21:sensor_luminance”}
Contact Bonus_PIR_Contact “Bonus Room PIR [%s]” (Occupancy) {channel = “zwave:device:9305b102:node15:sensor_door”}
Contact Garage_Door_Contact “Big Garage Door (35) [%s]” (Garage) {channel = “zwave:device:9305b102:node35:sensor_binary”}

  • Platform information:
    • Hardware: _CPUArchitecture/RAM/storage_IBM thinkpad

    • OS: _what OS is used and which version_Ubuntu 18.04

    • Java Runtime Environment: which java platform is used and what version openjdk version “1.8.0_202”

    • openHAB version: 2.4.0

  • Issue of the topic: please be detailed explaining your issue
  • Please post configurations (if applicable):
    • Items configuration related to the issue
    • Sitemap configuration related to the issue
    • Rules code related to the issue
    • Services configuration related to the issue
  • If logs where generated please post these here using code fences:
0 Likes

(SiHui) #2

Not much in there:

The device database has changed for this device a while ago, probably after 2.4. So first thing to do is update to the latest zwave 2.5 zwave snapshot binding.

0 Likes

(Scott Hogan) #3

It worked right from the start before. I removed the binding and installed 2.5 snapshot jar. No change. It actually looks like all of my contact items aren’t working. I have a couple of PIR sensors that are also not responding.

0 Likes

(SiHui) #4

Then it is time for a longer debug log. Please feed it through the log viewer to see what is happening:
https://www.cd-jackson.com/index.php/openhab/zwave-log-viewer

0 Likes

(Scott Hogan) #5

Here’s a log from the last half hour.

0 Likes

(SiHui) #6

From what I read in the docs sensor_binary is a switch itemtype and sensor_door is a contact itemtype:

https://www.openhab.org/addons/bindings/zwave/thing.html?manufacturer=eco&file=dwzwave25_0_0.html

0 Likes

(Chris Jackson) #7

What are you expecting to see here? From the things definition above, you only have the sensor_binary channel linked, and the binding is correctly decoding this, and setting the channel state.

The sensor_door channel is also being received, but it’s not updating the channel as it’s not linked as far as I can see.

0 Likes

(Scott Hogan) #8

The item status is not updating according to basic UI and rules are not seeing the updates.

0 Likes

(SiHui) #9

As said before: please use the correct itemtype.

0 Likes

(Scott Hogan) #10

This worked out of the box and for months without issue.
Contact Garage_Door_Contact_Small "Little Garage Door (36) [%s]"<garagedoor> (Garage) {channel = "zwave:device:9305b102:node36:sensor_binary"}

I tried this:
Contact Garage_Door_Contact_Small "Little Garage Door (36) [%s]"<garagedoor> (Garage) {channel = "zwave:device:9305b102:node36:sensor_door"}

And this:
Switch Garage_Door_Contact_Small "Little Garage Door (36) [%s]"<garagedoor> (Garage) {channel = "zwave:device:9305b102:node36:sensor_binary"}

I understand this a little better and believe 2 or 3 should work, but not 1.

0 Likes

(SiHui) #11

Correct, that is what the docs tell us.

0 Likes

(Scott Hogan) #12

I actually just created both 2 and 3 for node 35 and 36. None of the 4 items are updating. Just to make sure I have it correct, here is my current item definitions.

/***********************************************  Z Wave Sensors   ******************************************/
Switch GDBS "Little G Door Binary" <garagedoor>                                 (Garage)        {channel = "zwave:device:9305b102:node36:sensor_binary"}
Contact	Garage_Door_Contact_Small "Little Garage Door (36) [%s]"<garagedoor>	(Garage)		{channel = "zwave:device:9305b102:node36:sensor_door"}
Contact Kitchen_PIR_Switch   	"Kitchen PIR[%s]"   							(Occupancy)		{channel = "zwave:device:9305b102:node21:sensor_binary"}
Number Kitchen_RH 				"Kitchen Humidity [%s]"							(Thermostat,RH)	{channel = "zwave:device:9305b102:node21:sensor_relhumidity"}
Number Kitchen_Temp				"Kitchen Temp [%.1f]"							(Thermostat)	{channel = "zwave:device:9305b102:node21:sensor_temperature"}
Number Kitchen_Lum				"Kitchen Light Level [%.1f]"					(Thermostat)	{channel = "zwave:device:9305b102:node21:sensor_luminance"}
Contact	Bonus_PIR_Contact		"Bonus Room PIR [%s]"							(Occupancy)		{channel = "zwave:device:9305b102:node15:sensor_door"}
Switch	Garage_Door_Binary	"Big Garage Door Binary (35) [%s]"	<garagedoor>	(Garage)		{channel = "zwave:device:9305b102:node35:sensor_binary"}
Contact	Garage_Door_Contact 	"Big Garage Door (35) [%s]"	<garagedoor>    	(Garage)		{channel = "zwave:device:9305b102:node35:sensor_door"}
0 Likes

(Scott Hogan) #13

Assuming these appear correct, any suggestions on next steps would be appreciated.

0 Likes

(Chris Jackson) #14

From the main log, it looks fine - what does the event log show?

0 Likes

(Scott Hogan) #15

It doesn’t appear to me that there are any events showing up related to the garage door items. I activated them several times and they are showing up in the zwave debug. Sample from timestamp 15:21:55 from both logs below.

2019-04-28 15:21:55.051 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 35: Application Command Request (ALIVE:REQUEST_NIF)
2019-04-28 15:21:55.054 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 35: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2019-04-28 15:21:55.056 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 35: SECURITY not supported
2019-04-28 15:21:55.066 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 35: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT
2019-04-28 15:21:55.066 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 35: NOTIFICATION report - 0 = 0, event=3, status=255, plen=0
2019-04-28 15:21:55.067 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 35: Alarm Type = BURGLAR (0)
2019-04-28 15:21:55.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2019-04-28 15:21:55.067 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2019-04-28 15:21:55.067 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter processing NOTIFICATION
2019-04-28 15:21:55.068 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter NOTIFICATION event is 3, type OnOffType
2019-04-28 15:21:55.068 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Updating channel state zwave:device:9305b102:node35:alarm_tamper to ON [OnOffType]
2019-04-28 15:21:55.075 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter processing NOTIFICATION
2019-04-28 15:21:55.076 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter NOTIFICATION event is 3, type OnOffType
2019-04-28 15:21:55.078 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter processing NOTIFICATION
2019-04-28 15:21:55.086 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 35: Alarm converter NOTIFICATION event is 3, type OnOffType
2019-04-28 15:21:55.087 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 35: Commands processed 1.
2019-04-28 15:21:55.087 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 35: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@5ad17ba2.
2019-04-28 15:21:55.087 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2019-04-28 15:21:55.090 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0

2019-04-28 15:19:08.367 [nt.ItemStatePredictedEvent] - hue_color_5 predicted to become 74,79,100
2019-04-28 15:19:08.367 [nt.ItemStatePredictedEvent] - Thermostat_Mode predicted to become 1
2019-04-28 15:19:08.367 [nt.ItemStatePredictedEvent] - Thermostat_Fan_Mode predicted to become 0
2019-04-28 15:19:12.425 [vent.ItemStateChangedEvent] - sAlarmPanelDisplay changed from "FAULT 06                        " to "****DISARMED****  Ready to Arm  "
2019-04-28 15:19:50.214 [vent.ItemStateChangedEvent] - Sun_Elevation changed from 47.17007926790252 to 46.532746635523075
2019-04-28 15:20:00.011 [ome.event.ItemCommandEvent] - Item 'currentTime' received command 2019-04-28T15:20:00.009-0700
2019-04-28 15:20:00.020 [vent.ItemStateChangedEvent] - currentTime changed from 2019-04-28T15:19:00.013-0700 to 2019-04-28T15:20:00.009-0700
2019-04-28 15:20:05.033 [vent.ItemStateChangedEvent] - Kitchen_Lum changed from 9 to 8
2019-04-28 15:20:05.062 [vent.ItemStateChangedEvent] - Kitchen_RH changed from 30 to 29
2019-04-28 15:21:00.013 [ome.event.ItemCommandEvent] - Item 'currentTime' received command 2019-04-28T15:21:00.012-0700
2019-04-28 15:21:00.016 [vent.ItemStateChangedEvent] - currentTime changed from 2019-04-28T15:20:00.009-0700 to 2019-04-28T15:21:00.012-0700
2019-04-28 15:21:01.004 [ome.event.ItemCommandEvent] - Item 'zone1' received command CLOSED
2019-04-28 15:21:01.006 [vent.ItemStateChangedEvent] - zone1 changed from OPEN to CLOSED
2019-04-28 15:21:01.012 [ome.event.ItemCommandEvent] - Item 'zone4' received command CLOSED
2019-04-28 15:21:01.012 [vent.ItemStateChangedEvent] - zone4 changed from OPEN to CLOSED
2019-04-28 15:21:01.013 [ome.event.ItemCommandEvent] - Item 'zone6' received command CLOSED
2019-04-28 15:21:01.014 [vent.ItemStateChangedEvent] - zone6 changed from OPEN to CLOSED
2019-04-28 15:22:00.011 [ome.event.ItemCommandEvent] - Item 'currentTime' received command 2019-04-28T15:22:00.009-0700
2019-04-28 15:22:00.017 [vent.ItemStateChangedEvent] - currentTime changed from 2019-04-28T15:21:00.012-0700 to 2019-04-28T15:22:00.009-0700
2019-04-28 15:22:05.074 [vent.ItemStateChangedEvent] - Kitchen_Lum changed from 8 to 9
2019-04-28 15:23:00.012 [ome.event.ItemCommandEvent] - Item 'currentTime' received command 2019-04-28T15:23:00.011-0700
2019-04-28 15:23:00.016 [vent.ItemStateChangedEvent] - currentTime changed from 2019-04-28T15:22:00.009-0700 to 2019-04-28T15:23:00.011-0700
2019-04-28 15:23:05.081 [vent.ItemStateChangedEvent] - Kitchen_Lum changed from 9 to 8
2019-04-28 15:24:00.013 [ome.event.ItemCommandEvent] - Item 'currentTime' received command 2019-04-28T15:24:00.011-0700
2019-04-28 15:24:00.018 [vent.ItemStateChangedEvent] - currentTime changed from 2019-04-28T15:23:00.011-0700 to 2019-04-28T15:24:00.011-0700
2019-04-28 15:24:05.088 [vent.ItemStateChangedEvent] - Kitchen_Lum changed from 8 to 9
2019-04-28 15:24:05.150 [vent.ItemStateChangedEvent] - Kitchen_Temp changed from 70.3 to 70.2
0 Likes

(Scott Rushworth) #16

Have you seen any errors when restarting OH or saving your rule file? Or in VS Code when viewing the file? It looks like there is a space missing between the label and icon in the little door item definition. If so, that could prevent the whole file from loading.

oh… I just saw the event.log with some of the other items… nevermind!

But all items linked to sensor_binary Channels need to be switches.

0 Likes

(Scott Hogan) #17

I have had it complain about rule and item syntax, but not currently. I’m focused on the garage doors at the moment. All of them worked fine for months if not years as contact / sensor_binary before.

0 Likes

(Scott Hogan) #18

I don’t know what else to do but reinstall again. I’m happy to take some direction in debugging if it will benefit OH, otherwise I have way more time in this than it will take me to wipe it clean and start over. I have practice with that. Something similar happened last year, though it was blamed on my PI with SD storage. I’m on linux pc with HDD now.

0 Likes

(Mark) #19

Here’s a theory about the reason why the following channel update wasn’t logged.

From your log above, here’s where the binding updated one of the channels (alarm_tamper).

2019-04-28 15:21:55.068 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 35: Updating channel state zwave:device:9305b102:node35:alarm_tamper to ON [OnOffType]

There had to be an item linked to this channel, otherwise, the binding wouldn’t bother updating the channel.

Why was there nothing in the event log? Quite possibly because the state of the item already was ON, in which case, it would not be logged. Be default, only state change events are logged in events.log.

Item smarthomeItemStateEvent is only logged a ERROR level…

log4j2.logger.smarthomeItemStateEvent.name = smarthome.event.ItemStateEvent
log4j2.logger.smarthomeItemStateEvent.level = ERROR

A rule whose trigger was set to received update likely would’ve triggered in this case.

0 Likes

(Scott Hogan) #20

How do I change to debug?

0 Likes