Device with duplicate channels (scene_number)

Add-ons Bindings
1

I’ve got a device (in the zwave database here) that is getting the “Duplicate channels zwave:device:ID:nodeXX:scene_number” errors when trying to add them as a thing. Looking in the database it appears that there are, in fact, 2 scene number command classes (COMMAND_CLASS_SCENE_ACTIVATION_V1 and COMMAND_CLASS_CENTRAL_SCENE_V3). From the posts that I’ve read the best fix is for @chris to update the database (the registration page on the zwave database page appears to be disabled, so requesting access myself is unlikely).

So a few questions:

  1. What’s the right process to request a change in the database? (if indeed that’s the problem)

  2. I’ve updated the JAR file with the replacement, removing reference in the XML to the COMMAND_CLASS_SCENE_ACTIVATION_V1 class, and cleared the caches, but it still appears to not have updated anything. Still getting the log files indicating a scene_number conflict… Any thoughts on what to true here?

  3. I’ve tried to use the “thing-types” add-on. After looking at the API, it recognizes the custom XML file, but since the “database” version with the issues is in the list as well (and before the custom one), it appears that the incorrect XML is not overwritten by the thingtypes add-on… Is it possible to use the thing-types add-on to override an existing device type?

Thanks for the help.

2
3

After the jar update did you delete the ui thing page and do an inbox scan?

4

Yes. And even though I was pretty sure that would do nothing, I even excluded and reincluded the device from the network.

5

The scene channels are unlinked?

The device in the DB does seem to be missing association group 1. Probably not the issue, though

"Duplicate channels" error when adding a light switch ZWA4011/58433
6

Yes, unlinked.

I got it working though… I must have skipped a step in the jar update. What worked was:

  1. Updating the JAR. I remove the entry from the database entirely.
  2. Using the console to update the zwave bundle with the jar. Restarting openhab.
  3. Checked the API to make sure the right thing-types were showing up.
  4. Installed thingtypes add-on and added a custom XML with the duplicate class removed.
  5. Re-checked the API to ensure that the thing type was now there.
  6. Removed item from Inbox and re-scanned and added and it worked and came up and is working.

For updating the database to remove the older scene_number class, do I just submit a ticket with the relevant info?

7

Do you know which one is working?

EDIT: when scene activated (in debug mode) what does the byte sequence look like? Is there a 5B or 2B in the sequence, or use the debug viewer to report label. Thanks

8

I’m not really using the scene_number at all, so I’m not in a position to answer the second line of questioning.

I overwrote the definition in the jar for database item 1669 with 1589 and it worked as expected.

EDIT: I attached the XML that I am using for this Thing Type…. a bit of a hybrid between the two, but basically 1589.

cfswitch.xml (12.1 KB)

9

I have a Jasco 4009 and decided to use the central scene channel rather than the scene activation.

Also just noticed that 1589 and 1669 have the same TYPE:ID. This could cause a problem even though the devices look similar. I dropped the type:ID in your XML from 1589 and left on 1669 since that has the scene 1589 does not.

10

Thanks for your help!

1 Like