Why don’t we see time to go estimates for communication enabled batteries? This is such a simple thing, Cerbo knows the ah of the battery, it knows the load, it can easily compute an estimated runtime.. yet it doesn’t unless we have a Victron shunt installed. Why?
Thanks @AJM1 , I’m interested in this too.
I’ve followed your step and enabled my Pylon battery in the MP2 console.
In my VRM battery monitor I see these widget options
Is the “time to go” widget one of these?
If not, could I be on the wrong page or firmware version?
Thanks, David.
Looking more closely at @AJM1 ‘s screenshots , it looks like the icon shown on the “time to go” widget is the same as the smart shunt icon in the device list.
Is there a chance that “time to go” is a feature of the smart shunt rather than the battery bms?
I don’t have a smart shunt so maybe I’m in the same position as @adrummond
ya, the timetogo values are never calculated unless you have a shunt, its incredibly infuriating a $2-300 power station can do this but my full cerbo/bms enabled batteries can’t. This feature is long overdue. worse yet is the timetogo values are read-only so if you use node red to calculate it yourself you cant write the value in yourself. We’ve had to come up with a totally separate dashboard custom built in node red because it wont calculate and display an estimated runtime. bananas!
Ya you are correct if I disable the smartshunt it doesn’t update the graph from bms so definitely pulling timetogo data from shunt.
I’m not sure what a dbus-serialbattery is, I’m discussing close loop (CAN) communication enabled batteries such as EG4, EPOCH or similar batteries.
It’s an aftermarket D-bus driver that couples serial/485 enabled batteries to the Venus OS.
dbus-seriallbattery speaks also with some can-connected batteries
But i checked especially for you:
Even as i use my smartshunt instead of dbus-serialbattery as battery monitor, it still shows the remaining time as in my screenshot