yes, it clear now: a known issue in gui-v2. we’ll fix it.
1 Like
I have a related suggestion that I believe would open the door to many innovative use cases for the boat page: Allow setting a preferred ‘battery monitor’ other than the systemwide selected one.
And in extension thereof, allow independent selection of preferred data sources for all the values on display on the boat page:
- gps
- motor
- battery monitor
- ..other.. ?
That would truly free the boat page’s function/utility from it’s current restriction that it is assumed that the propulsion subsystem (including battery) and the energy storage subsystem (AC house/boat loads) are running from the same battery. Which is, in my humble opinion, not aligned with best practice systems design for maritime installations: better keep propulsion capacity and (boat)house loads capacity separate and isolated.
This way there would be a logical and useful separation of user interface functionality: boat page having boat propulsion focus , overview page having house / ESS focus and brief page allowing a customized overview of both combined.
I wonder whether this might be possible already:
What happens if we set the propulsion battery BMV Smartshunt instance to a lower value than that of the house battery BMV and manually select the house battery BMV (or the MP-II) battery monitor as primary battery monitor for VenusOS/ESS?
Those flows use the bigSSH node to enable commands as root from within Node-RED when there is no route available to SSH into the Cerbo otherwise. Setting the instance values worked the last time I tried, but didn’t have the desired effect (yet).