I’m at a loss as to how to configure this scene controller. I have it associated through HABmin (Paper UI throws errors), but I don’t see any channels in HABmin.
After it is associated though HABmin, when I go into Paper UI, it shows that there is a channel already linked called “scene_number”. Seems to be a conflict and I’m not sure which one is right.
When I push buttons on the scene controller, I don’t get any logs showing up in events.log though like I normally do with other zwave devices. Since there are no logs showing up, I don’t know what to do.
Does anyone have any pointers for me? Since it is online, it looks like it should work, but I don’t know what to do next.
Is HABmin showing no channels, or is it showing that there are no items linked to the channels? If the latter, you may be seeing the symptom of a HABmin bug. Refresh the page and it should show the linked items.
You could try putting the zwave binding into debug mode and check for activity in openhab.log when you press buttons on the device.
The database entry for this device was updated pretty recently. What version of openHAB are you running? If you’re on 2.3, it might make sense to upgrade to 2.4 M5 or a recent snapshot version. Be advised, if you are on 2.3 and you do upgrade, please read the post on changes to the Z-Wave binding.
Thanks, when I refresh HABmin, I do see “Scene Number” attached to it, like I do in Paper UI.
When I ran the existing debug logs through the tool, that’s all I saw in there - UPDATE_STATE_NODE_INFO_RECEIVED.
Maybe what I’ll do is exclude, keep it in debug and then include those logs as well. Thanks for the heads up on the log viewer tool.
Stupid question, but the buttons are not mapped to scenes, since I don’t see a way to do that within the binding for the thing. Is that maybe why I’m not seeing any SCENE_ACTIVATION commands? I also don’t see in the documentation on how to do that, as well as searching for VRCS4 examples in the forums.
I was away for a while and finally had a chance to look at this. When I set each group to “controller”, it seemed to fix the issue.
2018-12-05 20:35:24.697 [vent.ItemStateChangedEvent] - zwave_device_512_node21_scene_number changed from 4 to 3
2018-12-05 20:35:30.014 [vent.ItemStateChangedEvent] - zwave_device_512_node21_scene_number changed from 3 to 2
2018-12-05 20:35:32.943 [vent.ItemStateChangedEvent] - zwave_device_512_node21_scene_number changed from 2 to 1
2018-12-05 20:35:39.044 [vent.ItemStateChangedEvent] - zwave_device_512_node21_scene_number changed from 1 to 4