Right, in OH2 it should work that way. Check out this thread and see how to check your node.xml if SCENE_ACTIVATION is a known command. Also ensure you have a recent 2.0 (non-beta at least).
@chris is there a way to modify the zwave database in OH2 and test it before submit a pull request?
I think the SCENE_ACTIVATION is missing in the org.eclipse.smarthome.core.thing.Thing.json file.
Please can you be clear about what the problem is, and what version of the binding you have, and what device you have the problem with. There are too many variables and it will help us help you if you can provide information on your setup.
These fobs should have the scene channel. What version of the binding were you using before this? Has it been updated from an older version (ie were you using 2.0 stable before 2.1?). If so, then I would suggest to delete the thing and add it back again to make sure that you are using the latest thing definition since 2.0 would not have these channels.
So, there’ve been a separate Switch item for every scene number. I removed old xml files before switching to Z-Wave 2.1.0. I can post a section from my org.eclipse.smarthome.core.thing.Thing.json file related to these two things. And here’s what I see in PaperUI for one of these things:
So my question is did you ever use OH2.0? I guess the answer is ‘no’, but I just want to be sure as I don’t see why else the channel wouldn’t be processed other than this at the moment?
The OH1 configuration isn’t really relevant - you can’t use scenes in the same way in OH2 - I think they are all mapped to a number and you need to use a rule to handle them.
I was using OH2.0, but with z-wave 1.9 binding. This is the first time I’m setting up z-wave 2 (version 2.1.0). I understand that now scenes are mapped to numbers, that’s why I created a single Number item for a single KFob channel. Of course I’ll rewrite my rules accordingly, but the key is that the channel (and so the item too) is not being updated when SCENE_ACTIVATION is coming from the device (as you can see in the log snippet above).
There’s nothing obviously wrong - it’s just not processing the event it seems. There are a couple of reasons for this - to try and debug further can you provide a bit more information in the log above - I need to see the received messages which should be a line or two earlier than the log you’ve provided.
I’d also like to see the binding startup since this is where the event handlers are created - maybe there’s something wrong there.
Ok, old logs are already rotated. I will come home in the evening, restart the binding and press some buttons on the fob to trigger commands. One question: startup logs can be actually endless - till what line do you need them?
I want to be able to see the thing initialisation. This should happen in the first minute or so, so if you can grab the first minute of the log it should be fine.
If you like, you can open a ticket on my website (if you’re registered) and attach the log there - you can attach large files and it makes it easier for me to keep track than linking out to dropbox or somewhere…