Testing Z-Wave binding on openHAB-2

Until such a time, the script has been updated to reflect the new location, and the name of the JAR has been moved to a variable at the top section of the script. Enjoy!

20:26:31.877 [WARN ] [ig.xml.osgi.XmlDocumentBundleTracker] - The XML document '/ESH-INF/thing/popp_05438_0_0.xml' in module 'org.openhab.binding.zwave' could not be parsed: br : br
---- Debugging information ----
message             : br
cause-exception     : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message       : br
class               : java.util.ArrayList
required-type       : java.util.ArrayList

I have two devices where I need some help:

Aeon ZW100 Multisensor: Channel for Motion / Binary gets no update … also no entry in log that a value is updated for it

DLINK DCH Z110: This gets updated on the Contact however that state only shows up shortly on BasicUI and is set to " - " moments later? Also the status changed from On / Off instead of Open / Closed ?

cheers

This was fixed yesterday, but the changes weren’t merged until tomorrow…

@xsnrg is yours now fully running? binary and alarm do not get any update for me :frowning:

Hi

I am wondering about a device i have. the “Home Energy Meter G2” DSB28 in database. This device shows up as Unknown “Node 5 (0086:0002:001C:1.8)”.

Am i doing something wrong, or is this device not implemented?

/Henrik

for the DLINK it was that the item was declared as CONTACT which seems to loose the status after it was updated instantly. Doing it as a SWITCH does now work as expected. I hope i’m not doing it all wrong as I would say a door sensor should be a contact?..

that Aeon still troubles me … motion gets not detected whatever I do

The DSB28 was only added to the binding today (well, yesterday, but the current binding doesn’t have it). Please try with tomorrows snapshot and f it doesn’t work, please let me know…

Chris

Thanks for the quick answer

I am almost sorry to say we got this working, we changed parameter 3 to 15 seconds (at least better for testing I thing) and played around with parameter 5. Also a change in the database was requested:

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/database-history/devicesummary/73

We tested with a local build of the zwave binding with this change. And works now as expected.

I had not gotten to looking at it in depth yet, but I see later in this thread, it has been worked on, so that is great! Mine is included, and I am getting data from it though. Looking forward to trying out the build that happens in about 5 hours :slightly_smiling:

zwave_aeon_zw100_00_000_152e7642b11_node23 (Type=GroupItem, Members=7, State=UNDEF, Label=Node 23: ZW100 MultiSensor 6, Category=null, Tags=[thing])
zwave_aeon_zw100_00_000_152e7642b11_node23_alarm_general (Type=SwitchItem, State=NULL, Label=detached Alarm (general), Category=Door, Groups=[zwave_aeon_zw100_00_000_152e7642b11_node23])
zwave_aeon_zw100_00_000_152e7642b11_node23_battery_level (Type=NumberItem, State=100, Label=detached upstairs motion Battery Level, Category=Battery, Groups=[zwave_aeon_zw100_00_000_152e7642b11_node23, battery])
zwave_aeon_zw100_00_000_152e7642b11_node23_sensor_binary (Type=SwitchItem, State=ON, Label=detached upstairs motion, Category=Motion, Groups=[zwave_aeon_zw100_00_000_152e7642b11_node23, detached])
zwave_aeon_zw100_00_000_152e7642b11_node23_sensor_luminance (Type=NumberItem, State=6, Label=detached Sensor (luminance), Category=Temperature, Groups=[zwave_aeon_zw100_00_000_152e7642b11_node23, detached])
zwave_aeon_zw100_00_000_152e7642b11_node23_sensor_relhumidity (Type=NumberItem, State=26, Label=detached relative humidity, Category=Humidity, Groups=[zwave_aeon_zw100_00_000_152e7642b11_node23, detached])
zwave_aeon_zw100_00_000_152e7642b11_node23_sensor_temperature (Type=NumberItem, State=24.7, Label=Sensor (temperature), Category=Temperature, Groups=[zwave_aeon_zw100_00_000_152e7642b11_node23])
zwave_aeon_zw100_00_000_152e7642b11_node23_sensor_ultraviolet (Type=NumberItem, State=0, Label=detached Sensor (ultraviolet), Category=Temperature, Groups=[zwave_aeon_zw100_00_000_152e7642b11_node23, detached])

Since it is the device of the day, I took a look at the actual output from mine. It appears to be sending sensor multi-level and battery only. This seems to be in line with what @bhuism reported. I do have parameter 5 set to sensor_binary as well. Would you care to elaborate a little more on what change was needed? Curious. Thanks!

Hope I can help, this is the log of a motion detected event (just by moving my hand in front of the zw100):

2016-03-05 23:27:44.998 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 0F 03 30 03 FF 32 
2016-03-05 23:27:45.000 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-03-05 23:27:45.002 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 0F 03 30 03 FF 32 
2016-03-05 23:27:45.003 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 0F 03 30 03 FF 32 
2016-03-05 23:27:45.004 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 0F 03 30 03 FF 
2016-03-05 23:27:45.005 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Application Command Request (ALIVE:DONE)
2016-03-05 23:27:45.006 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 15: Incoming command class SENSOR_BINARY
2016-03-05 23:27:45.007 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 15: Received Sensor Binary Request (v1)
2016-03-05 23:27:45.008 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 15: Sensor Binary report, type=Unknown, value=255
2016-03-05 23:27:45.009 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveBinarySensorValueEvent
2016-03-05 23:27:45.010 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2016-03-05 23:27:45.010 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2016-03-05 23:27:45.011 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:alarm_general
2016-03-05 23:27:45.012 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:alarm_general
2016-03-05 23:27:45.013 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_relhumidity
2016-03-05 23:27:45.014 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_relhumidity
2016-03-05 23:27:45.015 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_ultraviolet
2016-03-05 23:27:45.016 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_ultraviolet
2016-03-05 23:27:45.017 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_temperature
2016-03-05 23:27:45.019 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_temperature
2016-03-05 23:27:45.020 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_luminance
2016-03-05 23:27:45.021 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_luminance
2016-03-05 23:27:45.022 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_binary
2016-03-05 23:27:45.023 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Processing event as channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_binary OnOffType
2016-03-05 23:27:45.024 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 1
2016-03-05 23:27:45.025 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 2
2016-03-05 23:27:45.026 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 3
2016-03-05 23:27:45.026 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 5
2016-03-05 23:27:45.027 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Updating zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_binary to ON
2016-03-05 23:27:45.029 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_binary
2016-03-05 23:27:45.030 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Processing event as channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_binary OnOffType
2016-03-05 23:27:45.031 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 1
2016-03-05 23:27:45.032 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 2
2016-03-05 23:27:45.032 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 3
2016-03-05 23:27:45.033 [DEBUG] [converter.ZWaveBinarySensorConverter] - ZWaveBinarySensorValueEvent 5
2016-03-05 23:27:45.034 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Updating zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_binary to ON
2016-03-05 23:27:45.036 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:sensor_binary
2016-03-05 23:27:45.037 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:battery-level
2016-03-05 23:27:45.038 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 15: Checking channel zwave:aeon_zw100_00_000:1532eca0da2:node15:battery-level

Current parameters:

Thanks, it looks similar to mine. The database and other changes must have been the ticket. I will update and try again later tonight.

@chris I updated the Leviton DZR15 entry in the db (which I’m assuming you saw). Any chance of squeaking that into tonight’s build? …added a receptacle to my family room and would like to tie it in with my switch :slight_smile: …wasn’t thinking of the database when I got a different one than the rest of my receptacles (it was in stock at HD and saved me ordering online).

I’ve just reprocessed the complete database to fix an error exporting devices with SENSOR_ALARM class. This may be at least part of the problem people are seeing with some sensors (but probably not if there’s nothing logged in the log at all :sunglasses:).

The other thing I’ve done (hopefully correctly!) is to consolidate the Philio devices since as far as I understand, for most of the Philio devices, the -1A / -1B / etc bit on the end just relates to the region, and type of ply etc. So, from a database perspective, it doesn’t make sense to have this in there multiple times…

The change in the Philio devices might upset some configurations, so I’ll apologise now (sorry :wink:).

@feens - I just saw your message in time :slightly_smiling:

Chris

@chris trying to figure out how to get my Aeotec hidden door sensor to work. It worked fine in version 1.9 of the binding. It seems to use the BASIC command set to send the open/closed commands, but I’m not sure how to get items to do that in the new binding. I tried playing with the config options for sending or not sending the basic and binary commands, but it still doesn’t trigger the item. Thoughts?

@feens , This is a device I worked on. I have mine working quite well now, so give these settings a try (picture)

Also, make sure the association back to the controller exists. I should also mention though that this is the gen5 version. Is yours? I do not recall, and do not see which yours is with a quick look back.

where do you get that listing from?

same settings for mine … moving my hand: (incoming alarm? transaction not completed? :frowning: )

07:57:23.619 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 09 0A 71 05 00 00 00 FF 07 08 00 00 6C 
07:57:23.623 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
07:57:23.625 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 09 0A 71 05 00 00 00 FF 07 08 00 00 6C 
07:57:23.627 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 09 0A 71 05 00 00 00 FF 07 08 00 00 6C 
07:57:23.629 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 09 0A 71 05 00 00 00 FF 07 08 00 00 
07:57:23.630 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Application Command Request (ALIVE:DONE)
07:57:23.632 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Incoming command class ALARM
07:57:23.634 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Received Alarm Request
07:57:23.635 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Process Alarm Report, V3, length 13
07:57:23.636 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Alarm report - 0 = 0, source=0, event=8, status=255
07:57:23.638 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Alarm Type = General (0)
07:57:23.639 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
07:57:23.640 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveAlarmValueEvent
07:57:23.642 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
07:57:23.643 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:alarm_general
07:57:23.645 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Processing event as channel zwave:aeon_zw100_00_000:15348538564:node9:alarm_general OnOffType
07:57:23.646 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Updating zwave:aeon_zw100_00_000:15348538564:node9:alarm_general to OFF
07:57:23.656 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:alarm_general
07:57:23.659 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Processing event as channel zwave:aeon_zw100_00_000:15348538564:node9:alarm_general OnOffType
07:57:23.668 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Updating zwave:aeon_zw100_00_000:15348538564:node9:alarm_general to OFF
07:57:23.675 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_relhumidity
07:57:23.676 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_relhumidity
07:57:23.677 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_ultraviolet
07:57:23.677 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_ultraviolet
07:57:23.678 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_temperature
07:57:23.679 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_temperature
07:57:23.680 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_luminance
07:57:23.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_luminance
07:57:23.681 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_binary
07:57:23.683 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:sensor_binary
07:57:23.684 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:battery-level
07:57:23.685 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Checking channel zwave:aeon_zw100_00_000:15348538564:node9:battery-level
07:57:23.686 [DEBUG] [ssage.ApplicationCommandMessageClass] - Transaction not completed: node address inconsistent.