This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
I have two smartshunts and one mppt in my system.
The VRM advanced widget ”Battery Voltage and Current” seem to be mixing the readings?
I cant edit this widget.
Bug or wrong settings somewhere?
This is the values separately from the smartshunts.
This is the value from the mppt (connected to Bank80)
More info showing that the system info matches info from both smartshunts.
I experience exactly the same on the Dashboard.
I have two cabled smartshunts (with tempsensors on the battery) and two temp/humid sensors from Ruuvi via bluetooth.
On the dashboard i get two widgets for the ruuvis, and one for Battery plus the graph which both seems to flipflop between the two smartshunts. (Funny that the third party ruuvis behave better than the smartshunts)
In the advanced page i have set up custom widgets and avoided the system voltage, and all is fine.
(But there i have issues with the tempsensors on the smartshunts while the Ruuvi's are behaving nicely)
On sep 11 there was practically no charging from my panels and only the globallink and smartshunts were drawing power. This makes it easy to see what is going on.
One bank had about 69% and one about 77% . You can clearly see that it changes between the two values , but it prefers the one with 69% especially in the afternoon :-)
And you can easily see how many values of the four for each hour have been 69% or 77%.
This must be a bug in the VRM itself as the same values behave properly in custom vidgets.
Other than this i really love the globalLink. I use the relay to switch on a Victron Orion-Tr 12/12v which powers my 4g wifi-router,webcam, and lots of Shelly devices to remote my generator etc. Before i found this gizmo i had a lot of messing about to try to save power on remote control and wifi with timers and stuff.
-Goffen
I've identified and fixed a bug today where the VRM side would not consistently select the same device connected to a GlobalLink as the source for the "system" data due to some small timing difference. The bugfix was deployed today; going forwards VRM should more consistently show system data from the same device.
