JKBMS BLE - Not connecting #819
Comments
|
Try to remove Please provide the logfiles as requested. Please do not use |
|
I have tried with and without the BMS_TYPE = Jkbms, I think they are @20CM apart. That is the log is just repeating itself. I have used the nightly one too, and is exactly the same error in the logs. I know that this bms use the protocol or framework jk02_32s (I hope I did remembered correctly). Using a esp32 and the code for esphome I can connect to the bms and receive the info. Venus os v3.10 Esp32 code is here : https://github.com/syssi/esphome-jk-bms/blob/main/esp32-ble-v11-example.yaml |
|
Can you try an older build like https://github.com/mr-manuel/venus-os_dbus-serialbattery/releases/tag/v1.0.20230525beta? |
|
Exactly the same: I have attached the device info from ESPhome: [07:44:59][D][button:010]: 'jk-bms retrieve device info' Pressed. Devices settings: [07:47:35][D][button:010]: 'jk-bms retrieve settings' Pressed. I have attached the logs from EspHome: INFO ESPHome 2023.8.3 |
|
Please provide the logs with timestamp, as we wrote everywhere. See also https://louisvdw.github.io/dbus-serialbattery/troubleshoot/#driver-log-files Anyway, now the error is another. @4000000065128866009ff72c ERROR:SerialBattery:No Bluetooth adapters found. |
|
I had a second USB Bluetooth connected, i had removed it, reinstalled, and still the same included the log. 2023-09-26 09:21:00.146421500 *** CCGX booted (0) ***
2023-09-26 09:22:45.740005500 Missing device address argument
2023-09-26 09:22:47.432327500 INFO:SerialBattery:
2023-09-26 09:22:47.432752500 INFO:SerialBattery:Starting dbus-serialbattery
2023-09-26 09:22:47.433665500 INFO:SerialBattery:dbus-serialbattery v1.0.20230525beta
2023-09-26 09:22:47.870858500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:22:47.871406500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:02.831165500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-09-26 09:23:02.831174500 connect and scrape on address: 20:22:08:25:17:41
2023-09-26 09:23:02.831177500 btloop
2023-09-26 09:23:02.831179500 reconnect
2023-09-26 09:23:02.831180500 Exiting bt-loop
2023-09-26 09:23:03.117505500 Missing device address argument
2023-09-26 09:23:04.764602500 INFO:SerialBattery:
2023-09-26 09:23:04.765033500 INFO:SerialBattery:Starting dbus-serialbattery
2023-09-26 09:23:04.765953500 INFO:SerialBattery:dbus-serialbattery v1.0.20230525beta
2023-09-26 09:23:05.154074500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:05.154536500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:20.776226500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-09-26 09:23:20.776382500 connect and scrape on address: 20:22:08:25:17:41
2023-09-26 09:23:20.776386500 btloop
2023-09-26 09:23:20.776387500 reconnect
2023-09-26 09:23:20.776389500 Exiting bt-loop
2023-09-26 09:23:21.039026500 Missing device address argument
2023-09-26 09:23:22.115334500 INFO:SerialBattery:
2023-09-26 09:23:22.115969500 INFO:SerialBattery:Starting dbus-serialbattery
2023-09-26 09:23:22.116990500 INFO:SerialBattery:dbus-serialbattery v1.0.20230525beta
2023-09-26 09:23:22.493285500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:22.493944500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:37.782339500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-09-26 09:23:37.782491500 connect and scrape on address: 20:22:08:25:17:41
2023-09-26 09:23:37.782495500 btloop
2023-09-26 09:23:37.782497500 reconnect
2023-09-26 09:23:37.782498500 Exiting bt-loop
2023-09-26 09:23:38.051658500 Missing device address argument
2023-09-26 09:23:39.202712500 INFO:SerialBattery:
2023-09-26 09:23:39.203141500 INFO:SerialBattery:Starting dbus-serialbattery
2023-09-26 09:23:39.204127500 INFO:SerialBattery:dbus-serialbattery v1.0.20230525beta
2023-09-26 09:23:39.605594500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:39.606058500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:54.778567500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-09-26 09:23:54.778798500 connect and scrape on address: 20:22:08:25:17:41
2023-09-26 09:23:54.778802500 btloop
2023-09-26 09:23:54.778803500 reconnect
2023-09-26 09:23:54.778805500 Exiting bt-loop
2023-09-26 09:23:55.044528500 Missing device address argument
2023-09-26 09:23:56.151729500 INFO:SerialBattery:
2023-09-26 09:23:56.152160500 INFO:SerialBattery:Starting dbus-serialbattery
2023-09-26 09:23:56.153071500 INFO:SerialBattery:dbus-serialbattery v1.0.20230525beta
2023-09-26 09:23:56.551272500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-09-26 09:23:56.551932500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
SVstats :
svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 7 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 10 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 10 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 11 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 12 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 12 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 12 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 13 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 13 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 14 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 14 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 14 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 15 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 15 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 16 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3052) 16 seconds
root@VFIEVOX3:~# svstat /service/dbus-blebattery.*
/service/dbus-blebattery.0: up (pid 3145) 0 seconds |
|
What is the output of bluetoothctl scan onWait for some seconds, then exit with |
|
Please tell me also the exact version of the driver you are using and Venus OS. Latest is not a useful answer. If you are not running driver version |
|
Hi, i have the same problem: tried with: nightly - dev from today Dmesg shows this: Also, the cerbo is a little laggy since installation of the driver - every few seconds, keys are delayed (top didnt show high load) on ssh and remote console. |
|
Hi, First of all: thanks for your fine work on this, it's much appreciated ! I have also same sort of a problem: **Jk BMS : Venus OS device type Venus OS version 3.12 Connection type Bluetoothctl info Config file /data/log/serial-starter/current /data/log/dbus-blebattery.*/current Any ideas on how to solve this problem ? |
|
From the logs I see that you are using the driver version A needed Python module named |
|
It doesn't seem to change things !? |
|
Try to run this manually: dbus-serialbattery/etc/dbus-serialbattery/reinstall-local.sh Lines 184 to 190 in a6d45e6 And then as last pip3 install dbus-fast |
|
Doesn't change much: |
|
You could try another pip3 install dbus-fast==v1.93.0There was a bug in dbus-fast some time ago. You can try different versions: https://github.com/Bluetooth-Devices/dbus-fast/releases |
|
Thanks for all the support, it does work now the first line was needed because otherwise ik kept hanging during making a wheel for dbus-fast. |
|
Hi, I have installed the latest nightly v1.0.20231102dev, i have the default pins : 1234 and 123456 :
|
|
Can you enable |
|
Done i change it for 100 lines |
|
I have bluetooth connection issue on my Jkbms (JK-B2A8S20P) and the Cerbo GX running this dbus serial battery driver too. The jkbms connects to Cerbo GX fine after a reboot, but will be disconnected after a while, in which case Cerbo GX doesn’t seem to know about the disconnection and still shows the BMS on the remote console (of course without displaying the correct up-to-date battery information), I know it because the bluetooth indicator on jkbms flashes when it is not connected to something. Any advice on how to go about troubleshooting this issue? Thanks! |
|
@itgenmar can you post a screenshot of the JKBMS displaying the hardware version? |
|
Attached the Image |
|
Sorry but the link is unavailable. Please insert the screenshot directly into GitHub. |
|
Also try the latest nightly from the dev branch. There were some relevant changes. |
|
|
|
Still no luck, here is the log: root@raspberrypi2:~# tail -F -n 100 /data/log/dbus-blebattery.*/current | tai64nlocal
2023-11-25 09:00:14.945526500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:00:16.929148500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:00:19.371688500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:00:24.461210500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:00:24.461673500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:00:24.751878500
2023-11-25 09:00:24.751992500 INFO:Bluetooth details
2023-11-25 09:00:24.753956500 [CHG] Device 20:22:08:25:17:41 RSSI: -62
2023-11-25 09:00:24.753964500 [CHG] Device 20:22:08:25:17:41 RSSI: -62
2023-11-25 09:00:24.753967500 [CHG] Device 20:22:08:25:17:41 RSSI: -41
2023-11-25 09:00:24.803023500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:00:24.803029500 Successful disconnected
2023-11-25 09:00:29.855923500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:00:29.855930500 Alias: JK_BD4A24S04
2023-11-25 09:00:29.855932500 Paired: no
2023-11-25 09:00:29.855934500 Trusted: no
2023-11-25 09:00:29.855936500 Blocked: no
2023-11-25 09:00:29.855937500 Connected: no
2023-11-25 09:00:29.855939500 LegacyPairing: no
2023-11-25 09:00:29.855941500 RSSI: -57
2023-11-25 09:00:29.856893500
2023-11-25 09:00:31.016673500 INFO:SerialBattery:
2023-11-25 09:00:31.017238500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:00:31.018425500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:00:31.496497500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:00:31.496963500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:00:34.203320500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:00:36.387988500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:00:41.013618500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:00:41.014089500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:00:41.292225500
2023-11-25 09:00:41.292334500 INFO:Bluetooth details
2023-11-25 09:00:41.294299500 [CHG] Device 20:22:08:25:17:41 RSSI: -57
2023-11-25 09:00:41.294308500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:00:41.338501500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:00:41.338508500 Successful disconnected
2023-11-25 09:00:46.390658500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:00:46.390664500 Alias: JK_BD4A24S04
2023-11-25 09:00:46.390667500 Paired: no
2023-11-25 09:00:46.390668500 Trusted: no
2023-11-25 09:00:46.390670500 Blocked: no
2023-11-25 09:00:46.390672500 Connected: no
2023-11-25 09:00:46.390674500 LegacyPairing: no
2023-11-25 09:00:46.390676500 RSSI: -63
2023-11-25 09:00:46.392663500
2023-11-25 09:00:47.466390500 INFO:SerialBattery:
2023-11-25 09:00:47.467218500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:00:47.468530500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:00:47.858728500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:00:47.859387500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:00:49.264848500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:00:51.403430500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:00:57.374379500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:00:57.374882500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:00:57.655496500
2023-11-25 09:00:57.655604500 INFO:Bluetooth details
2023-11-25 09:00:57.666579500 [CHG] Device 20:22:08:25:17:41 RSSI: -63
2023-11-25 09:00:57.666585500 [CHG] Device 20:22:08:25:17:41 RSSI: -57
2023-11-25 09:00:57.714824500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:00:57.714831500 Successful disconnected
2023-11-25 09:01:02.772857500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:01:02.772862500 Alias: JK_BD4A24S04
2023-11-25 09:01:02.772865500 Paired: no
2023-11-25 09:01:02.772866500 Trusted: no
2023-11-25 09:01:02.772868500 Blocked: no
2023-11-25 09:01:02.772870500 Connected: no
2023-11-25 09:01:02.772872500 LegacyPairing: no
2023-11-25 09:01:02.772874500 RSSI: -62
2023-11-25 09:01:02.775143500
2023-11-25 09:01:03.876882500 INFO:SerialBattery:
2023-11-25 09:01:03.877315500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:01:03.878258500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:01:04.248898500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:01:04.249332500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:01:07.191839500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:01:09.375123500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:01:13.766384500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:01:13.766517500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:01:14.040521500
2023-11-25 09:01:14.040629500 INFO:Bluetooth details
2023-11-25 09:01:14.041917500 [CHG] Device 20:22:08:25:17:41 RSSI: -62
2023-11-25 09:01:14.041926500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:01:14.086145500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:01:14.086152500 Successful disconnected
2023-11-25 09:01:19.142842500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:01:19.142848500 Alias: JK_BD4A24S04
2023-11-25 09:01:19.142850500 Paired: no
2023-11-25 09:01:19.142852500 Trusted: no
2023-11-25 09:01:19.142853500 Blocked: no
2023-11-25 09:01:19.142855500 Connected: no
2023-11-25 09:01:19.142857500 LegacyPairing: no
2023-11-25 09:01:19.142859500 RSSI: -57
2023-11-25 09:01:19.144669500
2023-11-25 09:01:20.272112500 INFO:SerialBattery:
2023-11-25 09:01:20.272847500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:01:20.273910500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:01:20.651157500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:01:20.651818500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:01:22.220554500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:01:37.986973500 *** CCGX booted (0) ***
2023-11-25 09:03:51.289590500
2023-11-25 09:03:51.289596500 INFO:Bluetooth details
2023-11-25 09:03:51.334060500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:03:51.334067500 Successful disconnected
2023-11-25 09:03:56.383225500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:03:56.383232500 Alias: JK_BD4A24S04
2023-11-25 09:03:56.383234500 Paired: no
2023-11-25 09:03:56.383236500 Trusted: no
2023-11-25 09:03:56.383238500 Blocked: no
2023-11-25 09:03:56.383239500 Connected: no
2023-11-25 09:03:56.383241500 LegacyPairing: no
2023-11-25 09:03:56.383243500 RSSI: -56
2023-11-25 09:03:56.384455500
2023-11-25 09:03:58.180752500 INFO:SerialBattery:
2023-11-25 09:03:58.181198500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:03:58.182121500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:03:58.644806500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:03:58.645291500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:04:03.638892500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecti ng to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:04:05.911487500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:04:08.163346500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:04:08.163817500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:04:08.437017500
2023-11-25 09:04:08.437150500 INFO:Bluetooth details
2023-11-25 09:04:08.440587500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:04:08.440595500 [CHG] Device 20:22:08:25:17:41 RSSI: -41
2023-11-25 09:04:08.440599500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:04:08.500211500 Device 20:22:08:25:17:41 not available
2023-11-25 09:04:13.556907500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:04:13.556914500 Alias: JK_BD4A24S04
2023-11-25 09:04:13.556916500 Paired: no
2023-11-25 09:04:13.556917500 Trusted: no
2023-11-25 09:04:13.556919500 Blocked: no
2023-11-25 09:04:13.556921500 Connected: no
2023-11-25 09:04:13.556923500 LegacyPairing: no
2023-11-25 09:04:13.556925500 RSSI: -63
2023-11-25 09:04:13.558490500
2023-11-25 09:04:14.641993500 INFO:SerialBattery:
2023-11-25 09:04:14.642638500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:04:14.643663500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:04:15.021677500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:04:15.022663500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:04:16.782571500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecti ng to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:04:18.876502500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:04:24.537235500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:04:24.537692500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:04:24.817920500
2023-11-25 09:04:24.817927500 INFO:Bluetooth details
2023-11-25 09:04:24.817931500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:04:24.868798500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:04:24.868806500 Successful disconnected
2023-11-25 09:04:29.927643500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:04:29.927650500 Alias: JK_BD4A24S04
2023-11-25 09:04:29.927652500 Paired: no
2023-11-25 09:04:29.927654500 Trusted: no
2023-11-25 09:04:29.927655500 Blocked: no
2023-11-25 09:04:29.927657500 Connected: no
2023-11-25 09:04:29.927659500 LegacyPairing: no
2023-11-25 09:04:29.927661500 RSSI: -56
2023-11-25 09:04:29.928550500
2023-11-25 09:04:31.021018500 INFO:SerialBattery:
2023-11-25 09:04:31.021520500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:04:31.022464500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:04:31.428751500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:04:31.429189500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:04:34.595878500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecti ng to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:04:36.868781500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:04:40.950662500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:04:40.950671500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:04:41.211800500
2023-11-25 09:04:41.211909500 INFO:Bluetooth details
2023-11-25 09:04:41.220100500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:04:41.220107500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:04:41.268636500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:04:41.268642500 Successful disconnected
2023-11-25 09:04:46.328927500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:04:46.328933500 Alias: JK_BD4A24S04
2023-11-25 09:04:46.328936500 Paired: no
2023-11-25 09:04:46.328937500 Trusted: no
2023-11-25 09:04:46.328939500 Blocked: no
2023-11-25 09:04:46.328941500 Connected: no
2023-11-25 09:04:46.328943500 LegacyPairing: no
2023-11-25 09:04:46.328945500 RSSI: -63
2023-11-25 09:04:46.330614500
2023-11-25 09:04:47.483698500 INFO:SerialBattery:
2023-11-25 09:04:47.484767500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:04:47.493340500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:04:47.885499500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:04:47.885952500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:04:49.715702500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:04:51.901230500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:04:57.401780500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:04:57.402310500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:04:57.680724500
2023-11-25 09:04:57.681007500 INFO:Bluetooth details
2023-11-25 09:04:57.687898500 [CHG] Device 20:22:08:25:17:41 RSSI: -63
2023-11-25 09:04:57.687905500 [CHG] Device 20:22:08:25:17:41 RSSI: -62
2023-11-25 09:04:57.729775500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:04:57.729782500 Successful disconnected
2023-11-25 09:05:02.798619500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:05:02.798625500 Alias: JK_BD4A24S04
2023-11-25 09:05:02.798627500 Paired: no
2023-11-25 09:05:02.798629500 Trusted: no
2023-11-25 09:05:02.798631500 Blocked: no
2023-11-25 09:05:02.798633500 Connected: no
2023-11-25 09:05:02.798635500 LegacyPairing: no
2023-11-25 09:05:02.798636500 RSSI: -56
2023-11-25 09:05:02.800541500
2023-11-25 09:05:03.892021500 INFO:SerialBattery:
2023-11-25 09:05:03.892463500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:05:03.893391500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:05:04.278802500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:04.279236500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:06.290387500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:05:08.904170500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:05:13.794480500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:05:13.794942500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:05:14.066718500
2023-11-25 09:05:14.066840500 INFO:Bluetooth details
2023-11-25 09:05:14.071734500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:05:14.071741500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:05:14.132645500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:05:14.132652500 [CHG] Device 20:22:08:25:17:41 RSSI is nil
2023-11-25 09:05:14.132655500 [CHG] Device A5:C2:37:01:AD:77 RSSI is nil
2023-11-25 09:05:14.132659500 [CHG] Controller B8:27:EB:2A:55:5A Discovering: no
2023-11-25 09:05:14.132663500 Successful disconnected
2023-11-25 09:05:19.193937500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:05:19.193943500 Alias: JK_BD4A24S04
2023-11-25 09:05:19.193946500 Paired: no
2023-11-25 09:05:19.193947500 Trusted: no
2023-11-25 09:05:19.193949500 Blocked: no
2023-11-25 09:05:19.193951500 Connected: no
2023-11-25 09:05:19.193953500 LegacyPairing: no
2023-11-25 09:05:19.193955500 RSSI: -56
2023-11-25 09:05:19.194856500
2023-11-25 09:05:20.371177500 INFO:SerialBattery:
2023-11-25 09:05:20.371901500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:05:20.372990500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:05:20.769732500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:20.770404500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:22.698993500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:05:24.887449500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:05:30.288156500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:05:30.288164500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:05:30.561097500
2023-11-25 09:05:30.561370500 INFO:Bluetooth details
2023-11-25 09:05:30.568488500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:05:30.568496500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:05:30.568500500 [CHG] Device 20:22:08:25:17:41 RSSI: -46
2023-11-25 09:05:30.612036500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:05:30.612043500 Successful disconnected
2023-11-25 09:05:35.668543500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:05:35.668549500 Alias: JK_BD4A24S04
2023-11-25 09:05:35.668552500 Paired: no
2023-11-25 09:05:35.668553500 Trusted: no
2023-11-25 09:05:35.668555500 Blocked: no
2023-11-25 09:05:35.668557500 Connected: no
2023-11-25 09:05:35.668559500 LegacyPairing: no
2023-11-25 09:05:35.668561500 RSSI: -56
2023-11-25 09:05:35.669434500
2023-11-25 09:05:36.755266500 INFO:SerialBattery:
2023-11-25 09:05:36.755677500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:05:36.756594500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:05:37.143068500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:37.143508500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:38.780787500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:05:40.867469500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2023-11-25 09:05:46.658627500 ERROR:SerialBattery:No BMS found at 20:22:08:25:17:41
2023-11-25 09:05:46.659102500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2023-11-25 09:05:46.929082500
2023-11-25 09:05:46.929185500 INFO:Bluetooth details
2023-11-25 09:05:46.934554500 [CHG] Device 20:22:08:25:17:41 RSSI: -56
2023-11-25 09:05:46.934562500 [CHG] Device 20:22:08:25:17:41 RSSI: -62
2023-11-25 09:05:46.982547500 Attempting to disconnect from 20:22:08:25:17:41
2023-11-25 09:05:46.982553500 Successful disconnected
2023-11-25 09:05:52.036303500 Device 20:22:08:25:17:41 (public)
2023-11-25 09:05:52.036309500 Alias: JK_BD4A24S04
2023-11-25 09:05:52.036311500 Paired: no
2023-11-25 09:05:52.036313500 Trusted: no
2023-11-25 09:05:52.036315500 Blocked: no
2023-11-25 09:05:52.036316500 Connected: no
2023-11-25 09:05:52.036318500 LegacyPairing: no
2023-11-25 09:05:52.036320500 RSSI: -62
2023-11-25 09:05:52.038296500
2023-11-25 09:05:53.115098500 INFO:SerialBattery:
2023-11-25 09:05:53.115528500 INFO:SerialBattery:Starting dbus-serialbattery
2023-11-25 09:05:53.116444500 INFO:SerialBattery:dbus-serialbattery v1.0.20231117dev
2023-11-25 09:05:53.499294500 INFO:SerialBattery:Init of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:53.499794500 INFO:SerialBattery:Test of Jkbms_Ble at 20:22:08:25:17:41
2023-11-25 09:05:54.816510500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: Characteristic with UUID 00002a24-0000-1000-8000-00805f9b34fb could not be found!
2023-11-25 09:05:57.868027500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit |
|
Hi it doesn't work : root@VFIEVOX3:~# bluetoothctl
Agent registered
[CHG] Controller B8:27:EB:2A:55:5A Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller B8:27:EB:2A:55:5A Discovering: yes
[CHG] Device 20:22:08:25:17:41 RSSI: -67
[NEW] Device A5:C2:37:01:AD:77 SP17S005P17S40A
[bluetooth]# scan off
Discovery stopped
[CHG] Device A5:C2:37:01:AD:77 RSSI is nil
[CHG] Device 20:22:08:25:17:41 RSSI is nil
[CHG] Controller B8:27:EB:2A:55:5A Discovering: no
[bluetooth]# connect 20:22:08:25:17:41
Attempting to connect to 20:22:08:25:17:41
[CHG] Device 20:22:08:25:17:41 Connected: yes
Connection successful
[CHG] Device 20:22:08:25:17:41 ServicesResolved: no
[CHG] Device 20:22:08:25:17:41 Connected: no
Failed to pair: org.bluez.Error.AuthenticationCanceled |
|
If you cannot connect that way, then you have another problem. Did you change the connection PIN of the BMS? |
|
I have 1234, 123456, and 0000
…On Sun 26 Nov 2023, 15:55 Manuel, ***@***.***> wrote:
If you cannot connect that way, then you have another problem. Did you
change the connection PIN of the BMS?
—
Reply to this email directly, view it on GitHub
<#819 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHP3VOXRBCOPBCTU3UCIFT3YGNQ7PAVCNFSM6AAAAAA5EL4LLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWHAZDAMBYGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hi all, Best regards
|
|
I think your issue is easy You need to install bleak opkg update |
Itgenmar, did you found a solution to your problem ? |
|
Not yet :( |
Seems we got the same proplem : #909 I've opened an issue on the Bleak project : hbldh/bleak#1493 My Jkbms is pretty old I just bought a BMV 712, at 130€ i will avoid many futur fail of the system, for what i can see .. the multi layer just for bluetooth BLuez / Bleak / DbusSerial ... is prone to fail easily on every new VenusOS/other dependencies update. |
I had the same kind of error then you had, turns out that for me the bluetooth communication ,is not "standard" enough to work with the Bleak API (it's not smart enough to me .. but it's an other problem). I've swapped my old JK for a newer one, and it work perfectly. |
Am I correct in thinking you are connecting to the JK to a ESP HOME device and to Venus OS at the same time? AFAIK, it can only connect to 1 device. If I power down the Venus and connect via my phone. It won't re-establish the Bluetooth connection when Venus is restarted. |
|
That's is incorrect.
there is an option to disable connection on the device (esp32)
…On Thu 18 Jan 2024, 11:34 Paul Phillips, ***@***.***> wrote:
Not yet :(
Am I correct in thinking you are connecting to the JK to a ESP HOME device
and to Venus OS at the same time?
AFAIK, it can only connect to 1 device. If I power down the Venus and
connect via my phone. It won't re-establish the Bluetooth connection when
Venus is restarted.
—
Reply to this email directly, view it on GitHub
<#819 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHP3VORLFNG3ALCEQM4WA2LYPECDTAVCNFSM6AAAAAA5EL4LLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGMYDSNJSGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Just tried again with the latest night v. |
|
options |
|
It looks like your BMS is connected to another device at the moment you restarted the driver. The JKBMS can only be connected to one device at a time. Please also add tripple |
|
To check if it is connected to an other device ?.. just start the Android app and see if you can connect to the BMS, if it is connected to an other device .. it will not show in the left list. |
|
@itgenmar please take a look at #900 (comment). Maybe this solves also this issue. |
|
Just tried it with the latest Nightly I just can't pair the device. I got another Bluetooth 5.0 still can't connect.. |
|
And sometimes I am getting this: |
|
Bluetoothctl Log |
|
What is the current state? Did you make sure, that only the dbus-serialbattery is connection to the JKBMS? From all the intel you gave it seems you are trying to connect two devices at thesame time with the JKBMS, which do not work by JKBMS design. |
|
HI Manuel, i made sure to disconnect all other devices, i have bought another raspberry pi and still doesn't work. here are the logs from dbus-serial battery version: v1.1.20240128dev with Venus OS version 3.14. and attached Bluethootlctl logs bluetoothctl both logs running in the same time |
|
Could you write me on Discord? |
|
Fixed with |
* fix Sinowealth not loading #702 * fix unique identifier function * enable BMS over config, if disabled by default Now you can also add more then one BMS for BMS_TYPE * show battery port in log * ANT BMS fixes Fixed that other devices are recognized as ANT BMS * Sinowealth BMS fixes Fixed that other devices are recognized as Sinowealth BMS * improved publish_battery error handling switched from error count to seconds * Improve Battery Voltage Handling in Linear Absorption Mode * Refactor change time() to int(time()) for consistency in max_voltage_start_time and tDiff calculation * Refactor battery voltage calculations for efficiency and clarity * Remove penalty_buffer * Reset max_voltage_start_time wenn we going to bulk(dynamic) mode * updated changelog * fix reply processing * Reduce the big inrush current, if the CVL jumps from Bulk/Absorbtion to Float fix #659 * Check returned data lenght for Seplos BMS Be stricter about the return data we accept, might fix the problem of grid meters accidently being recognized as a Seplos * Validate current, voltage, capacity and SoC for all BMS This prevents that a device, which is no BMS, is detected as BMS * removed double check * bump version * fix validation if None * updated changelog * proposal to #659 formatted :) * bugfix proposal to #659 * refactor setting float charge_mode * fix type error, removed bluetooth cronjob * updated changelog * fix rs485 write communication errors by inserting sleeps, add debug print for charge mode and fix crash on write soc failures * fix write problem on set_soc. also changed the switch charge/discharge function, just in case * debug msg * Bluetooth optimizations * Fixes by @peterohman #505 (comment) * fix #712 * fix meaningless time to go values * fix meaningless time to go values * Duration of transition to float depends on number of cells * Float transition - Voltage drop per second * Update hlpdatabms4s.py * Validate setting of FLOAT_CELL_VOLTAGE and avoid misconfiguration * consider utils.LINEAR_RECALCULATION_EVERY to refresh CVL * cleanup * consider utils.LINEAR_RECALCULATION_EVERY to refresh CVL * small refactor, introduced set_cvl_linear function to set CVL only once every LINEAR_RECALCULATION_EVERY seconds * fix typo * updated changelog * remove debug msg * remove debug msg * undo debug change * Daly BMS make auto reset soc configurable * added debug and error information for CVL * fix proposal for #733 (#735) * Added: Tollerance to enter float voltage once the timer is triggered * Add bulk voltage Load to bulk voltage every x days to reset the SoC to 100% for some BMS * JKBMS disable high voltage warning on bulk reenable after bulk was completed * fixed error * disable high voltage warning for all BMS when charging to bulk voltage * fix error and change default value measurementToleranceVariation from 0.025 to 0.5 else in OffGrid mode max voltage is always kept * Added temperature names to dbus/mqtt * Use current avg of last 300 cycles for TTG & TTS * Calculate only positive Time-to-SoC points * added current average of last 5 minutes * make CCL and DCL more clear * fix small error * bugfix: LLTJBD BMS SOC different in Xiaoxiang app and dbus-serialbattery * black formatting * JDB BMS - Control FETs for charge, discharge and disable / enable balancer (#761) * feature: Allow to control charge / discharge FET * feature: Allow to enable / disable balancer * bugfix: Cycle Capacity is in 10 mAh Fixes SoC with factor 100 * 100% percentage * JBD BMS show balancer state in GUI page IO (#763) * Bump version * Fix typos * Smaller fixes - fixes #792 (comment) * Removed comments from utils.py This should make more clear that there are no values to change * Updated changelog * possible fix for LLT/JBS connection problems #769 #777 * bugfix: LLT/JBD BMS general packet data size check * improved reinstall and disable script * LLT/JBD BMS - Improved error handling and automatical driver restart in case of error. Should fix: - #730 - #769 - #777 * Fixed Building wheel for dbus-fast won't finish on weak systems Fixes #785 * Support for Daly CAN Bus (#169) * support for Daly CAN Bus * fix constructor args * revert port, needs fix * add can filters * comment logger Some changes are still needed to work with the latest version. They will follow in a next PR. --------- Co-authored-by: Samuel Brucksch <samuel@iternio.com> Co-authored-by: Manuel <mr-manuel@outlook.it> * JKBMS BLE - Introduction of automatic SOC reset (HW Version 11) (#736) * Introduction of automatic SOC reset for JK BMS (HW Version 11) * Fixed value mapping * Rework of the code to make it simpler to use without additional configuration. Moved execution of SOC reset. It's now executed while changing from "Float" to "Float Transition". * Implementation of suggested changes Persist initial BMS OVP and OVPR settings Make use of max_cell_voltage to calculate trigger value for OVP alert * Added: Daly CAN and JKBMS CAN * added CAN bms to installation script optimized CAN drivers * smaller fixes * Trigger JK BLE SOC reset when using Step Mode * Moved trigger_soc_reset() * fixes LLT/JBD SOC > 100% #769 * changed VOLTAGE_DROP behaviour * Fix JKBMS not starting if BMS manuf. date is empty * corrected bulk, absorption and soc reset terms * fix typo * add JKBMS_BLE debugging data * fix small error * Some changes for lost bluetooth connection / hci_uart stack restart * added logging to config * add sleep before starting driver prevents lot of timeouts after reinstalling the driver, since the restart is now much faster than before * changed post install info * fix error * Daly BMS fixed embedded null byte #837 * added info for SoC reset to default config file * fix for #716 #716 * fix for #716 and JKBMS model recognition #716 * optimized logging * fix JKBMS recognition * added debugging * fixes #716 #716 * Bind device instance to unique_identifier #718 * added data types to battery class disabled unused variables * save current charge state #840 * correct file permissions * updated changelog * added periodic saveChargeDetails * fix some small errors * fix issue with ruuvi tags When there are hundreds of unused ruuvi tags in the settings list that where added because thei where nearby the driver does not start correctly. These stale entries are disabled on the driver startup. The issue was already filed to Victron developers * CVL with i-controller instead of penaltysum * cvl_controller: switch to choose PenaltySum or ICOntroller + documentation * docu enhancement * Add setting and install logic for usb bluetooth module * round temperatures * changed battery disconnect behaviour * Fixes #891 #891 * updated changelog * Add bluetooth device note to config.default.ini * Fix typo in bluetooth note in config.default.ini * fixed error in new cvl_controller * fixed float division by zero and code optimization * Restart MAX_VOLTAGE_TIME_SEC if cell diff > CELL_VOLTAGE_DIFF_KEEP_MAX_VOLTAGE_TIME_RESTART * Calculation of the SOC based on coloumb-counting (#868) * Calculation of the SOC in the driver based on coloumb-counting * soc_calc: add current correction before integration * soc_calc: correction map for current * Soc_calc: CorrectionMap, switch to turn on/off correction, selectable initial value * soc_calc: Bugfix * soc_calc: Bugfix * store soc in dbus for restart * store soc in dbus for restart (formatted) * store soc in dbus for restart (bugfix) * save soc_calc only after change > 1.0 * store soc in dbus for restart (bugfix) * logger does not work this way. do not know why * writing and reading to dbus works * Removed options: SOC_CALC_CURRENT_CORRECTION, SOC_CALC_RESET_VALUE_ON_RESTART, SOC_CALC_INIT_VALUE sort soc_calc alphabetically * fixed comments * Updated changelog, small fixes * Changed: PUBLISH_CONFIG_VALUES from 0/1 to True/False * Changed: Code optimizations - Changed some variables to be more clear - Added comments for easier code understanding * Calculated SOC: Added two decimals, added BMS SOC for MQTT & Node-RED * Updated changelog, small fixes * Changed: PUBLISH_CONFIG_VALUES from 0/1 to True/False * Changed: Code optimizations - Changed some variables to be more clear - Added comments for easier code understanding * Calculated SOC: Added two decimals, added BMS SOC for MQTT & Node-RED * Fix #898 #898 * Changed: Fix issue loading settings from dbus * Added nightly install option makes it easier for users to pretest fixes * Changed: more detailed error output when an exception happens * Possible fix for #912 #912 * Fixes #919 #919 * Changed: Exit script with error, if port excluded else the serialstarter stops at the dbus-serialbattery * Fixed some smaller errors * Updated pre-release workflow * Fix JK BMS connection restart when bluetooth fails. This fix installs a new thread to monitor the state of the original scraping thread. If scraping thread dies, it verifies that it did not because the scraping was intentionally stopped by calling stop_scrapping. When restarting the scrapper, it first calls the bluetooth reset lambda function that was passed in the class contructor, such that bluetooth is ready to make a proper connection. * Fixes #916 #916 * Added Venus OS version to logfile * Fix #840 #840 * Small code formatting fixes * Optimized reinstall script. Restart GUI only on changes. * Display debugging data in GUI when DEBUG enabled * Install script now shows repositories and version numbers * Update daly_can.py Fixing #950 for DalyBMS * Update jkbms_can.py Fixing #950 for Jk BMS * Fix black lint check * Fixes #970 #970 * Fixed some errors in restoring values from dbus settings * Moved sleep on start for all BMS * Update config description * Reworked a part of the default config * fix typo in stopping services when reinstalling * Fix Time-to-SoC and Time-to-Go calculation * Add changelog info * Round sum and diff voltage * Temperature limitation variables where changed * SoC limitation variables where changed * Added error messages * Remove unneeded code * Reset SoC to 0% if empty * Add GUIv2 for dbus-serialbattery * Check free space before installing * Added new GUIv2 version * Removed Python 2 compatibility * Changelog update * Code cleanup - Removed: get_temperatures() - Removed: update_last_seen() * Bluetooth code optimizations * Fixed some JKBMS BLE not starting #819 * Check if packages are already installed before install * Fixed some SOC calculation errors * Fixed None SOC on driver start * Do not show and allow button change when callback is missing for: - ForceChargingOff - ForceDischargingOff - TurnBalancingOff * Check if a device instance is already used by creating a PID file * Log and execute SOC reset to 100% or 0% only once * Update GitHub workflow and issue templates * Fixed LLT/JBD BMS with only on temperature sensor #791 #971 * Fix warning on reinstall * Fix missing IO control for JBDBMS #992 #992 * Prepare for removing dev branch --------- Co-authored-by: ogurevich <50322596+ogurevich@users.noreply.github.com> Co-authored-by: Bernd Stahlbock <6627385+transistorgit@users.noreply.github.com> Co-authored-by: wollew <wollew@users.noreply.github.com> Co-authored-by: Oleg Gurevich <oleg@gurevich.de> Co-authored-by: peterohman <psub@fieber.se> Co-authored-by: Strawder, Paul <paul@coach-ai.com> Co-authored-by: Paul Strawder <paulidstein@gmail.com> Co-authored-by: Samuel Brucksch <SamuelBrucksch@users.noreply.github.com> Co-authored-by: Samuel Brucksch <samuel@iternio.com> Co-authored-by: ArendsM <136503378+ArendsM@users.noreply.github.com> Co-authored-by: Meik Arends <github@arends.info> Co-authored-by: Marvo2011 <Marvin.Edeler@gmail.com> Co-authored-by: cflenker <christian.flenker@gmx.de> Co-authored-by: cflenker <125555670+cflenker@users.noreply.github.com> Co-authored-by: Cupertino Miranda <cupertinomiranda@gmail.com> Co-authored-by: Martin Polehla <p0l0us@users.noreply.github.com>
Describe the problem
**Jk BMS :
JK_bd4a24s4p
Serial number
Hardware v11.XW
SOFTWARE V11.25
POWER ON 13 TIMES
TOTL TIMES 1D14H30M0S
FIST ON DATE : 2023-04024
VERSION V4.15.7**
Getting the following error in the logs, no connection to venus os.
Driver version
v1.0.20230531
Venus OS device type
Raspberry Pi
Venus OS version
latest
BMS type
JKBMS / Heltec BMS
Cell count
7
Connection type
Bluetooth
Config file
Relevant log output
Any other information that may be helpful
No response
The text was updated successfully, but these errors were encountered: