Open Schnullerbacke2 opened 3 months ago
After a reboot without successful reconnection, the log shows the following.
2024-07-03 21:54:49.437041500 2024-07-03 21:54:50.191633500 INFO:SerialBattery: 2024-07-03 21:54:50.192071500 INFO:SerialBattery:Starting dbus-serialbattery 2024-07-03 21:54:50.193135500 INFO:SerialBattery:Venus OS v3.33 2024-07-03 21:54:50.193590500 INFO:SerialBattery:dbus-serialbattery v1.2.20240401 2024-07-03 21:55:06.468249500 INFO:SerialBattery:Init of Jkbms_Ble at C8:47:8C:EC:BA:6F 2024-07-03 21:55:06.468532500 INFO:SerialBattery:Test of Jkbms_Ble at C8:47:8C:EC:BA:6F 2024-07-03 21:55:17.097821500 INFO:SerialBattery:--> asy_connect_and_scrape(): device not found: C8:47:8C:EC:BA:6F 2024-07-03 21:55:17.098157500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 21:55:17.185993500 ERROR:SerialBattery:No BMS found at C8:47:8C:EC:BA:6F 2024-07-03 21:55:17.186304500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble 2024-07-03 21:55:17.376305500 [CHG] Device C8:47:8C:EC:BA:6F RSSI: -57 2024-07-03 21:55:17.376572500 2024-07-03 21:55:17.376633500 INFO:Bluetooth details 2024-07-03 21:55:17.408004500 Attempting to disconnect from C8:47:8C:EC:BA:6F 2024-07-03 21:55:17.408009500 Successful disconnected 2024-07-03 21:55:22.449397500 Device C8:47:8C:EC:BA:6F (public) 2024-07-03 21:55:22.449402500 Alias: JK_B2A24S15P 2024-07-03 21:55:22.449404500 Paired: no 2024-07-03 21:55:22.449407500 Trusted: no 2024-07-03 21:55:22.449409500 Blocked: no 2024-07-03 21:55:22.449411500 Connected: no 2024-07-03 21:55:22.449413500 LegacyPairing: no 2024-07-03 21:55:22.449415500 UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) 2024-07-03 21:55:22.449419500 RSSI: -55 2024-07-03 21:55:22.451376500 2024-07-03 21:55:23.155704500 INFO:SerialBattery: 2024-07-03 21:55:23.155975500 INFO:SerialBattery:Starting dbus-serialbattery 2024-07-03 21:55:23.156872500 INFO:SerialBattery:Venus OS v3.33 2024-07-03 21:55:23.157143500 INFO:SerialBattery:dbus-serialbattery v1.2.20240401 2024-07-03 21:55:39.424715500 INFO:SerialBattery:Init of Jkbms_Ble at C8:47:8C:EC:BA:6F 2024-07-03 21:55:39.425001500 INFO:SerialBattery:Test of Jkbms_Ble at C8:47:8C:EC:BA:6F 2024-07-03 21:55:40.626482500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: BleakDBusError('org.bluez.Error.Failed', 'Software caused connection abort') of type <class 'bleak.exc.BleakDBusError'> in /opt/victronenergy/dbus-serialbattery/bms/jkbms_brn.py line #474 2024-07-03 21:55:40.627076500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 21:55:40.630664500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered 2024-07-03 21:55:40.746956500 [CHG] Device C8:47:8C:EC:BA:6F RSSI: -55 2024-07-03 21:55:40.746961500 [CHG] Device C8:47:8C:EC:BA:6F RSSI: -55 2024-07-03 21:55:40.746965500 [CHG] Device C8:47:8C:EC:BA:6F RSSI is nil 2024-07-03 21:55:42.722294500 Starting bluetooth: bluetoothd. 2024-07-03 21:55:42.744304500 INFO:SerialBattery:System Bluetooth daemon should have been restarted 2024-07-03 21:55:55.095326500 INFO:SerialBattery:--> asy_connect_and_scrape(): device not found: C8:47:8C:EC:BA:6F 2024-07-03 21:55:55.095638500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 21:55:55.153250500 ERROR:SerialBattery:No BMS found at C8:47:8C:EC:BA:6F 2024-07-03 21:55:55.153646500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble ...
Additional information - Jkbms: Hardware Ver.: V11.XW Software Ver.: V11.26
After several reboots a I was able to restore a connection. Periodical a reconnect-beep each roughly minute accorse.
Log:
2024-07-03 22:22:30.084866500 [CHG] Device C8:47:8C:EC:BA:6F RSSI: -77 2024-07-03 22:22:30.084874500 [CHG] Device C8:47:8C:EC:BA:6F RSSI: -78 2024-07-03 22:22:30.084879500 [CHG] Device C8:47:8C:EC:BA:6F RSSI is nil 2024-07-03 22:22:32.023222500 Starting bluetooth: bluetoothd. 2024-07-03 22:22:32.046447500 INFO:SerialBattery:System Bluetooth daemon should have been restarted 2024-07-03 22:23:42.869651500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 22:23:42.872635500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered 2024-07-03 22:23:44.969469500 Starting bluetooth: bluetoothd. 2024-07-03 22:23:44.991916500 INFO:SerialBattery:System Bluetooth daemon should have been restarted 2024-07-03 22:24:55.866244500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 22:24:55.868883500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered 2024-07-03 22:24:57.961846500 Starting bluetooth: bluetoothd. 2024-07-03 22:24:57.980363500 INFO:SerialBattery:System Bluetooth daemon should have been restarted 2024-07-03 22:26:02.896132500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 22:26:02.898873500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered 2024-07-03 22:26:04.992019500 Starting bluetooth: bluetoothd. 2024-07-03 22:26:05.010720500 INFO:SerialBattery:System Bluetooth daemon should have been restarted 2024-07-03 22:27:09.902714500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 22:27:09.904826500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered 2024-07-03 22:27:11.997207500 Starting bluetooth: bluetoothd. 2024-07-03 22:27:12.015723500 INFO:SerialBattery:System Bluetooth daemon should have been restarted 2024-07-03 22:28:16.897239500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 22:28:16.899233500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered 2024-07-03 22:28:18.990674500 Starting bluetooth: bluetoothd. 2024-07-03 22:28:19.009483500 INFO:SerialBattery:System Bluetooth daemon should have been restarted 2024-07-03 22:29:23.907271500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit 2024-07-03 22:29:23.909872500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered 2024-07-03 22:29:26.004568500 Starting bluetooth: bluetoothd. 2024-07-03 22:29:26.025009500 INFO:SerialBattery:System Bluetooth daemon should have been restarted
I have the same issue. I turned off the bluetooth in the Venus GX device (serial battery turns it on itself) so it worked better. However, it still hung from time to time. The solution for me so far is to switch off NodeRed. I don't understand why and how NodeRed has an influence, CPU load is good, temperature too and I only have a few nodes for displaying voltage and current or for day/night adjustment of the feed.
What kind of system do I have? Three battery blocks (16S 280Ah) each with a JKB2A20S20P, connected via Bluetooth, three Multiplus 3000 and three MPPT charge controllers.
With NodeRed switched off, it runs quite stable, regulates and limits the voltages perfectly to a maximum of 3.45V, then drops to 3.35V. So far so good. But what is still a problem are the many cell imbalance warnings, even though there is no load and a real maximum difference of 5mV.
Unfortunately my knowledge of Bluetooth connections is very limited and I'm not able to solve and troubleshoot this problem. Any help is very welcome!
I'm having a similar problem. First thing I tried to do is run the /etc/init.d/bluetooth restart script to restart bluetoothd, but this doesn't seem to work.
I just started having this problem. I used to lose connection every couple weeks, and a restart of the Cerbo would solve it. This morning, it has happened three times already. A restart solves it for a bit.
I am using Large OS. Updating now to 3.41 to see if that helps. Next step is to try a bluetooth dongle instead of built-in bluetooth.
I just started having this problem. I used to lose connection every couple weeks, and a restart of the Cerbo would solve it. This morning, it has happened three times already. A restart solves it for a bit.
I am using Large OS. Updating now to 3.41 to see if that helps. Next step is to try a bluetooth dongle instead of built-in bluetooth.
I also started having connection disrupts. I believe it was with updating to 3.41. I try to go back to 3.40. Could you find any solutions? I need to power cycle the cerbo gx every day. Sometimes if I can still reach it, it says no battery manager found. It was running more or less stable before. I also suspect some shelly dms or mqtt connection problem to have an influence as the problem increased since my home assistant instance with a mqtt broker stopped working because of an update.
I dont really know how to trouble shoot as i can barely reach the device.
I've got the same Problem, but I belive the BMS is the problem. What makes me think of that? Even rebooting or disconnect the Raspberry PI3b from the power source doesn't help. But if I press the button on the BMS for 5 seconds, the dbus serialbattery is able to connect automatically.
I'll check if there is a firmware update for the BMS.
This is the endless loop tring to reconnect:
2024-10-01 15:58:47.650939500 INFO:SerialBattery:
2024-10-01 15:58:47.651412500 INFO:SerialBattery:Starting dbus-serialbattery
2024-10-01 15:58:47.652900500 INFO:SerialBattery:Venus OS v3.42
2024-10-01 15:58:47.653332500 INFO:SerialBattery:dbus-serialbattery v1.4.20240928
2024-10-01 15:59:03.999950500 INFO:SerialBattery:Init of Jkbms_Ble at C8:47:80:03:B1:8D
2024-10-01 15:59:04.000444500 INFO:SerialBattery:Test of Jkbms_Ble at C8:47:80:03:B1:8D
2024-10-01 15:59:05.920678500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: BleakDBusError('org.bluez.Error.Failed', 'Software caused connection abort') of type <class 'bleak.exc.BleakDBusError'> in /opt/victronenergy/dbus-serialbattery/bms/jkbms_brn.py line #474
2024-10-01 15:59:05.921429500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2024-10-01 15:59:05.927431500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered
2024-10-01 15:59:06.019008500 [CHG] Device C8:47:80:03:B1:8D RSSI: -57
2024-10-01 15:59:06.019016500 [CHG] Device C8:47:80:03:B1:8D RSSI: -57
2024-10-01 15:59:06.019020500 [CHG] Device C8:47:80:03:B1:8D RSSI is nil
2024-10-01 15:59:08.037842500 Starting bluetooth: bluetoothd.
2024-10-01 15:59:08.071667500 INFO:SerialBattery:System Bluetooth daemon should have been restarted
2024-10-01 15:59:11.260295500 INFO:SerialBattery:--> asy_connect_and_scrape(): error while connecting to bt: BleakDBusError('org.bluez.Error.Failed', 'Software caused connection abort') of type <class 'bleak.exc.BleakDBusError'> in /opt/victronenergy/dbus-serialbattery/bms/jkbms_brn.py line #474
2024-10-01 15:59:11.260792500 INFO:SerialBattery:--> asy_connect_and_scrape(): Exit
2024-10-01 15:59:11.265866500 INFO:SerialBattery:Reset of system Bluetooth daemon triggered
2024-10-01 15:59:13.364495500 Starting bluetooth: bluetoothd.
2024-10-01 15:59:13.385058500 INFO:SerialBattery:System Bluetooth daemon should have been restarted
2024-10-01 15:59:13.513742500 ERROR:SerialBattery:No BMS found at C8:47:80:03:B1:8D
2024-10-01 15:59:13.516017500 ERROR:SerialBattery:ERROR >>> No battery connection at Jkbms_Ble
2024-10-01 15:59:15.811012500
2024-10-01 15:59:15.811211500
2024-10-01 15:59:15.811438500 INFO:Preparing Bluetooth for connection to BMS
2024-10-01 15:59:15.811625500 INFO:Bluetooth details
2024-10-01 15:59:15.849032500 Attempting to disconnect from C8:47:80:03:B1:8D
2024-10-01 15:59:15.849039500 Successful disconnected
2024-10-01 15:59:20.901560500 Device C8:47:80:03:B1:8D (public)
2024-10-01 15:59:20.901566500 Alias: A2H
2024-10-01 15:59:20.901567500 Paired: no
2024-10-01 15:59:20.901569500 Trusted: no
2024-10-01 15:59:20.901571500 Blocked: no
2024-10-01 15:59:20.901573500 Connected: no
2024-10-01 15:59:20.901574500 LegacyPairing: no
2024-10-01 15:59:20.901576500 UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
2024-10-01 15:59:20.901581500 RSSI: -57
2024-10-01 15:59:20.903545500
2024-10-01 15:59:23.989540500 INFO:SerialBattery:
2024-10-01 15:59:23.989979500 INFO:SerialBattery:Starting dbus-serialbattery
2024-10-01 15:59:23.991427500 INFO:SerialBattery:Venus OS v3.42
2024-10-01 15:59:23.991874500 INFO:SerialBattery:dbus-serialbattery v1.4.20240928
Describe the bug
I’m facing sporadic disconnect issues after a while (sometimes one hour, sometimes a day or a bit more). Venus OS doesn’t recognize the disconnect as values don’t get updated. After a while the messages in the log changes. I have spent hours searching through reported issue reports, but have not found any identical, unfixed or reported bugs.
How to reproduce
Issue is reproducible, but periodes vary. Sometimes the connection works for more than 24 hours, in other cases only for minutes or hours.
Expected behavior
Stable connection
Driver version
1.2.20240401
Venus OS device type
Raspberry Pi 4
Venus OS version
v3.33
BMS type
JKBMS / Heltec BMS
Cell count
18
Battery count
1
Connection type
Bluetooth
Config file
Relevant log output
Any other information that may be helpful
This behavior was already apparent immediately after initial operation. It is reproducible, but periodes vary. Sometimes the connection works for more than 24 hours, in other cases only for minutes or hours.