Testing Z-Wave binding on openHAB-2

danielwalters86 · February 26, 2016, 2:31pm

Ran into problems when I updated yesterday. I noticed that the temperature value from my multisensor wasn’t being updated. What I found strange was that the sensor sends temp, humidity, uv and luminance all at the same time and I could see that luminance (only other one I checked) had been updated so I had a quick look and found there were changes around the temperature channel scale. However when I go into HABmin, select Celsius from the drop down and hit the big green Save button it doesn’t seem to save.

Am I doing something wrong?

chris · February 26, 2016, 3:19pm

There’s quite possibly a bug or two in this part of the code since this is quite new and has only had minimal testing… Do you have any logs of the temperature data being received?

chris · February 26, 2016, 3:29pm

So it looks like this always sends a 0, but you should be able to get this in a rule with the trigger Item received update which I think should trigger each time there’s an ‘update’ (even if the update is the same value - I think)?

danielwalters86 · February 26, 2016, 3:39pm

I’m at work at the moment so can’t access them (actually on that thought I think a web version of the logs/karaf console would be useful too! ) until tonight. I just wanted to double check I wasn’t doing anything stupid.

chris · February 26, 2016, 4:20pm

Anything? Well, I can’t comment on that . However in this case, no - it’s more likely to be an issue with the binding…

feens · February 26, 2016, 6:00pm

Thats what I originally thought, but turns out it’s not working. I did a bit more playing with it and tried to capture more log into to see what’s going on. I stumbled upon this past issue which seems to be somewhat similar: https://github.com/cdjackson/HABmin/issues/202

Here’s a deeper log of what happens when I press the button:

2016-02-26 12:30:25.890 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Application Command Request (ALIVE:MANUFACTURER) 2016-02-26 12:30:25.891 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class ALARM 2016-02-26 12:30:25.891 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Received Alarm Request 2016-02-26 12:30:25.892 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm report - Value = 0 2016-02-26 12:30:25.893 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 14: Alarm Type = General (0) 2016-02-26 12:30:25.893 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent 2016-02-26 12:30:25.894 [DEBUG] [ng.zwave.internal.ZWaveActiveBinding] - ZwaveIncomingEvent 2016-02-26 12:30:25.895 [DEBUG] [ng.zwave.internal.ZWaveActiveBinding] - NODE 14: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0 2016-02-26 12:30:25.897 [DEBUG] [ssage.ApplicationCommandMessageClass] - Transaction not completed: node address inconsistent.

Here’s a more detailed init log:

2016-02-26 12:27:23.766 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Unsupported command class ZWAVE_PLUS_INFO
2016-02-26 12:27:23.767 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class VERSION
2016-02-26 12:27:23.768 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: Adding command class VERSION to the list of supported command classes.
2016-02-26 12:27:23.769 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class MANUFACTURER_SPECIFIC
2016-02-26 12:27:23.770 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: Adding command class MANUFACTURER_SPECIFIC to the list of supported command classes.
2016-02-26 12:27:23.771 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Unsupported command class DEVICE_RESET_LOCALLY
2016-02-26 12:27:23.772 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Unsupported command class POWERLEVEL
2016-02-26 12:27:23.773 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class BATTERY
2016-02-26 12:27:23.775 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: Adding command class BATTERY to the list of supported command classes.
2016-02-26 12:27:23.776 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class CONFIGURATION
2016-02-26 12:27:23.777 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: Adding command class CONFIGURATION to the list of supported command classes.
2016-02-26 12:27:23.779 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class ASSOCIATION
2016-02-26 12:27:23.781 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: Adding command class ASSOCIATION to the list of supported command classes.
2016-02-26 12:27:23.782 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Unsupported command class ASSOCIATION_GROUP_INFO
2016-02-26 12:27:23.783 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Creating new instance of command class WAKE_UP
2016-02-26 12:27:23.786 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 14: Adding command class WAKE_UP to the list of supported command classes.
2016-02-26 12:27:23.788 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 14: Unsupported command class FIRMWARE_UPDATE_MD
2016-02-26 12:27:23.788 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveNodeInfoEvent
2016-02-26 12:27:23.789 [DEBUG] [ng.zwave.internal.ZWaveActiveBinding] - ZwaveIncomingEvent
2016-02-26 12:27:23.790 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: 14 NIF event during initialisation stage PING
2016-02-26 12:27:23.791 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: NIF event during initialisation stage PING - advancing
2016-02-26 12:27:23.792 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: NIF event during initialisation stage DETAILS
2016-02-26 12:27:23.793 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer - DETAILS: queue length(0), free to send(true)
2016-02-26 12:27:23.794 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer: loop - DETAILS try 1: stageAdvanced(false)
2016-02-26 12:27:23.795 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer: received RequestNodeInfo
2016-02-26 12:27:23.795 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer - advancing to MANUFACTURER
2016-02-26 12:27:23.796 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer: loop - MANUFACTURER try 0: stageAdvanced(true)
2016-02-26 12:27:23.797 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer: MANUFACTURER - send ManufacturerSpecific
2016-02-26 12:27:23.798 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 14: Creating new message for command MANUFACTURER_SPECIFIC_GET
2016-02-26 12:27:23.799 [DEBUG] [wave.internal.protocol.SerialMessage] - NODE 14: Creating empty message of class = SendData (0x13), type = Request (0x00)
2016-02-26 12:27:23.800 [DEBUG] [ve.internal.protocol.ZWaveController] - Callback ID = 114
2016-02-26 12:27:23.802 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
2016-02-26 12:27:23.803 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer - queued packet. Queue length is 1
2016-02-26 12:27:23.804 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: 10 NIF event during initialisation stage PING
2016-02-26 12:27:23.805 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Is awake with 1 messages in the wake-up queue.
2016-02-26 12:27:23.807 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveWakeUpEvent
2016-02-26 12:27:23.807 [DEBUG] [ng.zwave.internal.ZWaveActiveBinding] - ZwaveIncomingEvent
2016-02-26 12:27:23.809 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Wakeup during initialisation.
2016-02-26 12:27:23.810 [DEBUG] [nitialization.ZWaveNodeStageAdvancer] - NODE 14: Node advancer - MANUFACTURER: queue length(1), free to send(false)

I thought (from the issue I linked to above) that maybe I had to do a wakeup near the controller to help things out, so I did that, and here’s the output:

2016-02-26 12:27:23.982 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 14: Incoming command class MANUFACTURER_SPECIFIC
2016-02-26 12:27:23.983 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 14: Received Manufacture Specific Information
2016-02-26 12:27:23.984 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 14: Manufacturer ID = 0x0178
2016-02-26 12:27:23.985 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 14: Device Type = 0x4442
2016-02-26 12:27:23.987 [DEBUG] [WaveManufacturerSpecificCommandClass] - NODE 14: Device ID = 0x3130
2016-02-26 12:27:28.825 [DEBUG] [wave.internal.protocol.SerialMessage] - NODE 255: Creating empty message of class = SendDataAbort (0x16), type = Request (0x00)
2016-02-26 12:27:28.826 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 03 00 16 EA 
2016-02-26 12:27:28.828 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 14: Sending ABORT Message = 01 03 00 16 EA 
2016-02-26 12:27:28.830 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 14: Timeout while sending message. Requeueing - 2 attempts left!
2016-02-26 12:27:28.832 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Is sleeping
2016-02-26 12:27:28.833 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.
2016-02-26 12:27:28.834 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-02-26 12:27:28.835 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Message already on the wake-up queue. Removing original.
2016-02-26 12:27:28.844 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 14: Putting message SendData in wakeup queue.```

It's like OH is receiving the event but doesn't quite know what to do with it.

I also noticed one of these: 
```2016-02-26 12:11:15.827 [DEBUG] [ng.zwave.internal.ZWaveActiveBinding] - NODE 14: Polling list: item Sensor_Doorbell is not completed initialization

Further info…here’s my items line:

Number Sensor_Doorbell "Doorbell [%s]" (ALL,ff,sensor) {zwave="14:command=ALARM"}

And my rule:

when
	Sensor_Doorbell received update
then
	logInfo("Doorbell", "The doorbell rang")
end

chris · February 26, 2016, 6:10pm

I’m getting confused - is this with the OH2 zwave binding or OH1?

It looks ok - the initialisation is a bit slow and it might need waking up a few more times. The alarm processing might not be right either - I’ll have a better look at that later.

feens · February 26, 2016, 6:12pm

Thats from OH1 binding.

Christer_Akerlund · February 26, 2016, 9:54pm

Managed to get some time and test everything out for once and overall most of the stuff seems to work without trouble (in regards to the software, old fibaro plugs never seem to play nicely…).
But i ran into some questions about the Nodon Octon Remote aswell (this one http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/249)
Since its not in the release it wont work, but ignoring that, i used it like this before

Switch bfmax “Master GF max” { zwave=“41:command=SCENE_ACTIVATION,scene=10,state=0” }
Switch bfmin “Master GF min” { zwave=“41:command=SCENE_ACTIVATION,scene=20,state=0” }
Switch bfinc “Master GF inc” { zwave=“41:command=SCENE_ACTIVATION,scene=30,state=0” }
Switch bfdec “Master GF dec” { zwave=“41:command=SCENE_ACTIVATION,scene=40,state=0” }

when those where triggered i changed a numbervalue (0/100 for min/max and +/-20 for inc/dec)
and when the numbervalue changed it in turn sets all dimmers on the bottom floor to that level, and if the level is more than 50 it turns on all switches and respectively turns all switches off if it is below 50. Making it a master for the entire floor (one button when i go to bed for ex, and at most 3 clicks to set any out of 5 possible dimminglevels).

However. Now i get this in the log:
21:33:26.061 [WARN ] [tocol.commandclass.ZWaveCommandClass] - NODE 11: Unsupported command class CENTRAL_SCENE
21:33:26.062 [ERROR] [ssage.ApplicationCommandMessageClass] - NODE 11: Unsupported command class CENTRAL_SCENE (0x5b)

First, CENTRAL_SCENE isn’t the same as SCENE_ACTIVATION i guess? Have that name changed or have i done some configuration that i have forgotten about? (not entirely uncommon with me…)
And lastly, would that type of configuration be possible now? since i bind a channel to an item now i dont really configure it the same way so i cant specify command and state. Or are the configuration in the itemfiles planned to work in parallell with the configuration from the gui?

A lot of speculation, but its friday night and im trying to avoid working…

/C

chris · February 26, 2016, 10:26pm

Nope - they’re definately different . However, I doubt this is new - if the device supports both classes, then this is just saying that the binding doesn’t support the CENTRAL_SCENE - it doesn’t say it doesn’t support SCENE_ACTIVATION - that’s still supported.

The OH2 binding should work the same as OH1 - the only issue at the moment is that the database doesn’t support the SCENE_ACTIVATION class, so you can’t set channels for it. It’s also possible we may need to do something in the conveter, but it should be broadly the same as OH1.

I’ve added the SCENE_ACTIVATION class to the database now, so we should look to update this device to support these classes and add some channels - I’ll need to think about the format and I’ll do that over the next few days…

Christer_Akerlund · February 26, 2016, 10:33pm

No rush =)

Also a facepalm… it pretty much explains it in the link i provided aswell… parameter 3 lets you toggle between scene activation and central scene… so it probably reset when i switched controller at the same time as testing OH2… I’ll read up better before asking weird questions the next time =)

/C

bhuism · February 27, 2016, 1:18pm

@chris The color command for Aeotec ZW098 is not implemented so it seems, I’d love to help:

-27 14:09:15.366 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color' received command 325,75,50
2016-02-27 14:09:15.375 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No messages returned from converter
2016-02-27 14:09:15.387 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 0,0,0 to 325,75,50
2016-02-27 14:09:15.660 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color' received command 3,74,50
2016-02-27 14:09:15.665 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No messages returned from converter
2016-02-27 14:09:15.681 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 325,75,50 to 3,74,50
2016-02-27 14:09:15.966 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color' received command 2,88,50
2016-02-27 14:09:15.971 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No messages returned from converter
2016-02-27 14:09:15.986 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 3,74,50 to 2,88,50
2016-02-27 14:09:16.750 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color' received command 2,88,100
2016-02-27 14:09:16.756 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No messages returned from converter

Can u point me in the right direction?

bhuism · February 27, 2016, 1:23pm

Als, maybe unrelated, some errors getting the messages out the door so it seems:

2016-02-27 14:05:26.631 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 2 attempts left!
2016-02-27 14:05:26.637 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message.
2016-02-27 14:05:26.720 [ERROR] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (CAN), resending
2016-02-27 14:05:26.773 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 0,0,70 to 0,0,83
2016-02-27 14:05:26.775 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_1530ad9faba_serial_can changed from 23 to 24
2016-02-27 14:05:26.828 [WARN ] [ss.ZWaveMultiLevelSwitchCommandClass] - Unsupported Command 1 for command class SWITCH_MULTILEVEL (0x26).
2016-02-27 14:05:30.953 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_greenwave_gwpn6_00_000_1530ad9faba_node10_meter_watts1 changed from 0.1 to 0
2016-02-27 14:05:31.699 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 2 attempts left!
2016-02-27 14:05:31.703 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message.
2016-02-27 14:05:31.764 [ERROR] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (CAN), resending
2016-02-27 14:05:31.775 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_1530ad9faba_serial_can changed from 24 to 25
2016-02-27 14:05:31.879 [WARN ] [ss.ZWaveMultiLevelSwitchCommandClass] - Unsupported Command 1 for command class SWITCH_MULTILEVEL (0x26).
2016-02-27 14:05:32.472 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_greenwave_gwpn6_00_000_1530ad9faba_node10_meter_watts1 changed from 0 to 1
2016-02-27 14:05:33.950 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_greenwave_gwpn6_00_000_1530ad9faba_node10_meter_watts1 changed from 1 to 0
2016-02-27 14:05:36.757 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 2 attempts left!
2016-02-27 14:05:36.761 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message.
2016-02-27 14:05:36.826 [ERROR] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (CAN), resending
2016-02-27 14:05:36.838 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_1530ad9faba_serial_can changed from 25 to 26
2016-02-27 14:05:36.847 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 0,0,83 to 0,0,0
2016-02-27 14:05:36.939 [WARN ] [ss.ZWaveMultiLevelSwitchCommandClass] - Unsupported Command 1 for command class SWITCH_MULTILEVEL (0x26).
2016-02-27 14:05:36.953 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_greenwave_gwpn6_00_000_1530ad9faba_node10_meter_watts1 changed from 0 to 10.5
2016-02-27 14:05:41.811 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 2 attempts left!
2016-02-27 14:05:41.813 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message.
2016-02-27 14:05:41.868 [ERROR] [WaveSerialHandler$ZWaveReceiveThread] - Protocol error (CAN), resending
2016-02-27 14:05:41.879 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_1530ad9faba_serial_can changed from 26 to 27
2016-02-27 14:05:41.976 [WARN ] [ss.ZWaveMultiLevelSwitchCommandClass] - Unsupported Command 1 for command class SWITCH_MULTILEVEL (0x26).
2016-02-27 14:05:46.863 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 8: Timeout while sending message. Requeueing - 1 attempts left!
2016-02-27 14:05:46.866 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 8: Got an error while sending data. Resending message.

If I can do/test anything let me know

chris · February 27, 2016, 1:28pm

It is implemented - is this using the latest update from this morning?

Yes, it’s not related. Are you running OH in a VM?

bhuism · February 27, 2016, 1:43pm

I will update now to latest snapshot: https://openhab.ci.cloudbees.com/job/openHAB-Distribution/157/ and let you know if the color works.

It runs on an Udoo i.MX6 Quad Board ( http://shop.udoo.org/eu/home/udoo-quad.html ) Never above 10% CPU, whn I switch all the lights on/off I get a lot of zwave transmit errors as wel, but it retries and eventually it gets the messages out.

4integration · February 27, 2016, 1:45pm

Have Habmin2 and Z-wave binding moved to openHAB github?
I cannot see any updated builds here: https://github.com/cdjackson/HABmin2/tree/theme/output

If yes, where can I get updated binaries?

Also I see some issues with “ZW100 MultiSensor 6” where Temperature won’t update. Also as someone else noted, not possible to select/save Celcius in config.

chris · February 27, 2016, 2:02pm

The latest build should be available on cloudbees (or using PaperUI).

Please make sure you have the latest version of HABmin, and the latest binding, and a recent version of OH2 (ie not the beta release, but a new snapshot). This is still quite new, so there might be bugs here, but it should save ok at least.

So not running under a VM or container of some description then?

bhuism · February 27, 2016, 2:12pm

Nope, plain ARMBIAN:

bhuism@udoo:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 8.3 (jessie)
Release:	8.3
Codename:	jessie

Java:

bhuism@udoo:~$ java -version
java version "1.8.0_71"
Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
Java HotSpot(TM) Client VM (build 25.71-b15, mixed mode)

Looks like the latest version can not find any converts:

(of should I remove and add the things again? then I get “Error loading inbox!” in Habmin2 and “ERROR: 500 - Internal Server Error” in Paper UI)

2016-02-27 14:51:42.714 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:alarm_general, class ALARM
2016-02-27 14:51:42.714 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: No converter for zwave:aeon_zw089_00_000:1530ad9faba:node11:alarm_general, class ALARM
2016-02-27 14:51:42.716 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.718 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.718 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:switch_dimmer, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.718 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter for zwave:aeon_zw100_00_000:1530ad9faba:node5:alarm_general, class ALARM
2016-02-27 14:51:42.720 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:sensor_power, class SENSOR_MULTILEVEL
2016-02-27 14:51:42.720 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:switch_dimmer, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.722 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: No converter for zwave:aeon_zw089_00_000:1530ad9faba:node11:battery-level, class BATTERY
2016-02-27 14:51:42.726 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_relhumidity, class SENSOR_MULTILEVEL
2016-02-27 14:51:42.726 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_kwh, class METER
2016-02-27 14:51:42.726 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:color_color, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.728 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_ultraviolet, class SENSOR_MULTILEVEL
2016-02-27 14:51:42.728 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_watts, class METER
2016-02-27 14:51:42.728 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:color_color, class COLOR
2016-02-27 14:51:42.734 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:sensor_power1, class SENSOR_MULTILEVEL
2016-02-27 14:51:42.736 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:color_color, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.736 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_temperature, class SENSOR_MULTILEVEL
2016-02-27 14:51:42.736 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer1, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.736 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:color_color, class BASIC
2016-02-27 14:51:42.737 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer1, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.737 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:color_temperature, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.738 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_kwh1, class METER
2016-02-27 14:51:42.738 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter for zwave:aeon_zw098_00_000:1530ad9faba:node8:color_temperature, class COLOR
2016-02-27 14:51:42.738 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_luminance, class SENSOR_MULTILEVEL
2016-02-27 14:51:42.739 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_watts1, class METER
2016-02-27 14:51:42.747 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer2, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.747 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 11: No converter for zwave:aeon_zw089_00_000:1530ad9faba:node11:sensor_binary, class SENSOR_BINARY
2016-02-27 14:51:42.749 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer2, class SWITCH_MULTILEVEL
2016-02-27 14:51:42.747 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_binary, class SENSOR_BINARY
2016-02-27 14:51:42.774 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:switch_binary, class SWITCH_BINARY
2016-02-27 14:51:42.774 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary, class SWITCH_BINARY
2016-02-27 14:51:42.777 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary1, class SWITCH_BINARY
2016-02-27 14:51:42.778 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: No converter for zwave:greenwave_gwpn1_03_000:1530ad9faba:node6:switch_binary, class SWITCH_BINARY
2016-02-27 14:51:42.777 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:switch_binary1, class SWITCH_BINARY
2016-02-27 14:51:42.782 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: No converter for zwave:greenwave_gwpn1_03_000:1530ad9faba:node6:switch_binary1, class SWITCH_BINARY
2016-02-27 14:51:42.793 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: No converter for zwave:greenwave_gwpn6_00_000:1530ad9faba:node10:switch_binary, class SWITCH_BINARY
2016-02-27 14:51:42.807 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: No converter for zwave:greenwave_gwpn1_03_000:1530ad9faba:node7:switch_binary, class SWITCH_BINARY
2016-02-27 14:51:53.579 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:switch_binary
2016-02-27 14:51:54.244 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No converter set for zwave:aeon_zw098_00_000:1530ad9faba:node8:switch_dimmer
2016-02-27 14:51:54.568 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node7:switch_binary
2016-02-27 14:51:56.160 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 10: No converter set for zwave:greenwave_gwpn6_00_000:1530ad9faba:node10:switch_binary
2016-02-27 14:51:57.563 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:51:57.980 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node6:switch_binary
2016-02-27 14:51:58.100 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node6:switch_binary
2016-02-27 14:51:58.758 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:sensor_power
2016-02-27 14:51:58.809 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_kwh
2016-02-27 14:51:58.861 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_kwh
2016-02-27 14:51:58.908 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer
2016-02-27 14:51:58.961 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_kwh1
2016-02-27 14:51:59.035 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:meter_kwh1
2016-02-27 14:51:59.085 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer1
2016-02-27 14:51:59.211 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:sensor_power1
2016-02-27 14:51:59.261 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer2
2016-02-27 14:52:01.947 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:52:26.358 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:52:28.835 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:53:43.591 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter set for zwave:aeon_zw100_00_000:1530ad9faba:node5:alarm_general
2016-02-27 14:54:46.450 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:54:47.423 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:54:54.000 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:54:56.409 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:54:58.804 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:54:59.671 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 12: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node12:switch_binary
2016-02-27 14:55:01.806 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for zwave:fibaro_fgd212_00_000:1530ad9faba:node4:switch_dimmer
2016-02-27 14:55:01.859 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:switch_binary
2016-02-27 14:55:01.874 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node6:switch_binary
2016-02-27 14:55:10.017 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter set for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_relhumidity
2016-02-27 14:55:10.727 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter set for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_relhumidity
2016-02-27 14:55:11.896 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter set for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_relhumidity
2016-02-27 14:55:12.040 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: No converter set for zwave:aeon_zw100_00_000:1530ad9faba:node5:sensor_relhumidity
2016-02-27 14:55:19.923 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:switch_binary
2016-02-27 14:55:25.715 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:switch_binary
2016-02-27 14:55:28.052 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 3: No converter set for zwave:greenwave_gwpn1_03_000:1530ad9faba:node3:switch_binary

On the Aeotec led bulb front some change, but no color:

2016-02-27 15:11:10.934 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_temperature' received command 91
2016-02-27 15:11:10.939 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_temperature changed from 0 to 91
2016-02-27 15:11:11.089 [WARN ] [.commandclass.ZWaveColorCommandClass] - Unsupported Command 0x05 for command class COLOR (0x33).
2016-02-27 15:11:11.118 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 8: Color report WARM_WHITE 91
2016-02-27 15:11:11.118 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_temperature' received command 91
2016-02-27 15:11:11.151 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 8: Color report GREEN 0
2016-02-27 15:11:11.214 [WARN ] [.commandclass.ZWaveColorCommandClass] - Unsupported Command 0x05 for command class COLOR (0x33).
2016-02-27 15:11:11.249 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 8: Color report RED 0
2016-02-27 15:11:11.298 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 8: Color report COLD_WHITE 9
2016-02-27 15:11:11.347 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 8: Color report BLUE 0
2016-02-27 15:11:11.348 [INFO ] [.commandclass.ZWaveColorCommandClass] - NODE 8: Color report finished {WARM_WHITE=91, GREEN=0, RED=0, COLD_WHITE=9, BLUE=0}
2016-02-27 15:11:11.355 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 0,0,91 to 0,0,0
2016-02-27 15:11:11.363 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_temperature changed from 91 to 0
2016-02-27 15:11:14.396 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No messages returned from converter
2016-02-27 15:11:14.399 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color' received command 339,69,90
2016-02-27 15:11:14.405 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 0,0,0 to 339,69,90
2016-02-27 15:11:14.696 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No messages returned from converter
2016-02-27 15:11:14.703 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 339,69,90 to 354,99,90
2016-02-27 15:11:14.706 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color' received command 354,99,90
2016-02-27 15:11:15.687 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: No messages returned from converter
2016-02-27 15:11:15.691 [INFO ] [smarthome.event.ItemCommandEvent    ] - Item 'zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color' received command 354,99,100
2016-02-27 15:11:15.698 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw098_00_000_1530ad9faba_node8_color_color changed from 354,99,90 to 354,99,100

ptmuldoon · February 27, 2016, 2:31pm

@bhuism I and others have the same issue with the Aeotec LED RGBW bulbs and were actually just talking about it yesterday here.

I think Chris and group are already looking into it.

chris · February 27, 2016, 2:39pm

I don’t see this issue here . I’m not running exactly the same version as I’ve built it myself (but otherwise it should be the same code!) but it seems to run fine. Do you see any exceptions or anything?