This afternoon, I achieved a 100% State of Charge (SoC) for the first time since installing the protocol adapter, thanks to today's sunny weather. However, I'm noticing some strange behavior and am a bit concerned about the battery charging process.
Here's the sequence of messages I collected from Home Assistant in the sensor registry. It includes a mix of status changes, errors from the BMS, and CAN communication errors—quite a confusing situation
![Unsure :unsure: :unsure:](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
!
Code:
jk-bms-ble-can errors
15:54:21 - Tra 5 secondi
jk-bms-ble-can Charging Status cambiato in Bulk
15:53:52 - 24 secondi fa
jk-bms-ble-can Charging Status cambiato in Wait
15:53:50 - 1 minuto fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:51:49 - 3 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:51:38 - 3 minuti fa
jk-bms-ble-can Charging Status cambiato in Bulk
15:50:46 - 4 minuti fa
jk-bms-ble-can Charging Status cambiato in Wait
15:50:45 - 4 minuti fa
jk-bms-ble-can errors cambiato in Cell Overvoltage
15:48:48 - 6 minuti fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:48:44 - 6 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:48:28 - 7 minuti fa
jk-bms-ble-can errors
15:47:45 - 7 minuti fa
jk-bms-ble-can Charging Status cambiato in Bulk
15:47:41 - 7 minuti fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:45:49 - 9 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:45:39 - 9 minuti fa
jk-bms-ble-can Charging Status cambiato in Bulk
15:44:47 - 10 minuti fa
jk-bms-ble-can Charging Status cambiato in Wait
15:44:46 - 11 minuti fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:43:05 - 12 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:42:55 - 13 minuti fa
jk-bms-ble-can Charging Status cambiato in Bulk
15:42:13 - 13 minuti fa
jk-bms-ble-can Charging Status cambiato in Wait
15:42:12 - 13 minuti
jk-bms-ble-can errors cambiato in Cell Overvoltage
15:40:47 - 16 minuti fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:40:43 - 16 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:40:32 - 16 minuti fa
jk-bms-ble-can errors
15:40:05 - 17 minuti fa
jk-bms-ble-can Charging Status cambiato in Bulk
15:39:56 - 17 minuti fa
jk-bms-ble-can Charging Status cambiato in Wait
15:39:55 - 17 minuti fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:38:30 - 19 minuti fa
jk-bms-ble-can errors cambiato in Cell Overvoltage
15:38:30 - 19 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:38:15 - 19 minuti fa
jk-bms-ble-can Charging Status cambiato in Bulk
15:37:39 - 20 minuti fa
jk-bms-ble-can Charging Status cambiato in Wait
15:37:37 - 20 minuti fa
jk-bms-ble-can errors
15:37:37 - 20 minuti fa
jk-bms-ble-can errors cambiato in Cell Overvoltage
15:37:00 - 21 minuti fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:36:24 - 22 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:35:57 - 22 minuti fa
jk-bms-ble-can Charging Status cambiato in Bulk
15:35:27 - 23 minuti fa
jk-bms-ble-can Charging Status cambiato in Wait
15:35:26 - 23 minuti fa
jk-bms-ble-can Charging Status cambiato in Alarm
15:34:38 - 24 minuti fa
jk-bms-ble-can Charging Status cambiato in Absorption
15:33:40 - 25 minuti fa
Additionally, here's the overall battery voltage during the same period.
View attachment 192174
I've kept the default charging parameters in the YAML file.
Any ideas on what might be happening
![Confused :confused: :confused:](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
?
Davide