How can we know the type of BMS

[gris74]

Hi,

I have an ULTIMATRON battery 12v100Ah with integrated bluetooth BMS but unknown type.
I try each type in you plugin without success.
How can we check the type of Bluetooth BMS without destroying the battery cover

Great job

[gris74]

This is the log of the espHome bluetooth proxy next to the battery 70:3E:97:07:F1:AF

[11:38:17][VV][esp32_ble_tracker:575]: Parse Result:
[11:38:17][VV][esp32_ble_tracker:592]:   Address: 70:3E:97:07:F1:AF (PUBLIC)
[11:38:17][VV][esp32_ble_tracker:594]:   RSSI: -53
[11:38:17][VV][esp32_ble_tracker:595]:   Name: '12100A220600347'
[11:38:17][VV][esp32_ble_tracker:603]:   Ad Flag: 6
[11:38:17][VV][esp32_ble_tracker:609]:   Manufacturer data: 97.07.F1.AF
[11:38:17][VV][api.service:334]: send_bluetooth_le_advertisement_response: BluetoothLEAdvertisementResponse {
  address: 123414124163503
  name: '12100A220600347'
  rssi: -53
  service_uuids: '0xFF00'
  manufacturer_data: BluetoothServiceData {
  uuid: '0x3E70'
  data: '\x97�\xf1\xaf'
}

Log Batmon

INFO     [sampling.py:38] connecting bms JbdBt(**70:3E:97:07:F1:AF**)
DEBUG    [client.py:181] Connecting to device @ 70:3E:97:07:F1:AF with hci0
ERROR    [sampling.py:90] battery347 error: [org.freedesktop.DBus.Error.NameHasNoOwner] Could not activate remote peer: unit failed.
ERROR    [main.py:205] 1 exceptions occurred fetching BMSs
ERROR    [main.py:83] Error (num 41) reading BMS: [org.freedesktop.DBus.Error.NameHasNoOwner] Could not activate remote peer: unit failed.
ERROR    [main.py:84] Stack: Traceback (most recent call last):
  File "/app/main.py", line 79, in fetch_loop
    await fn()
  File "/app/main.py", line 206, in fn
    raise exceptions[0]
  File "/app/main.py", line 201, in fn
    await t
  File "/app/bmslib/sampling.py", line 29, in __call__
    return await self.sample()
  File "/app/bmslib/sampling.py", line 42, in sample
    async with bms:
  File "/app/bmslib/bt.py", line 80, in __aenter__
    await self.connect()
  File "/app/bmslib/jbd.py", line 45, in connect
    await super().connect(**kwargs)
  File "/app/bmslib/bt.py", line 22, in connect
    await self.client.connect(timeout=timeout)
  File "/usr/lib/python3.10/site-packages/bleak/backends/bluezdbus/client.py", line 190, in connect
    device = await BleakScannerBlueZDBus.find_device_by_address(
  File "/usr/lib/python3.10/site-packages/bleak/backends/scanner.py", line 205, in find_device_by_address
    return await cls.find_device_by_filter(
  File "/usr/lib/python3.10/site-packages/bleak/backends/scanner.py", line 234, in find_device_by_filter
    async with cls(detection_callback=apply_filter, **kwargs):
  File "/usr/lib/python3.10/site-packages/bleak/backends/scanner.py", line 79, in __aenter__
    await self.start()
  File "/usr/lib/python3.10/site-packages/bleak/backends/bluezdbus/scanner.py", line 123, in start
    assert_reply(reply)
  File "/usr/lib/python3.10/site-packages/bleak/backends/bluezdbus/utils.py", line 23, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)
bleak.exc.BleakDBusError: [org.freedesktop.DBus.Error.NameHasNoOwner] Could not activate remote peer: unit failed.
WARNING  [main.py:86] too many errors, abort
INFO     [main.py:213] Shutting down ...
INFO     [main.py:218] Disconnecting JbdBt(70:3E:97:07:F1:AF)
INFO     [main.py:227] exit signal handler...
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[fl4p]

You can use https://github.com/fl4p/batmon-ha/blob/master/tools/service_explorer.py to inspect the BLE characteristics. Each BMS model has its own UUID signature.

[clerosch]

Hello, do you got a result for ultimatron bms? Im also looking for a solution with ultimatron batteries. Iv also tested all types without success, service_explorer didnt brought a solution - see attachement - i cant understand the feedback.