You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a Multiplus-II 48/5000/70-50 inverter, and in the VRM overview, I currently observe fluctuating grid values on the left side, varying between 90W and 110W. On the right side, under AC Loads, the values shift between approximately 85W and 92W.
If I'm not mistaken, these values correspond to the following Home Assistant entities:
Vebus Active In L1 Power (sensor.victron_vebus_activein_l1_power_228)
Vebus Out L1 Power (sensor.victron_vebus_out_l1_power_228)
However, I've noticed an issue: the first value only shows either 90W or 100W, without registering anything in between, while the VRM clearly displays a range of values within this spectrum.
Similarly, the second value alternates between 80W and 90W, with no readings in between, despite VRM showing more precise fluctuations.
The text was updated successfully, but these errors were encountered:
Unfortunately the modbus server endpoint provided by victron doesn't return values as finegrained as can be seen on the VRM for some entities.
This integration does not scale/round wattage (power) related entities.
You can open an issue on https://github.com/victronenergy/dbus_modbustcp to see if victron would like to change this behaviour.
I have a Multiplus-II 48/5000/70-50 inverter, and in the VRM overview, I currently observe fluctuating grid values on the left side, varying between 90W and 110W. On the right side, under AC Loads, the values shift between approximately 85W and 92W.
If I'm not mistaken, these values correspond to the following Home Assistant entities:
However, I've noticed an issue: the first value only shows either 90W or 100W, without registering anything in between, while the VRM clearly displays a range of values within this spectrum.
Similarly, the second value alternates between 80W and 90W, with no readings in between, despite VRM showing more precise fluctuations.
The text was updated successfully, but these errors were encountered: