Z-Wave-JS discovered already added Things

With OH version 5.1.0, I switched my Z-Wave devices to Z-Wave JS. They work perfectly.

After updating to OH 5.1.1 or after stop and restart my OH container, all my Z-Wave JS things are new discovered again in the inbox, even though I had already added them using “Add as Thing”.

Could this be because I changed the Thing ID from, for example, node25 to node025 (using three digit number) when adding the things?

This isn’t a problem with other bindings, so does the Z-Wave JS binding work differently?

If it’s due to the Thing ID change, I’d like to go through the trouble of adding all the things again, but I’d prefer to avoid that since I would then also have to reassign the items.

BR Ulf

This indeed can be the issue, as the node id is used as representation property, which is the key to avoid duplicates. Other bindings often use different keys, stored as thing properties, which are not editable.

Probably you’re right. But if so, why I get the correct item state updates :roll_eyes:

I’ll add one or two things with the correct Thing ID to see what happens when I restart OH.

The ID doesn’t break the functioning of the Thing. But it does make is so the Inbox cannot tell if you’ve already included the device it just discovered or not. Some bindings keep track of what’s been discovered (so it doesn’t readd it to the inbox) based on the Thing ID.

Just select and ignore the duplicate Things in the Inbox and they won’t show up any more unless you click “show ignored”.

1 Like

Thanks for the answer from you both, I will ignore the things and change my practice for new devices.