Z-Wave: Command for unknown channel

Add-ons Bindings
1

Hello,

I updated yesterday to the latest OH2 snapshot via apt, and I am running the latest Z-wave binding from the top of this thread. The binding was in use successfully prior to the OH2 upgrade.

Now, with this latest release, I can’t control any Z-Wave items. When I try, I get log errors like this:

2017-04-19 12:00:14.325 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:159387b2735:node4:switch_dimmer --> ON
2017-04-19 12:00:14.325 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for command zwave:device:159387b2735:node4:switch_dimmer type OnOffType
2017-04-19 12:00:16.618 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:159387b2735:node4:switch_dimmer --> INCREASE
2017-04-19 12:00:16.618 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command for unknown channel zwave:device:159387b2735:node4:switch_dimmer with IncreaseDecreaseType
2017-04-19 12:00:17.091 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:159387b2735:node4:switch_dimmer --> ON
2017-04-19 12:00:17.091 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for command zwave:device:159387b2735:node4:switch_dimmer type OnOffType
2017-04-19 12:00:17.274 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:159387b2735:node4:switch_dimmer --> ON
2017-04-19 12:00:17.274 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: No converter set for command zwave:device:159387b2735:node4:switch_dimmer type OnOffType
2017-04-19 12:00:17.396 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:159387b2735:node4:switch_dimmer --> INCREASE
2017-04-19 12:00:17.396 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command for unknown channel zwave:device:159387b2735:node4:switch_dimmer with IncreaseDecreaseType
2017-04-19 12:00:17.565 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:159387b2735:node4:switch_dimmer --> INCREASE
2017-04-19 12:00:17.566 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command for unknown channel zwave:device:159387b2735:node4:switch_dimmer with IncreaseDecreaseType
2017-04-19 12:00:17.865 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command received zwave:device:159387b2735:node4:switch_dimmer --> INCREASE
2017-04-19 12:00:17.866 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 4: Command for unknown channel zwave:device:159387b2735:node4:switch_dimmer with IncreaseDecreaseType

Unlinking and re-linking the Items to the channel doesn’t resolve this issue, and neither does reinitializing the node. Any thoughts?

2

All of your Z-Wave devices are offline?

Is your controller Online?

What is the Controller’s device number?
In your logs it appears to be 159387b2735.

Did it change? Although I think re-initializing would have updated the linking. Do you have an example of your items file? Did you turn on Debugging for zwave?

3

All of them are ONLINE.

Yes, online.

Do you mean node number?

It hasn’t changed. No items file, I am using UI “native” configured items. Debugging is on. There’s nothing really interesting the logs. I can attach them, but they don’t say more than this “command for unknown channel” error. I am receiving data from my nodes - temperatures, humidity, etc. I just can’t SEND commands.

4

Ok, assuming you’re using Paper or HABmin, are the Channels Linked?

Clicking on the Blue Circles in PaperUI.

Are you familiar with the REST API page? You might investigate the Links and Channels. Check the GET sections to see if you can determine mappings.

5

HABmin and Paper UI show the items are linked. I will orient myself with the API and see what I find.

6

Looks like it is linked:

"UID": "zwave:device:159387b2735:node4",
    "thingTypeUID": "zwave:ge_45606_00_000",
    "channels": [
      {
        "linkedItems": [
          "Office_Cans"
        ],
        "uid": "zwave:device:159387b2735:node4:switch_dimmer",
        "id": "switch_dimmer",
        "channelTypeUID": "zwave:switch_dimmer",
        "itemType": "Dimmer",
        "kind": "STATE",
        "label": "Dimmer",
        "defaultTags": [],
        "properties": {
          "binding:Command:OnOffType": "COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC",
          "binding:*:PercentType": "COMMAND_CLASS_SWITCH_MULTILEVEL,COMMAND_CLASS_BASIC"
        },
        "configuration": {
          "config_restorelastvalue": true
        }
      }
    ]
7

Did you do this?

“You MUST delete your existing things and add them back. Current definitions are not compatible due to a number of breaking changes. You don’t need to re-initialise the network or re-include devices - just delete the things and add back again.”

8

I did on the original load of the latest Z-Wave binding - but I haven’t done that since I upgraded OH2. I’ll give that a try right now.

9

That fixed it for my test node. 66 more to go. Not sure why the OH2 upgrade would have triggered this when it worked fine on this same binding version before.

1 Like
10

66, ouch! Good luck.

11

I wish there were a way to script this with the Karaf console!