search

Louisvdw / dbus-serialbattery

Battery Monitor driver for serial battery in VenusOS GX systems
MIT License
541 stars 165 forks source link

JKBMS with RS485 connection: Battery SoC does not reset to 100% #995

Closed tfboy closed 8 months ago

tfboy commented 8 months ago

Describe the problem

Battery SoC is slowly reducing, despite being fully charged. I know there's a "100% reset SoC" function available but I believe only with Bluetooth connection and not RS485 which is what I'm using. I did read a thread which suggested some tweaks and the newer driver would fix the reset value which I believe JK say is not possible over serial, only BLE. Right now, I believe the battery is fully charged showing over 3.5V per cell when solar is providing charge. No current is going in, battery is in absorption, but battery SoC never goes above 83% when I believe it should be 95%+.

Driver version

v1.2.20240227beta

Venus OS device type

Cerbo GX

Venus OS version

v3.13

BMS type

JKBMS / Heltec BMS

Cell count

16

Battery count

1

Connection type

Serial USB adapter to RS485

Config file

[DEFAULT]

; --------- Battery Current limits ---------
MAX_BATTERY_CHARGE_CURRENT    = 120.0
MAX_BATTERY_DISCHARGE_CURRENT = 140.0

; --------- Cell Voltages ---------
; Description: Cell min/max voltages which are used to calculate the min/max battery voltage
; Example: 16 cells * 3.45V/cell = 55.2V max charge voltage. 16 cells * 2.90V = 46.4V min discharge voltage
MIN_CELL_VOLTAGE   = 2.700
; Max voltage can seen as absorption voltage
MAX_CELL_VOLTAGE   = 3.510
FLOAT_CELL_VOLTAGE = 3.400

; --------- SOC reset voltage ---------
; Description: May be needed to reset the SoC to 100% once in a while for some BMS, because of SoC drift.
;              Specify the cell voltage where the SoC should be reset to 100% by the BMS.
;                - JKBMS: SoC is reset to 100% if one cell reaches OVP (over voltage protection) voltage
;              As you have to adopt this value to your system, I reccomend to start with
;              OVP voltage - 0.030 (see Example).
;                - Try to 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.
;                - Try to 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 has to be higher as the MAX_CELL_VOLTAGE
SOC_RESET_VOLTAGE = 3.525
; 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 this
; 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 =

; --------- Charge mode ---------
; Choose the mode for voltage / current limitations (True / False)
; False is a step mode: This is the default with limitations on hard boundary steps
; True is a linear mode:
;     For CCL and DCL the values between the steps are calculated for smoother values (by WaldemarFech)
;     For CVL max battery voltage is calculated dynamically in order that the max cell voltage is not exceeded
LINEAR_LIMITATION_ENABLE = True

; Specify in seconds how often the linear values should be recalculated
LINEAR_RECALCULATION_EVERY = 60
; Specify in percent when the linear values should be recalculated immediately
; Example: 5 for a immediate change, when the value changes by more than 5%
LINEAR_RECALCULATION_ON_PERC_CHANGE = 5

; --------- Charge Voltage limitation (affecting CVL) ---------
; Description: Limit max charging voltage (MAX_CELL_VOLTAGE * cell count), switch from max voltage to float
;              voltage (FLOAT_CELL_VOLTAGE * cell count) and back
;     False: Max charging voltage is always kept
;     True: Max charging voltage is reduced based on charge mode
;         Step mode: After max voltage is reached for MAX_VOLTAGE_TIME_SEC it switches to float voltage. After
;                    SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT it switches back to max voltage.
;         Linear mode: After max voltage is reachend and cell voltage difference is smaller or equal to
;                      CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL it switches to float voltage after 300 (fixed)
;                      additional seconds.
;                      After cell voltage difference is greater or equal to CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT
;                      OR
;                      SoC is below SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT
;                      it switches back to max voltage.
; Example: The battery reached max voltage of 55.2V and hold it for 900 seconds, the the CVL is switched to
;          float voltage of 53.6V to don't stress the batteries. Allow max voltage of 55.2V again, if SoC is
;          once below 90%
;          OR
;          The battery reached max voltage of 55.2V and the max cell difference is 0.010V, then switch to float
;          voltage of 53.6V after 300 additional seconds to don't stress the batteries. Allow max voltage of
;          55.2V again if max cell difference is above 0.080V or SoC below 90%.
; Charge voltage control management enable (True/False).
CVCM_ENABLE = True

; -- CVL reset based on cell voltage diff (linear mode)
; Specify cell voltage diff where CVL limit is kept until diff is equal or lower
CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_UNTIL = 0.010
; Specify cell voltage diff where CVL limit is reset to max voltage, if value get above
; the cells are considered as imbalanced, if the cell diff exceeds 5% of the nominal cell voltage
; e.g. 3.2 V * 5 / 100 = 0.160 V
CELL_VOLTAGE_DIFF_TO_RESET_VOLTAGE_LIMIT = 0.160

; -- CVL reset based on SoC option (step mode)
; Specify how long the max voltage should be kept, if reached then switch to float voltage
MAX_VOLTAGE_TIME_SEC = 900
; Specify SoC where CVL limit is reset to max voltage, if value gets below
SOC_LEVEL_TO_RESET_VOLTAGE_LIMIT = 90

; --------- Cell Voltage Current limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be in-/decreased depending on min and max cell voltages
; Example: 18 cells * 3.55V/cell = 63.9V max charge voltage
;          18 cells * 2.70V/cell = 48.6V min discharge voltage
;          But 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

; Charge current control management referring to cell-voltage enable (True/False).
CCCM_CV_ENABLE = True
; Discharge current control management referring to cell-voltage enable (True/False).
DCCM_CV_ENABLE = True

; Set steps to reduce battery current
; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True
CELL_VOLTAGES_WHILE_CHARGING   = 3.55, 3.50, 3.45, 3.40
MAX_CHARGE_CURRENT_CV_FRACTION =    0, 0.1,  0.5,    1

CELL_VOLTAGES_WHILE_DISCHARGING   = 2.70, 2.80, 2.90, 3.10
MAX_DISCHARGE_CURRENT_CV_FRACTION =    0,  0.1,  0.5,    1

; --------- Temperature limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be in-/decreased depending on temperature
; Example: The temperature limit will be monitored to control the currents. If there are two temperature senors,
;          then the worst case will be calculated and the more secure lower current will be set.
; Charge current control management referring to temperature enable (True/False).
CCCM_T_ENABLE = True
; Charge current control management referring to temperature enable (True/False).
DCCM_T_ENABLE = True

; Set steps to reduce battery current
; The current will be changed linear between those steps if LINEAR_LIMITATION_ENABLE is set to True
TEMPERATURE_LIMITS_WHILE_CHARGING = 0,   2,   5,  10,  15, 20, 35,  45, 55
MAX_CHARGE_CURRENT_T_FRACTION     = 0, 0.1, 0.4, 0.6, 0.8,  1,  1, 0.8,  0

TEMPERATURE_LIMITS_WHILE_DISCHARGING = -20,   0,   5,  10, 15, 45, 55
MAX_DISCHARGE_CURRENT_T_FRACTION     =   0, 0.2, 0.5, 0.8,  1,  1,  0

; --------- SOC limitation (affecting CCL/DCL) ---------
; Description: Maximal charge / discharge current will be increased / decreased depending on State of Charge,
;              see CC_SOC_LIMIT1 etc.
; Example: The SoC limit will be monitored to control the currents.
; Charge current control management enable (True/False).
CCCM_SOC_ENABLE = True
; Discharge current control management enable (True/False).
DCCM_SOC_ENABLE = True

; Charge current soc limits
CC_SOC_LIMIT1 = 98
CC_SOC_LIMIT2 = 95
CC_SOC_LIMIT3 = 91

; Charge current limits
CC_CURRENT_LIMIT1_FRACTION = 0.05
CC_CURRENT_LIMIT2_FRACTION = 0.3
CC_CURRENT_LIMIT3_FRACTION = 0.5

; Discharge current soc limits
DC_SOC_LIMIT1 = 10
DC_SOC_LIMIT2 = 15
DC_SOC_LIMIT3 = 20

; Discharge current limits
DC_CURRENT_LIMIT1_FRACTION = 0.1
DC_CURRENT_LIMIT2_FRACTION = 0.3
DC_CURRENT_LIMIT3_FRACTION = 0.5

; --------- Time-To-Go ---------
; Description: Calculates the time to go shown in the GUI
;              Recalculation is done based on TIME_TO_SOC_RECALCULATE_EVERY
TIME_TO_GO_ENABLE = True

; --------- Time-To-Soc ---------
; Description: Calculates the time to a specific SoC
; 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 that 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 are 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 as negative time. Disabling this improves performance slightly
TIME_TO_SOC_INC_FROM = False

; Publish the config settings to the dbus path "/Info/Config/"
PUBLISH_CONFIG_VALUES = 1

; Select the format of cell data presented on dbus [Valid values 0,1,2,3]
; 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

; Simulate Midpoint graph (True/False).
MIDPOINT_ENABLE = False

; Battery temperature
; Specify how the battery temperature is assembled
; 0 Get mean of temperature sensor 1 to sensor 4
; 1 Get only temperature from temperature sensor 1
; 2 Get only temperature from temperature sensor 2
; 3 Get only temperature from temperature sensor 3
; 4 Get only temperature from temperature sensor 4
TEMP_BATTERY = 0

; Temperature sensor 1 name
TEMP_1_NAME = Temp 1

; Temperature sensor 2 name
TEMP_2_NAME = Temp 2

; Temperature sensor 2 name
TEMP_3_NAME = Temp 3

; Temperature sensor 2 name
TEMP_4_NAME = Temp 4

Relevant log output

2024-03-01 17:19:27.832606500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 120.0A | MAX BATTERY DISCHARGE CURRENT: 140.0A
2024-03-01 17:19:27.833246500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 70.0A | MAX BATTERY DISCHARGE CURRENT: 120.0A (read from BMS)
2024-03-01 17:19:27.833817500 INFO:SerialBattery:> CVCM:     True
2024-03-01 17:19:27.834425500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.7V | MAX CELL VOLTAGE: 3.51V
2024-03-01 17:19:27.835013500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2024-03-01 17:19:27.835593500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2024-03-01 17:19:27.836159500 INFO:SerialBattery:> CCCM SOC: True  | DCCM SOC: True
2024-03-01 17:19:27.836708500 INFO:SerialBattery:Serial Number/Unique Identifier: XavBMS-1
2024-03-01 17:19:27.890517500 INFO:SerialBattery:DeviceInstance = 2
2024-03-01 17:19:27.891365500 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0
2024-03-01 17:19:27.920202500 INFO:SerialBattery:publish config values = 1
2024-03-01 17:26:05.356117500 INFO:SerialBattery:Starting dbus-serialbattery
2024-03-01 17:26:05.357699500 INFO:SerialBattery:dbus-serialbattery v1.0.20230531
2024-03-01 17:26:05.358406500 INFO:SerialBattery:Testing Daly
2024-03-01 17:26:05.504347500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:05.505179500 INFO:SerialBattery:Testing Daly
2024-03-01 17:26:05.643281500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:05.644033500 INFO:SerialBattery:Testing Ecs
2024-03-01 17:26:05.724302500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:05.725013500 INFO:SerialBattery:Testing HeltecModbus
2024-03-01 17:26:09.518523500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:09.519222500 INFO:SerialBattery:Testing HLPdataBMS4S
2024-03-01 17:26:14.042285500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:14.043033500 INFO:SerialBattery:Testing Jkbms
2024-03-01 17:26:14.335221500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:14.339595500 INFO:SerialBattery:Testing Lifepower
2024-03-01 17:26:14.635100500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:14.639409500 INFO:SerialBattery:Testing LltJbd
2024-03-01 17:26:14.921952500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:14.925264500 INFO:SerialBattery:Testing Renogy
2024-03-01 17:26:15.232361500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:15.236226500 INFO:SerialBattery:Testing Renogy
2024-03-01 17:26:15.520099500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:15.524293500 INFO:SerialBattery:Testing Seplos
2024-03-01 17:26:16.550330500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:17.051892500 INFO:SerialBattery:Testing Daly
2024-03-01 17:26:17.197606500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:17.199050500 INFO:SerialBattery:Testing Daly
2024-03-01 17:26:17.340795500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:17.341732500 INFO:SerialBattery:Testing Ecs
2024-03-01 17:26:17.766451500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:17.767223500 INFO:SerialBattery:Testing HeltecModbus
2024-03-01 17:26:21.579438500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:21.581523500 INFO:SerialBattery:Testing HLPdataBMS4S
2024-03-01 17:26:26.106305500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:26:26.107049500 INFO:SerialBattery:Testing Jkbms
2024-03-01 17:26:26.249727500 INFO:SerialBattery:Connection established to Jkbms
2024-03-01 17:26:26.250450500 INFO:SerialBattery:Battery Jkbms connected to dbus from /dev/ttyUSB0
2024-03-01 17:26:26.251039500 INFO:SerialBattery:========== Settings ==========
2024-03-01 17:26:26.251712500 INFO:SerialBattery:> Connection voltage: 53.62V | Current: -0.0A | SoC: 82%
2024-03-01 17:26:26.252493500 INFO:SerialBattery:> Cell count: 16 | Cells populated: 0
2024-03-01 17:26:26.253134500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2024-03-01 17:26:26.253754500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 120.0A | MAX BATTERY DISCHARGE CURRENT: 140.0A
2024-03-01 17:26:26.254350500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 70.0A | MAX BATTERY DISCHARGE CURRENT: 120.0A (read from BMS)
2024-03-01 17:26:26.256135500 INFO:SerialBattery:> CVCM:     True
2024-03-01 17:26:26.257309500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.7V | MAX CELL VOLTAGE: 3.51V
2024-03-01 17:26:26.258141500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2024-03-01 17:26:26.258990500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2024-03-01 17:26:26.259806500 INFO:SerialBattery:> CCCM SOC: True  | DCCM SOC: True
2024-03-01 17:26:26.260414500 INFO:SerialBattery:Serial Number/Unique Identifier: XavBMS-1
2024-03-01 17:26:26.347565500 INFO:SerialBattery:DeviceInstance = 2
2024-03-01 17:26:26.349066500 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0
2024-03-01 17:26:26.380568500 INFO:SerialBattery:publish config values = 1
2024-03-01 17:32:16.631218500 INFO:SerialBattery:
2024-03-01 17:32:16.631843500 INFO:SerialBattery:Starting dbus-serialbattery
2024-03-01 17:32:16.633848500 INFO:SerialBattery:Venus OS v3.13
2024-03-01 17:32:16.634490500 INFO:SerialBattery:dbus-serialbattery v1.2.20240227beta
2024-03-01 17:32:32.648147500 INFO:SerialBattery:-- Testing BMS: 1 of 3 rounds
2024-03-01 17:32:32.648157500 INFO:SerialBattery:Testing Daly at address "\x40"
2024-03-01 17:32:32.806886500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:32:32.811363500 INFO:SerialBattery:Testing Daly at address "\x80"
2024-03-01 17:32:32.952351500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:32:32.953692500 INFO:SerialBattery:Testing Ecs
2024-03-01 17:32:33.034099500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:32:33.034824500 INFO:SerialBattery:Testing HeltecModbus
2024-03-01 17:32:36.833537500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:32:36.834293500 INFO:SerialBattery:Testing HLPdataBMS4S
2024-03-01 17:32:37.655299500 ERROR:SerialBattery:>>> ERROR: No reply - returning
2024-03-01 17:32:37.656285500 INFO:SerialBattery:Testing Jkbms
2024-03-01 17:32:37.802112500 INFO:SerialBattery:Connection established to Jkbms
2024-03-01 17:32:37.802852500 INFO:SerialBattery:Battery Jkbms connected to dbus from /dev/ttyUSB0
2024-03-01 17:32:37.803446500 INFO:SerialBattery:========== Settings ==========
2024-03-01 17:32:37.804110500 INFO:SerialBattery:> Connection voltage: 53.6V | Current: -0.0A | SoC: 82%
2024-03-01 17:32:37.804737500 INFO:SerialBattery:> Cell count: 16 | Cells populated: 0
2024-03-01 17:32:37.805384500 INFO:SerialBattery:> LINEAR LIMITATION ENABLE: True
2024-03-01 17:32:37.806022500 INFO:SerialBattery:> MIN CELL VOLTAGE: 2.7V | MAX CELL VOLTAGE: 3.51V
2024-03-01 17:32:37.806692500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 120.0A | MAX BATTERY DISCHARGE CURRENT: 140.0A
2024-03-01 17:32:37.807447500 INFO:SerialBattery:> MAX BATTERY CHARGE CURRENT: 70.0A | MAX BATTERY DISCHARGE CURRENT: 120.0A (read from BMS)
2024-03-01 17:32:37.808130500 INFO:SerialBattery:> CVCM:     True
2024-03-01 17:32:37.808818500 INFO:SerialBattery:> CCCM CV:  True  | DCCM CV:  True
2024-03-01 17:32:37.809548500 INFO:SerialBattery:> CCCM T:   True  | DCCM T:   True
2024-03-01 17:32:37.810187500 INFO:SerialBattery:> CCCM SOC: True  | DCCM SOC: True
2024-03-01 17:32:37.811203500 INFO:SerialBattery:Serial Number/Unique Identifier: XavBMS-1
2024-03-01 17:32:38.499508500 INFO:SerialBattery:Found existing battery with DeviceInstance = 1
2024-03-01 17:32:38.522090500 INFO:SerialBattery:Remove /Settings/Devices/serialbattery_ttyUSB0 from dbus. Old entry. Delete result: False
2024-03-01 17:32:38.899433500 INFO:SerialBattery:DeviceInstance = 1
2024-03-01 17:32:38.901790500 INFO:SerialBattery:PID file created successfully: /var/tmp/dbus-serialbattery_1.pid
2024-03-01 17:32:38.903703500 INFO:SerialBattery:Used DeviceInstances = ['1', '2']
2024-03-01 17:32:38.905192500 INFO:SerialBattery:com.victronenergy.battery.ttyUSB0
2024-03-01 17:32:38.961731500 INFO:SerialBattery:publish config values = False

Any other information that may be helpful

No response

tfboy commented 8 months ago

Sorry, forgot to say I'm fairly certain my cells are reaching 3.525V which is the SoC value, but it doesn't seem to do anything. Maybe I should lower this? Is the value her required for just one cell or do all cells need to exceed the SoC reset value for it to actually reset?

In looking at the history, today, one cell did reach 3.54V so why didn't it reset to 100% SoC ? image

mr-manuel commented 8 months ago

There are many issues with the same behaviour. JKBMS sets SOC to 95% when reaching OVPR and 100 % when one cell reaches OVP.

kommando828 commented 8 months ago

The JK firmware is suspect, here is a fudge fix from Youtube.

https://www.youtube.com/watch?v=maTqnSs_XAI

Title is Reset the old JK-BMS to 100% SOC when fully charged with no OVP. Here is how.

But it also covers the new version.

tfboy commented 8 months ago

Thank you both. I've not yet tweaked the settings within the JK bluetooth app, but it seems to have reset to 95% today. I'll keep an eye on it and apply the workaround Andy described if I have the problem again. :)

mr-manuel commented 8 months ago

@kommando828 this video is explaining that what I wrote :-)