One of those entries lists METER_RESET command, the other doesn’t. It looks like OH2.4 uses the entry without METER_RESET since it is not available in paperui.
Can I somehow force it to use the correct entry (or the database has to be updated)?
Will the upgrade force using the latest entry? Now I have dbReference field in properties equal to 397 - that corresponds to the first entry without this channel.
This channel exists in the db entry [1014] but not in [397] that is used by the binding, so the question is how do I force the binding to use entry with this channel defined.
You can’t.
As I said before: you need to find out if your device supports that channel, then we can add it to the database and then your device will be able to use that channel.
As I’ve written before my device does support this channel. The problem is that two database entries are compatible with this device and the wrong one is used.
Device 1014 has minversion less than version of my device thus it is compatible.
Device 397 has minversion “all” and is compatible too.
It is not possible to use the “wrong” device: if you have firmware version 2.32, the 1014 db entry is used, if you have another firmware version, 397 is used.
The meter_reset functionality was added only for firmware version 2.32, see this thread:
I have two of these devices with firmware version 3.94 and none does list it is supported.
Anyway, to end this I will add this channel, if it is not working we will need to remove it later.
