Battery display error noted in V3.60~58 but also in V3.55

I noticed this in V3.60~58 but it is also present in V3.60~60 and V3.55.

Up until 4 weeks ago I had an AGM battery bank. The temperature sensor for the batteries was connected to sensor 1 on the Cerbo GX. DVCC STS was enabled with this temperature sensor chosen.

I then swapped the batteries for NG lithiums with Lynx NG BMS. Before the swap I removed STS and DVCC.

However, the Cerbo GX is still picking up sensor 1 as the displayed battery temperature, not the temperature from the Lynx BMS. Something is persisting in the settings, but as DVCC STS is now forced off there is little that the user can do.

Sreenshots show temperatures, overview 22degC, BMS 17degC and Cerbo temp 1 as 22degC.


K

I’ve previously found that some of the DBus data is persistent - the data remains even if the source of the data is turned off. Rebooting/ power cycling the GX clears this old data.
If you can connect to the Cerbo in superuser mode using SSH from a pc, then you can use DBus -spy to look at this, otherwise try settings>Debug&Develop and see if you can find the value there.

@MikeD thanks for your reply. I have enabled superuser and gone into Debug & Develop and found an entry persisting to the old battery sensor per screenshots below. I tried a power down and restart to no avail. I am not conversant with SSH etc. so I have no idea how to edit this.

With the Lynx BMS forcing off STS it would make sense for it to populate this entry with the battery temperature from the BMS.

On Remote Console

On Cerbo GX directly

@MikeD Further to the post above I used Node Red to create a virtual temperature sensor ID 100 and inject the Lynx BMS battery temperature into that. I then did a one off inject of the text “com.victronenergy.temperature/100/Temperature” to the Venus temperature service (com.victronenergy.settings/Settings/SystemSetup/TemperatureService) so it now reads the battery temperature, albeit indirectly.

I could not get the VenusOS temperature service to read the battery temperature directly. I note in the VenusOS github that there is an item to enable the battery temperature to be used in VenusOS as for example a relay temperature.

Thanks for your prompt, it got me thinking.

I have a small system running with 48V battery, CAN connected BMS, and a 3kW Multiplus2 inverter, and small MPPT charger.
For my system where the BMS provides the temperature, the shared temp sense is forced off and the temp service listed above just shows default.

SSH from a unix console on the LAN: This needs to be enabled on the cerbo, with a password.
This allows you to look at and edit files directly on the Cerbo. It also allows you to run some utility programs like dbus spy. This latter also allows you to look at all the dbus services, and also to edit any value.. note that if you edit a value, if a service is writing this value frequently, then your edit will get promptly over-written. Nice thing is, the cerbo multitasks, so you can open several dbus spy windows and look at both BMS and other Dbus values simultaneously, and watch the interactions.
In your case I’d initially check that the lynx BMS is sharing values properly over the dbus.