question

thanks for your response - if you take a look at the screenshot (History data) you can see, that the reported payload is {"value": -1996.800... } - it is not a mater of rounding, these values are physically wrong... There has never ever been a current of 2000 Amps ;)

And: there is no alert or warning tripped, so in my opinion, internally the values are ok, but there is a bug in the reporting module publishing the mqtt data to the broker

can you check the firmware version of the pylontech batteries?

I have added one new US2000C block to my system and probably this could be an issue...

no, I can't...it is said, that in case of an upgrade/change, the newest module (highest S/N and therefore probably the newest FW) must be made master in the stack.

I have checked the firmware versions of the US2000C - every module is up to date (Jan 2023 and Sep 2022 - based on the hardware revision all modules have the latest possible versions: US_C_Nt_V1.7 and US_C_V2.8)

The system operates flawless - there are no errors (temp or over current) logged and the data logged to the VRM-Portal has no glitches - to me, this behavior can only be explained by an internal software bug of the GX module...

I am not alone ;)

I have found a post with similar "glitches" on pylontech batteries:

https://community.victronenergy.com/questions/54257/pylontech-und-ccgx.html?childToView=195792#answer-195792

But: read the content carefully: it is not a matter of linking the batteries with the correct cabling or having a poor CANbus quality - be aware, that the overall performance of the running system is OK: no errors, no faults, no current or temperature warnings, no logs - just wrong values communicated by the GX module (it does not matter if you use mqtt or modbus)...

I hope someone with connections to victron can take a look to this - or give us a feedback how to debug the internal data.

kind regards ;)

Hi, just a note that I’m following this conversation. I am from Victron.

But I have no idea where the bug would be.

The code that takes data from our internal databus (D-Bus); and publishes that to MQTT is here:

https://github.com/victronenergy/dbus-mqtt">https://github.com/victronenergy/dbus-mqtt

Fairly simple code.

I don’t remember ever seen such weird values for DC current in VRM.

Is it always the current that has an issue?

Can you show screenshots of graphs that show how often it happens?

Hi, I have checked my DBs and I was surprised, that my retention policy was set to 7days only on my influxV2 instance - all the data are "collected" by telegraf directly from the internal mqtt broker of the victronGX module. It looks like this:

as you can see: all the values coming from the topic "N/XXX/battery/512/Dc/0/..." seems to be temporarily corrupted - the green SoC seems to be ok, but:

.../Current ...Voltage .../Temperature .../Power

have the same glitches.

I compared the values from .../Voltage and the CellMin and CellMax voltage values from the N/XXX/battery/512/System/MaxCellVoltage and ...MinCellVoltage and copied following screenshot:

The database of my home assistant server although stores the values from the GX-Broker directly:

thanks for keeping an eye on this issue, kind regards ;)

I am running firmware 3.30 as large version and I have the same glitches all over the mqtt values. Here an example:

Value is reported as 1.083,3 kWh and suddenly it goes to 915,03 kWh and back to normal.

I have the suspicion that it has to do with restarting HA (not reboot). Almost everytime I restart HA, my Node-Red instance on the Cerbo (not the HA Addon) crashes and restarts again. Not sure if this two problems are somehow related.