Since getting updated to Venus 3.60 on my Cerbo, I’m using 500MB/day in bandwidth from my Cerbo to mqtt40.victronenergy.com
Prior to 3.60, I was using 50-85MB/day (still very high), but now it’s crazy high.
The IP address of my Cerbo is 172.30.76.5. I have enabled local SSH access, and temporarily installed a couple of binaries to verify what is causing the traffic (tcpdump and lsof).
In the above, the two connections on port 443 are for MQTT (flashmq), and the port 22 (SSH) connection is the reverse proxy my installer is using to monitor my system remotely from VRM.
As stated, this behavior is new since 3.60, as I was running 3.55 prior to a few days ago. The site in question has limited connectivity, so using 500MB/day means that in a few days I will no longer have access, as my connectivity is limited.
Thanks for any help you can provide. I am VERY comfortable debugging OS and configuration issues regarding services, but am new to solar configuration.
Unfortunately, it appears that if you connect to VRM to monitor the system (even if real-time is disabled), it ‘pulls’ data at a much higher rate from the monitored system, causing much higher data usage.
When I realized this this morning, I disabled the monitoring setup, and traffic has SIGNIFICANTLY decreased.
What would be nice would be the ability to pull the stored data in VRM without it negatively effecting the bandwith on the system, but at this point, at least I have what I believe to be a solution to reduce bandwidth on my remote system.
I’ll continue to monitor the bandwidth and update this topic if anything more comes out.
The main purpose / reason of existence of Grafana is to store low interval data.
Retrieved via MQTT.
Extracting it from the VRM database instead, or getting the (for you now set to 30 minutes) normal VRM data transmits forwarded, is not implemented and also not trivial to implement
Thanks for the details. I’m now running venus-grafana and storing it on a local computer located at my remote instance for detailed analysis.
However, it does make me a bit more leery of using VRM, as doing so causes a huge data hit from my remote site. With that in place, what is the point of reducing the log interval if VRM is just going to be fetching the data in realtime whenever it’s used?
The configured interval is how often the Gx should send data to the vrm database.
Totally separate from that is the mqtt stream of data. Which is on change, used for the real time feature in VRM, used by Grafana, and its active as soon as anyone of those tools “asks for it” (= sends keep alives).
Sorry for the confusion. When using venus-grafana to connect to VRM with real-time updates disabled, the data usage was huge. I was not connected to my local box, I was connected to VRM, and this was causing a huge amount of data to get pulled from my remote to VRM and then over to my grafana instance.
My venus-grafana instance was only connected to VRM.
Because connecting to VRM was the cause of the data usage, that was why I was concerned about using VRM.