### Describe the bug
The latest Venus update has triggered an odd issue. The d…isplay mode of both of my Cerbo GX devices have changed from Dark display mode to Light display mode, ignoring the display mode selection.
Switching firmware does not fix the issue. I did a factory reset of the Cerbo which fixed the issue, only to return after a reboot which also coincided with the serial driver install.
Executing: bash custom-gui-uninstall.sh, reboot, display mode functionality returns.
Executing: bash custom-gui-install.sh, reboot, display mode switches to Light display mode again.
### How to reproduce
set display mode to dark.
**When serial driver was already installed:**
update firmware to 3.60-71
reboot or downgrade firmware
reload 3.60-71.
**After factory reset**
reboot
install serial driver
reboot
During startup, the splash screen & GUI will switch light mode, and ignore the mode selection.
### Expected behavior
Display Mode should follow the selection option.
### Installation method
Install script from the documentation
### Driver version of the currently installed driver
2.0.20250324rc
### Driver version of the last known working driver
_No response_
### Venus OS device type
Cerbo GX
### Venus OS version
v3.60-71
### BMS type
Jiabaida JDB BMS (LLT Power, Overkill Solar, Smart BMS)
### Cell count
8
### Battery count
1
### Connection type
Serial USB adapter to TTL
### USB hub
Yes, no external power supply
### Config file
```ini
[DEFAULT]
;------------ Setup for Luna's 8S energy battery ---------
; 12/16/2024 PWK first connections, 300aH test
; 12/17/2024 PWK driver update, bump top voltage to 3.52, tune charge ramp to get better balancing.
; 12/22/2024 PWK lowered CCL/DCL Recovery Threshold to 0.8% (1.2A)
; 01/09/2025 PWK Updated driver, changed config.ini to match
; 03/26/2025 PWK Swapped to Cerbo-S after USB fail. changed config.ini to match latest
; 05/08/2025 PWK Firmware failure ~71 req'd reset, reinstall driver & new config from old data
; --------- Set logging level ---------
; ERROR: Only errors are logged
; WARNING: Errors and warnings are logged
; INFO: Errors, warnings, and info messages are logged
; DEBUG: Errors, warnings, info, and debug messages are logged
LOGGING = INFO
; --------- Battery Current Limits ---------
; +++ Limits apply to each individual battery/BMS. +++
; +++ If you have multiple batteries, you need a battery aggregator. +++
MAX_BATTERY_CHARGE_CURRENT = 120.0
MAX_BATTERY_DISCHARGE_CURRENT = 200.0
; --------- Cell Voltages ---------
; Description:
; Calculates the minimum and maximum battery voltage based on the number of cells and their voltage.
; ATTENTION: This does not prevent overcharging or overdischarging of individual cells.
; To prevent overcharging and overdischarging, use these features (enabled by default):
; - Charge Voltage Limitation (prevents overcharging)
; - Cell Voltage Current Limitation (prevents both overcharging and overdischarging)
;
; Example:
; 8 cells * 3.52 V/cell = 28.16 V max charge voltage
; 8 cells * 2.90 V/cell = 23.2 V min discharge voltage
;
; Minimum voltage (can NOT be seen as cut-off voltage)
; Used to:
; - Ensures that the charge voltage limit (CVL) does not fall below the threshold if calculated dynamically
; - Set SOC to 0%, if SOC_CALCULATION is enabled
MIN_CELL_VOLTAGE = 2.900
; Maximum voltage (can be seen as bulk/absorption voltage)
; Used to;
; - Set the maximum charge voltage limit (CVL).
; - Set SOC to 100%, if SOC_CALCULATION is enabled
MAX_CELL_VOLTAGE = 3.520
; Float voltage (can be seen as resting voltage)
; Used to:
; - Set the maximum charging voltage (CVL) after the battery is fully charged
FLOAT_CELL_VOLTAGE = 3.375
; --------- SoC Reset Voltage (must match BMS settings) ---------
; +++ This section is independent and unrelated to the "SoC calculation" section below. +++
; This is used to reset the SoC to 100% periodically to correct SoC drift.
; Description:
; Some BMS systems may need to reset the SoC to 100% periodically due to SoC drift.
; For example, JKBMS resets its internal SoC value if it reaches the upper voltage level.
; Using this method, the charging voltage can be raised regularly to achieve that.
; (Other BMS systems like Daly need an active overwriting of the SoC parameter. This happens each time
; when the charging mode changes from bulk/absorption to float and the cells are equalized. They do
; not need this feature here.)
; Specify the cell voltage at which the SoC should be reset to 100% by the BMS.
; - JKBMS: SoC is reset to 100% if one cell reaches the Over Voltage Protection (OVP) voltage.
; It is recommended to start with OVP voltage - 0.030 (see Example).
; - Increase (add) by 0.005 in steps if the system does not switch to float mode, even if
; the target voltage SOC_RESET_VOLTAGE * CELL_COUNT is reached.
; - Decrease (lower) by 0.005 in steps if the system hits the OVP too fast, before all
; cells could be balanced and the system goes into protection mode multiple times.
; Example:
; If OVP is 3.650, then start with 3.620 and increase/decrease by 0.005.
; Note:
; The value must be higher than the MAX_CELL_VOLTAGE.
; You also have to set CELL_VOLTAGES_WHILE_CHARGING accordingly if you set CCCM_CV_ENABLE to true,
; otherwise the charging current will be reduced to 0 before the target voltage is reached and the
; battery will never switch to float.
SOC_RESET_VOLTAGE = 3.650
; Specify after how many days the SoC reset voltage should be reached again.
; The timer is reset when the SoC reset voltage is reached.
; Leave empty if you don't want to use the SoC reset feature.
; Example:
; Value is set to 15
; day 1: SoC reset reached once
; day 16: SoC reset reached twice
; day 31: SoC reset not reached since it's very cloudy
; day 34: SoC reset reached since the sun came out
; day 49: SoC reset reached again, since last time it took 3 days to reach SoC reset voltage
SOC_RESET_AFTER_DAYS =
; --------- SoC Calculation ---------
; +++ This section is independent and unrelated to the "SoC reset voltage" section above. +++
; Description:
; Calculate SoC in driver instead of using BMS reported SoC.
; Cannot be used with EXTERNAL_SENSOR_DBUS_PATH_SOC.
; True:
; Calculate SoC in driver.
; - Integrate current reported.
; - Set SoC to 100% when battery switches to float mode (requires CVCM_ENABLE to be enabled).
; - Set SoC to 0% if:
; * Lowest cell voltage <= MIN_CELL_VOLTAGE.
; * Battery is discharging for at least 300 seconds.
SOC_CALCULATION = False
; --------- Current correction ---------
; Correct the current reported by the BMS using a correction list.
; CURRENT_REPORTED_BY_BMS: List of current values reported by the BMS.
; CURRENT_MEASURED_BY_USER: List of current values measured by the user.
; If the lists are the same, this feature is disabled.
; Example to set small currents to zero:
; CURRENT_REPORTED_BY_BMS = -300, -0.5, 0.5, 300
; CURRENT_MEASURED_BY_USER = -300, 0.0, 0.0, 300
; Example to set zero current to a small current:
; CURRENT_REPORTED_BY_BMS = -300, -1, 0.0, 0.1, 1, 300
; CURRENT_MEASURED_BY_USER = -300, -1, -0.4, 0.0, 1, 300
CURRENT_REPORTED_BY_BMS = -300, 300
CURRENT_MEASURED_BY_USER = -300, 300
; --------- BMS Disconnect Behavior ---------
; Description:
; Block charge and discharge when communication with the BMS is lost. If you are removing the
; BMS intentionally, you must restart the driver/system to reset the block.
; True:
; Charge and discharge are blocked immediately on BMS communication loss. They are unblocked when the connection is re-established
; or the driver/system is restarted. This is the default behavior for Victron Energy devices.
BLOCK_ON_DISCONNECT = True
; --------- Charge Mode ---------
; Choose the mode for voltage/current limitations.
; 1: Linear mode with smoother values.
; For CCL and DCL, values between steps are calculated for smoother transitions.
; 2: Step mode with limitations on hard boundary steps.
CHARGE_MODE = 1
; Specify in seconds how often the linear values should be recalculated.
CVL_RECALCULATION_EVERY = 60
; Specify the percentage change that triggers an immediate recalculation of linear values.
; Example:
; 33 means an immediate change when the value changes by more than 33%.
CVL_RECALCULATION_ON_MAX_PERCENTAGE_CHANGE = 33
; --------- Charge Voltage Limitation (affecting CVL) ---------
; Description:
; Limit the maximum charging voltage (MAX_CELL_VOLTAGE * cell count), switch from max voltage to float
; voltage (FLOAT_CELL_VOLTAGE * cell count) and back.
; True: Max charging voltage is reduced based on charge mode.
; After max voltage is reached and cell voltage difference is smaller or equal to
; SWITCH_TO_FLOAT_CELL_VOLTAGE_DIFF, it switches to float voltage after SWITCH_TO_FLOAT_WAIT_FOR_SEC
; additional seconds.
; After cell voltage difference is greater or equal to SWITCH_TO_BULK_CELL_VOLTAGE_DIFF
; OR
; SoC is below SWITCH_TO_BULK_SOC_THRESHOLD,
; it switches back to max voltage.
; Example when set to True:
; The battery reaches a max voltage of 28.16 V and the max cell difference is 0.010 V, then switch to float
; voltage of 27.0 V after 900 additional seconds to reduce stress on the batteries. Max voltage of
; 28.16 V is allowed again if the max cell difference exceeds 0.080 V or SoC drops below 80%.
; Enable charge voltage control management (True/False).
CVCM_ENABLE = True
; -- CVL switch to float
; INFO: If SWITCH_TO_FLOAT_WAIT_FOR_SEC and SWITCH_TO_FLOAT_CELL_VOLTAGE_DIFF are disabled, the battery will switch instantly to
; float voltage when max voltage is reached.
; ---- Based on time ----
; Specify how long the max voltage should be maintained.
; If cells are balanced, maintain max voltage for an additional SWITCH_TO_FLOAT_WAIT_FOR_SEC seconds.
; To disable, leave empty or set to 0.
SWITCH_TO_FLOAT_WAIT_FOR_SEC = 900
; ---- Based on cell voltage difference ----
; Specify the cell voltage difference where CVL is maintained until the difference is equal or lower.
; To disable, leave empty or set to 10.
SWITCH_TO_FLOAT_CELL_VOLTAGE_DIFF = 0.015
; Specify the cell voltage difference threshold for restarting SWITCH_TO_FLOAT_WAIT_FOR_SEC.
; Example:
; If SWITCH_TO_FLOAT_CELL_VOLTAGE_DIFF is 0.010 and SWITCH_TO_FLOAT_CELL_VOLTAGE_DEVIATION is 0.003,
; the timer will restart if the cell voltage difference exceeds 0.013 V (0.010 + 0.003).
SWITCH_TO_FLOAT_CELL_VOLTAGE_DEVIATION = 0.003
; -- CVL switch to bulk/absorption
; WARNING: If SWITCH_TO_BULK_SOC_THRESHOLD and SWITCH_TO_BULK_CELL_VOLTAGE_DIFF are disabled, the battery will stay at the float
; voltage until the driver/system is restarted.
; ---- Based on SoC ----
; Specify the SoC level where CVL is reset to max voltage (bulk/absorption).
; To disable, leave empty or set to 0.
SWITCH_TO_BULK_SOC_THRESHOLD = 80
; ---- Based on cell voltage difference ----
; Specify the cell voltage difference where CVL is reset to max voltage (bulk/absorption) if the value exceeds this threshold.
; As a guideline: Cells are considered imbalanced if the cell difference exceeds 5% of the nominal cell voltage.
; Example: 3.2 V * 5 / 100 = 0.160 V
; To disable, leave empty or set to 10.
SWITCH_TO_BULK_CELL_VOLTAGE_DIFF = 0.080
; --------- Cell Voltage Limitation (affecting CVL) ---------
; This function prevents overcharging of single cells in a poorly balanced battery, which could cause the BMS to switch off due to overvoltage.
;
; Example:
; 7 cells are at 3.5 V, 1 cell is at 3.6 V. The total battery voltage is 28.10 V, and the Victron System sees no reason to
; lower the charging current as the control voltage (absorption voltage) is 28.16 V.
; In this case, the cell voltage limitation kicks in and lowers the control voltage to keep it close to the MAX_CELL_VOLTAGE.
;
; In theory, this can also be done with CCL, but doing it with CVL has 2 advantages:
; - In a well-balanced system, the current can be kept quite high until the end of charge by using MAX_CELL_VOLTAGE for charging.
; - In systems with MPPTs and DC-feed-in activated, the Victron systems do not respect CCL, so CVL is the only way to prevent the
; highest cell in a poorly balanced system from overcharging.
;
; There are different methods implemented to calculate CVL when a cell exceeds MAX_CELL_VOLTAGE:
; 1. P-Controller (penalty sum method)
; The voltage overshoot of all cells that exceed MAX_CELL_VOLTAGE is summed up, and the control voltage is lowered by this "penalty sum".
; This is calculated every CVL_RECALCULATION_EVERY seconds.
; 2. I-Controller
; An I-Controller tries to control the voltage of the highest cell to MAX_CELL_VOLTAGE + SWITCH_TO_FLOAT_CELL_VOLTAGE_DIFF.
; (for example, 3.52 V + 0.01 V = 3.62 V). If the voltage of the highest cell is above this level, CVL is reduced. If the voltage is below, CVL is
; increased until cell count * MAX_CELL_VOLTAGE.
; An I-Part of 0.2 V/Vs (CVL_ICONTROLLER_FACTOR) has proven to provide stable and fast control behavior.
; This method is not as fast as the Penalty Sum Method but is usually smoother and more stable against toggling and has no stationary deviation.
; More info: https://github.com/Louisvdw/dbus-serialbattery/pull/882
;
; 0: Disabled
; 1: P-Controller (penalty sum method)
; 2: I-Controller
CVL_CONTROLLER_MODE = 1
; I-Controller factor (V/Vs)
CVL_ICONTROLLER_FACTOR = 0.2
; --------- Cell Voltage Current Limitation (affecting CCL/DCL) ---------
; Description:
; The maximum charge/discharge current will be increased or decreased depending on the minimum and maximum cell voltages.
; Example:
; 8 cells * 3.52 V/cell = 28.16 V max charge voltage
; 8 cells * 2.90 V/cell = 23.20 V min discharge voltage
; In reality, not all cells reach the same voltage at the same time. The (dis)charge current
; will be (in-/)decreased if even one single battery cell reaches the limits.
; Enable charge current control management based on cell voltage (True/False).
CCCM_CV_ENABLE = True
; Enable discharge current control management based on cell voltage (True/False).
DCCM_CV_ENABLE = True
; Set steps to reduce battery current.
; The current will be changed linearly between these steps if LINEAR_LIMITATION_ENABLE is set to True.
CELL_VOLTAGES_WHILE_CHARGING = 3.570, 3.520, 3.495, 3.470, 3.445
MAX_CHARGE_CURRENT_CV_FRACTION = 0.000, 0.005, 0.050, 0.250, 1.000
CELL_VOLTAGES_WHILE_DISCHARGING = 2.800, 2.900, 3.000, 3.100, 3.190
MAX_DISCHARGE_CURRENT_CV_FRACTION = 0.000, 0.005, 0.050, 0.250, 1.000
; --------- Temperature Current Limitation (affecting CCL/DCL) ---------
; Description:
; The maximum charge/discharge current will be increased or decreased depending on temperatures.
; NOTE: The temperatures are in °Celsius. Temperature sensors 1 to 4 are used for the calculation.
; Example:
; The temperature limit will be monitored to control the currents. If there are two temperature sensors,
; the worst case will be calculated, and the more secure lower current will be set.
; Enable charge current control management based on temperature (True/False).
CCCM_T_ENABLE = True
; Enable discharge current control management based on temperature (True/False).
DCCM_T_ENABLE = True
; Set steps to reduce battery current.
; The current will be changed linearly between these steps if CHARGE_MODE is set to 1 (linear).
TEMPERATURES_WHILE_CHARGING = 0, 2, 5, 10, 40, 45, 50, 55
MAX_CHARGE_CURRENT_T_FRACTION = 0.00, 0.25, 0.50, 1.00, 1.00, 0.50, 0.25, 0.00
TEMPERATURES_WHILE_DISCHARGING = -10, 0, 5, 10, 40, 45, 50, 55
MAX_DISCHARGE_CURRENT_T_FRACTION = 0.00, 0.25, 0.50, 1.00, 1.00, 0.50, 0.25, 0.00
; --------- MOSFET Temperature Current Limitation (affecting CCL/DCL) ---------
; Description:
; The maximum charge/discharge current will be increased or decreased depending on MOSFET temperatures.
; NOTE: The temperatures are in °Celsius. MOSFET temperature sensor is only used if available.
; Example:
; The MOSFET temperature limit will be monitored to control the currents.
; Enable charge current control management based on MOSFET temperature (True/False).
CCCM_T_MOSFET_ENABLE = True
; Enable discharge current control management based on MOSFET temperature (True/False).
DCCM_T_MOSFET_ENABLE = True
; Set steps to reduce battery current.
; The current will be changed linearly between these steps if CHARGE_MODE is set to 1 (linear).
MOSFET_TEMPERATURES_WHILE_CHARGING = 70, 80, 90
MAX_CHARGE_CURRENT_T_MOSFET_FRACTION = 1.00, 0.25, 0.00
MOSFET_TEMPERATURES_WHILE_DISCHARGING = 70, 80, 90
MAX_DISCHARGE_CURRENT_T_MOSFET_FRACTION = 1.00, 0.25, 0.00
; --------- CCL/DCL Recovery Threshold ---------
; Description:
; This threshold applies if any of the following limitations are enabled:
; - Cell Voltage Current Limitation (CCCM_CV_ENABLE, DCCM_CV_ENABLE)
; - Temperature Limitation (CCCM_T_ENABLE, DCCM_T_ENABLE)
; - SoC Limitation (CCCM_SOC_ENABLE, DCCM_SOC_ENABLE)
; Once the current reaches 0, it will only increase again if it exceeds this threshold.
; The threshold is a percentage of the maximum charge/discharge current.
; This prevents rapid switching (flapping) between allowing and blocking charge/discharge, which can cause system instability and excessive notifications.
; Example:
; If the maximum charge current is 120 A and the threshold is set to 0.0045 (0.45%), the current must exceed 0.54A (120A * 0.0045) before charging resumes.
; If the maximum discharge current is 200 A and the threshold is set to 0.02 (2.0%), the current must exceed 4A (200A * 0.02) before discharging resumes.
CHARGE_CURRENT_RECOVERY_THRESHOLD_PERCENT = 0.0045
DISCHARGE_CURRENT_RECOVERY_THRESHOLD_PERCENT = 0.02
; --------- Time-To-Go ---------
; Description:
; Calculates the time remaining until the battery reaches a specific SoC, shown in the GUI.
; If ESS is enabled and an "Optimized..." option is selected, it uses the SoC limit of the ESS system.
; Otherwise, it uses SOC_LOW_WARNING from the config file.
; Recalculation is done based on TIME_TO_SOC_RECALCULATE_EVERY.
TIME_TO_GO_ENABLE = True
; --------- Time-To-Soc ---------
; Description:
; Calculates the time remaining until the battery reaches specific SoC levels.
; Example:
; TIME_TO_SOC_POINTS = 50, 25, 15, 0
; 6h 24m remaining until 50% SoC
; 17h 36m remaining until 25% SoC
; 22h 5m remaining until 15% SoC
; 28h 48m remaining until 0% SoC
; Set of SoC percentages to report on dbus and MQTT. The more you specify, the more it will impact system performance.
; [Valid values 0-100, comma-separated list. More than 20 intervals are not recommended]
; Example: TIME_TO_SOC_POINTS = 100, 95, 90, 85, 75, 50, 25, 20, 10, 0
; Leave empty to disable.
TIME_TO_SOC_POINTS =
; Specify TimeToSoc value type [Valid values 1, 2, 3]
; 1 Seconds
; 2 Time string <days>d <hours>h <minutes>m <seconds>s
; 3 Both seconds and time string "<seconds> [<days>d <hours>h <minutes>m <seconds>s]"
TIME_TO_SOC_VALUE_TYPE = 1
; Specify in seconds how often the TimeToSoc should be recalculated.
; Minimum is 5 seconds to prevent CPU overload.
TIME_TO_SOC_RECALCULATE_EVERY = 60
; Include TimeToSoC points when moving away from the SoC point [Valid values True, False]
; These will be shown as negative time. Disabling this improves performance slightly.
TIME_TO_SOC_INC_FROM = False
; --------- History ---------
; Description:
; Calculate the history values of the battery, that are not available from the BMS.
HISTORY_ENABLE = True
; --------- Additional settings ---------
; Specify one or more BMS types (separated by a comma) to load, or leave empty to try to load all available.
;
BMS_TYPE = LltJbd
; Exclude these serial devices from the driver startup.
; Example:
; /dev/ttyUSB2, /dev/ttyUSB4
EXCLUDED_DEVICES =
; BMS poll interval in seconds.
; If the driver consumes too much CPU, you can increase this value to reduce the refresh rate
; and CPU usage.
; Default for most BMS is 1 second; some BMS may have a higher value.
; Leave empty to use the BMS default value; decimal values are allowed.
POLL_INTERVAL = 1
; Publish the config settings to the dbus path "/Info/Config/".
PUBLISH_CONFIG_VALUES = True
; Make all battery data available on MQTT as JSON under the topic "/N/<VRM_ID>/battery/<BATTERY_INSTANCE>/JsonData".
; This topic can be used to feed dbus-mqtt-battery or other MQTT clients.
PUBLISH_BATTERY_DATA_AS_JSON = True
; Select the format of cell data presented on dbus.
; 0 Do not publish all the cells (only the min/max cell data as used by the default GX)
; 1 Format: /Voltages/Cell (also available for display on Remote Console)
; 2 Format: /Cell/#/Volts
; 3 Both formats 1 and 2
BATTERY_CELL_DATA_FORMAT = 1
; Battery temperature
; Specify how the battery temperature is calculated.
; Provide a comma-separated list of temperature sensor numbers to use for the calculation.
; The temperature will be calculated as the average of the specified sensors.
; Example: TEMPERATURE_SOURCE_BATTERY = 1, 2, 3, 4
; This will use temperature sensors 1, 2, 3, and 4 to calculate the average battery temperature.
TEMPERATURE_SOURCE_BATTERY = 1, 2
; Temperature sensor 1 name
TEMP_1_NAME = Temp 1
; Temperature sensor 2 name
TEMP_2_NAME = Temp 2
; Temperature sensor 3 name
TEMP_3_NAME = Temp 3
; Temperature sensor 4 name
TEMP_4_NAME = Temp 4
; Show additional info in GUI -> Serialbattery -> Parameters.
; This will show additional information to better understand how the driver works
; and what values are currently set which are not shown elsewhere in the GUI.
; You have to scroll down to see the additional information.
GUI_PARAMETERS_SHOW_ADDITIONAL_INFO = True
; Telemetry settings
; To help us improve the driver, we are collecting telemetry data. This data is anonymous and
; will only be used to improve the driver. The data is sent once every week.
; You can disable this feature by setting this value to False.
; Some data we collect: Venus OS version, driver version, driver runtime, battery type, battery count.
TELEMETRY = True
; --------- BMS specific settings ---------
; -- LltJbd settings
; SoC low levels
; Note:
; SOC_LOW_WARNING can be used to calculate the Time-To-Go, even if you are not using an LltJbd BMS.
SOC_LOW_WARNING = 20
SOC_LOW_ALARM = 10
```
### Relevant log output
```shell
/data/log/dbus-serialbattery.ttyUSB2$ cat current | tai64nlocal
2025-05-09 11:57:13.558182500 INFO:SerialBattery:
2025-05-09 11:57:13.559325500 INFO:SerialBattery:Starting dbus-serialbattery
2025-05-09 11:57:13.561866500 INFO:SerialBattery:Venus OS v3.60~71 running on Cerbo-S GX
2025-05-09 11:57:13.562611500 INFO:SerialBattery:dbus-serialbattery v2.0.20250324rc
2025-05-09 11:57:29.563778500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2025-05-09 11:57:29.564575500 INFO:SerialBattery:Testing LltJbd at address "\x00"
2025-05-09 11:57:30.059753500 ERROR:SerialBattery:>>> ERROR: BMS send insufficient data. Received 11 expected 7
2025-05-09 11:57:31.088604500 INFO:SerialBattery:-- Connection established to LltJbd
2025-05-09 11:57:32.181109500 INFO:SerialBattery:Reconnected to previously identified battery with DeviceInstance: 1
2025-05-09 11:57:32.555686500 INFO:SerialBattery:Use DeviceInstance: 1
2025-05-09 11:57:32.557689500 INFO:SerialBattery:Use dbus ServiceName: com.victronenergy.battery.ttyUSB2
2025-05-09 11:57:32.645192500 INFO:SerialBattery:Polling interval: 1.000 s
2025-05-09 11:57:32.656741500 INFO:SerialBattery:Battery LLT/JBD connected to dbus from /dev/ttyUSB2
2025-05-09 11:57:32.657855500 INFO:SerialBattery:========== Settings ==========
2025-05-09 11:57:32.658942500 INFO:SerialBattery:> Connection voltage: 25.96 V | Current: 6.18 A | SoC: 41%
2025-05-09 11:57:32.659791500 INFO:SerialBattery:> Cell count: 8 | Cells populated: 8
2025-05-09 11:57:32.660484500 INFO:SerialBattery:> CHARGE MODE: Linear
2025-05-09 11:57:32.661204500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.900 V | MAX CELL VOLTAGE: 3.520 V| FLOAT CELL VOLTAGE: 3.375 V
2025-05-09 11:57:32.661880500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 120.0 A | MAX BATTERY DISCHARGE CURRENT: 200.0 A
2025-05-09 11:57:32.662817500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 200.0 A | MAX BATTERY DISCHARGE CURRENT: 300.0 A (read from BMS)
2025-05-09 11:57:32.663719500 INFO:SerialBattery:> CVCM: True
2025-05-09 11:57:32.666009500 INFO:SerialBattery:> CCCM CV: True | DCCM CV: True
2025-05-09 11:57:32.673578500 INFO:SerialBattery:> CCCM T: True | DCCM T: True
2025-05-09 11:57:32.681924500 INFO:SerialBattery:> CCCM T MOS: True | DCCM T MOS: True
2025-05-09 11:57:32.681933500 INFO:SerialBattery:> CCCM SOC: False | DCCM SOC: False
2025-05-09 11:57:32.681936500 INFO:SerialBattery:> CHARGE FET: True | DISCHARGE FET: True | BALANCE FET: True
2025-05-09 11:57:32.681940500 INFO:SerialBattery:Serial Number/Unique Identifier: 39_304.0Ah
```
### Any other information that may be helpful
_No response_
### Please confirm that you have completed the following steps before submitting your support request
- [x] I have carefully read all the instructions above including the descriptions.
- [x] I have tried the `nightly` build first, if I was not already using it. This means the logs I provide are from the `nightly` build.
- [x] I have rebooted at least once after I saw the issue.
- [x] I have read the complete [changelog](https://github.com/mr-manuel/dbus-serialbattery/blob/master/CHANGELOG.md).
- [x] I have provided the logfiles in the correct format with a HUMAN READABLE timestamp by piping it through `tai64nlocal`.
- [ ] I have clicked all checkboxes because I did not read the instructions.
