This is really a continuation of my efforts here to get my Aeotec ZW056 device to work: Item Type: Number or Decimal
With the 2.3.0 binding, only three channels show up when the device is first added from the Inbox, even though the database entry is showing six channels. The first is the Switch channel, which works fine. The second two are the Volume and Repetitions, which are both using configuration commands. However, as pointed out in the above thread, the channels seem to be configured with a “Decimal” data type which makes it impossible to create and link an item.
So I took a look at a few more example database entries that work similarly (e.g. GE zw4006) and made the attached updated database entry: zw056_0_0.xml (15.0 KB)
This is an improvement, because I have all 5 configuration command based channels available and can link them to proper items with Number type. However, updating the channels in Paper UI and Rules does not work. I’m getting errors like the following in the debug log:
16:21:42.405 [INFO ] [smarthome.event.ItemCommandEvent ] - Item 'Annunciator_Play' received command 6 16:21:42.406 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 17: Command received zwave:device:07c3b712:node17:config_decimal_param6 --> 6 16:21:42.406 [DEBUG] [ndclass.ZWaveBinarySwitchCommandClass] - NODE 5: Creating new message for application command SWITCH_BINARY_GET 16:21:42.407 [DEBUG] [converter.ZWaveConfigurationConverter] - NODE 17: Config parameter 6 not found in converter 16:21:42.407 [DEBUG] [CommandClassTransactionPayloadBuilder] - At build COMMAND_CLASS_SWITCH_BINARY 16:21:42.408 [DEBUG] [nding.zwave.handler.ZWaveThingHandler] - NODE 17: No messages returned from converter
These same configuration parameter can successfully be set through the configuration parameters in PaperUI and HABmin
While I was investigating the issue I noticed a log message that probably needs cleaning up: ZWaveThingHandler::initialiseNode line 249 should probably be using bindingType as the last parameter.