Some time ago I bought 3 Shelly Wave PM Mini (at the same time). These are sensors measuring power and energy but don’t have a relay. I included all of them to my zwave network, added all as Things to openHAB (latest stable version), created and linked Items. Then I disconnected them, put them in a drawer - until a few weeks ago, when the actual use started:
Two are used and work as expected since then: they send measured values as they should.
The last one is used since a few days ago, but it doesn’t send data; only polling works.
The settings are the same (mainUI), but if I look at the Code tab, there are differences. While for the two devices sending data without need for polling there is an entry
group_1:
- controller
it’s empty for the third one
group_1: []
Now my questions are:
Is the different config as show in the Code tab the reason for the different behavior?
Where do the differences come from?
How can I fix that?
I already tried to modify the settings within the Code tab, but this doesn’t seem to have any effect, I don’t think that these modifications are even transferred to the device when saving. But on the UI tab for configuration, there is nothing where I could set the group/controller (also not if I check Show Advanced).
There is likely a difference between the devices. On the UI page for each device what numbers are listed a device type and device ID. Or what is the dbReference
At least one device has a bad configuration in the ZWDB. I suspect it is this one OpenSmartHouse Z-Wave Device Database. There are no associations groups. I can add it, but you will need to modify your jar like this or wait until the binding is updated.
EDIT: went ahead and modified the entry missing the Association group and marked for approval (AFAIK every device needs this group anyway and the device docs show it) If your device matches this one, here is an xml that should work if it replaces the one in your jar file.
Thank you very much for your fast response. Unfortunately what you describe is not the case; I checked the following and it’s all the same for the 3 devices:
In any case I think the updated XML should fix the bad one.
EDIT: an easier first step might be to exclude the bad one and re-include. Maybe there was some variation in the inclusion process. The DB is not correct, but maybe somehow the device can override that.