I’ve been running my first solar for about 4 months and learning the Victron tools during the process. Used to be I could watch MPPT stats on the dashboard, but now I only see the total output of all mppts in the “PV Charger” stat. The mppt stats never update after emptying browser cache on Windows, ipad and iphone. My internet connection is excellent. Anyone else ever seen this behavior?
TIA
Not exactly the same issue, but something has definitely changed in VRM. Right at the moment I have 9300W of power coming in from my solar panels. 168A of that are going into my batteries and yet, VRM says the batteries are discharging. This has been happening for more than a week now. The system sometimes decides that it is charging and displays whatever the SOC of the batteries is, but when it decides that it is discharging, the SOC always shows as 86% for some reason. If I look at the Cerbo GX console, it is rock solid, displaying charge and discharge correctly and the SOC stays constant at the real value, so it’s not a local issue.
If anyone (especially from Victron) wants to see this in action, my site is on VRM World at “99 Stephen”.
Hi @irkshnoitz I recommend to first update your GX device to latest official release, and see if that solves it
Hi @away , I checked your system, which is running a recent beta firmware version; and there is definitively something strange going on.
We’ll look into that and report back.
Thank you both for the reports, and note that its two different and unrelated behaviours.
1 Like
Hi @away
Your problem is being caused by two clients on your LAN that have retained old venus MQTT values and are publishing those through the GX to VRM. They are located on 192.168.21.15 and 192.168.20.59, and have core-mosquitto.cerbo as client ID.
Not only that, but because of the duplicate client ID, they are in a connect/kick-out battle all the time.
If I block those IPs from accessing the GX MQTT service, the behavior goes away.
You have to reset those clients, remove their retained message databases (new Venus versions don’t do retained messages anymore, so the problem should not reappear) and give them unique client IDs.
Aah, thank you for that. I recently spun up a Home Assistant instance on 192.168.20.59 and was using it for testing some things. That explains it.
It’s working again. Go figure.