I think you need to put “%.3f %unit%” in the Metadata of the Item.
Should be fixed, try new build
the binding will also set the pattern to “%.3f %unit%”
Starting openHAB 4.2.0 (Build #3909) on a completely fresh docker image
But sorry … no change when adding the nCurrent or Accumulated Current channels. They’re still on kWh and %.0f
I’m still using the org.openhab.binding.shelly-4.2.0-SNAPSHOT-ncurrent.jar you provided some days before.
of course you new to update to yesterday’s build
“Should be fixed, try new build”
Does this latest build include the fix to the BLU JavaScript file? Or is there a latest build jar file somewhere on the official openHAB github?
o.k. the unit is now correctly set to A
the pattern remains at %.0f A
yes, that’s the trade-off between precision and channel updates creating load and spamming the log when minimal changes to the value (in this case 1 mA would trigger a channel update).
If you like a higher precision try overwriting the default pattern with meta data config
yes triggering updates only for 10mA would be far sufficient enough (which is also in the vicinity of shelly’s measurement capabilities).
I suggest to set the default pattern to %.1f
For now I have no plan to change the logic there, but you could set the pattern according to your needs
fyi: PR has already been merged
Cool thanks for your effort, looking forward to the release!
About that, is that only when OH 4.2 is released that new merged bindings are downloaded?
And otherwise I would have to remove the existing binding, and put a jar file somewhere?
No, I’m working to provide a consolidated DEV build, which can be installed independently from OH 4.2 SNAPSHOTS or releases.
This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.