SEPLOS BMS 10E (V2) not detected

[patman15]

I have two Mason SEPLOS Battery packs, each with SEPLOS BMS 10E (V2) and BT Modul.
The Mastepack (BP0) is connected by CAN bus to a Victron Multiplus GX and the two packs are interconnected by RS485
There is a design flaw with this SEPLOS BMS: When the CAN bus is in use, the desktop software can only monitor the slave battery pack(s), but not the master. :-(
So, I am using the iOS app to monitor both packs:
So, I am really excited about @patman15 's work to give access via home assistant:

I'd like to provide feedback information as well, but I am stuck at setting the system up.
• Installed a ESP32 BT Proxy via ESPhome, and add "active: true" in yaml
• I have downloaded the BLE Battery Management System (BMS) V1.13.0 in the HACS
• When I try to add this integration, there is the message: "Keine unterstützen Geräte via Bluetooth gefunden."
• The advertise monitor proofs that the ESP32 Proxy found the two BMS as BP00 and BP01 with RSSI of -79
• In terminal the command bluetoothctl devices >> No default controller available"
• manually connecting does not work neither

Did I forget a step or did something wrong?

Right click in the advertise monitor not the BP01 und BP00 entries produces: {"name":"BP01\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","address":"04:7F:0E:13:21:33","rssi":-79,"manufacturer_data":{},"service_data":{},"service_uuids":["0000ff00-0000-1000-8000-00805f9b34fb"],"source":"94:54:C5:E8:38:24","connectable":true,"time":1741291451.996939,"tx_power":null}

{"name":"BP00\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","address":"04:7F:0E:13:21:DB","rssi":-77,"manufacturer_data":{},"service_data":{},"service_uuids":["0000ff00-0000-1000-8000-00805f9b34fb"],"source":"94:54:C5:E8:38:24","connectable":true,"time":1741291452.2929354,"tx_power":null}

Originally posted by @maps0n in #171

[patman15]

Hi @maps0n, please do not mix issues, it makes it very difficult to follow different discussions then. You have a detection problem, the post was about the stacked battery system.

Regarding your issue: The problem is the name that seems to be wrongly transmitted by the BT proxy. It should be BP00 and BP01 without all the \u0000. Can you please post the raw advertisement message of the packs, using nRF connect?

Thanks,
Patrick

[maps0n]

Hello Patrick,
sorry for mixing and thank you for opening this case.

Attached are screenshots – I hope they comprise the information you need for the investigation.
Please advise, if something is missing – I am not familiar with Bluetooth nor the nRF connect app.
I added the ESPhome yaml of my ESP proxy.

TIA for looking into it.
BR Herb

BP01.txt

[patman15]

It's an issue with the proxy. You can either try to recompile the proxy using a current version of ESPHome (if not done already) or use a BT dongle?
Could you please also go to the bluetooth integration. On your BT adapter select configure->advertisement monitor, click the device in question and provide the information via copy to clipboard.

[maps0n]

• As far as I can see, my ESPhome is current.
• Is the yaml file I posted correct?
• I reinstall the proxy – attached is the install log. Is there anything strange?
Attempt to integrate BLE Battery Management still error:
"Keine unterstützen Geräte via Bluetooth gefunden."

Currently no BT Dongle available- I am going to order one.

Thanx

Advertise Data of BP00 an bt proxy:
{"name":"BP00\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","address":"04:7F:0E:13:21:DB","rssi":-73,"manufacturer_data":{},"service_data":{},"service_uuids":["0000ff00-0000-1000-8000-00805f9b34fb"],"source":"94:54:C5:E8:38:24","connectable":true,"time":1741614687.6760793,"tx_power":null}

Advertise Data of BP01 an bt proxy:
{"name":"BP01\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","address":"04:7F:0E:13:21:33","rssi":-74,"manufacturer_data":{},"service_data":{},"service_uuids":["0000ff00-0000-1000-8000-00805f9b34fb"],"source":"94:54:C5:E8:38:24","connectable":true,"time":1741614687.3680832,"tx_power":null}

[patman15]

Is the yaml file I posted correct?

I can't see an issue with it.

Attempt to integrate BLE Battery Management still error:
"Keine unterstützen Geräte via Bluetooth gefunden."

The reason is still the wrongly communicated name by the proxy: BP01\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
it shall be BP01.

Currently no BT Dongle available- I am going to order one.
👍

You can modify the following two lines

BMS_BLE-HA/custom_components/bms_ble/manifest.json

Line 137 in 867f614

"local_name": "BP0?",

BMS_BLE-HA/custom_components/bms_ble/plugins/seplos_v2_bms.py

Line 71 in 867f614

"local_name": "BP0?",

to BP0* then it will work also on your system. Note: any update will overwrite your changes!

[maps0n]

Hi Patrick,
Your suggestions to replace BP0? to BP0* did the trick and the integration is up.
So, I am starting to looking around.

Tomorrow the BT dongles will arrive and I will keep one as backup, when the files are overwritten.

Pending is what is wrong with my exp32 bluetooth proxy.

Thank you very much for the integration you created and especially for your support on this issue here.

BR herb

P.S.
I changed in the yaml file the framework to type: esp-idf – was recommend by others - of course did address the the name issue.

[patman15]

Hi! Just to confirm (and probably document in FAQ) you changed the framework from Arduino to esp-idf and that solves the name issue with the \u0000, correct?

[maps0n]

Sorry, I wanted to write: ... "of course did not address the the name issue."

One Question:
I experience that the entities data disappears randomly and comes back.
Where should I report about this?

[patman15]

Sorry, I wanted to write: ... "of course did not address the the name issue."

😞

I experience that the entities data disappears randomly and comes back.
Where should I report about this?

First see the known issues. If you do not think it is covered by this, or you want me to check, just raise a new issue and provide me a debug log of a period of time where data is available and not available.