Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No supported devices found via Bluetooth. #94

Open
3 tasks done
jeremyjoslin opened this issue Nov 19, 2024 · 17 comments
Open
3 tasks done

No supported devices found via Bluetooth. #94

jeremyjoslin opened this issue Nov 19, 2024 · 17 comments
Labels
question Further information is requested

Comments

@jeremyjoslin
Copy link

Checklist

  • I need support with using the integration.
  • My issue is not a feature request
  • I'm not avoiding to fill out the bug report form.

Describe the issue

Installed add-on in HACS and when selecting the integration to add, I get this error immediately. No scanning can happen instantly so I assume this thinks I have no BLE devices which is not correct.

I have an rPi with BT scanning and several Shelly devices in active or passive mode. Other BTE integrations are using my bluetooth sensors fine.

I am trying to connect to my golf cart battery so I know when it needs to be charged. No luck so far on my second add-on to achieve this. Any assistance is appreciated.

@jeremyjoslin jeremyjoslin added the question Further information is requested label Nov 19, 2024
@patman15
Copy link
Owner

Hi! The integration checks the devices discovered by Home Assistant for compatibility. If it brings the error message this means it does not recognise the battery type.
Which BMS is used in your golf cart and are you sure it's in range?

@jeremyjoslin
Copy link
Author

Thanks for asking. Yes, the BMS is definitely in range of the Shelly which is working as a proxy. I can see the golf cart BMS with another popular add-on that shows log files and I can see the MAC and name easily.

The battery is an Ogrphy from Amazon (popular Chinese brand). Unsure what BMS it uses or how I can figure that out.

@patman15
Copy link
Owner

Hi Jeremy, does the another popular add-on work with the battery? If so, as far as I know you need to configure the BMS type, which one did you set and did you deactivate it before trying this integration?
If it does not work, please follow the steps below:

  • Open a terminal to Home Assistant.
  • Use the command bluetoothctl devices to check that your devices is detected and
  • run bluetoothctl info <MAC_of_BMS> and paste the output here, so I probably can have an idea which type of BMS is used.

Best regards, Patrick

@jeremyjoslin
Copy link
Author

Thanks for the direction. This is good.

  • regarding the other add-on, I can see the MAC of the BMS in the logs but I cannot connect to it. I tried each of the different types (jk, sok, etc) to no avail.
  • I wasn't aware of these terminal commands which are very insightful. Using bluetoothctl devices I do not see the MAC of my BMS though. It appears that this command is only showing BLE devices visible to the HA device itself and not the proxies.
  • Interestingly, I am also trying the Bermuda add-on for triangulation, and this one finds the beacon of the BMS and gives me a pretty good location for it - no connection, just passive.
  • I wonder if my problem may be with the Shelly BLE proxy and how I have it set up. I toggle between and active ad passive modes as part of my troubleshooting. Bermuda finds it with passive.

I'll continue to troubleshoot on this end... based on results of bluetoothctl it doesn't look like the issue is with your add-on.

@patman15
Copy link
Owner

It appears that this command is only showing BLE devices visible to the HA device itself
You can use bluetoothctl and then

list                                              List available controllers
show [ctrl]                                       Controller information
select <ctrl>                                     Select default controller

see the help.

I wonder if my problem may be with the Shelly BLE proxy

I guess you have seen that a maximum of 3 devices can be covered by a Bluetooth proxy for active connections and you need to have active connections enabled!

based on results of bluetoothctl it doesn't look like the issue is with your add-on.

Well, not yet, but since it is unclear which BMS is used by the battery, it could still happen that the integration is not compatible with it. Let me know if you come to that point!

@andreas-bulling
Copy link

I think I have the same problem. Upon installing the add-on it directly detected the two BMS (Seplos v3) but these cannot be configured - I assume because I haven't paired with these yet.

However, bluetoothctl devices doesn't show them.

The HomeAssistant box with the bluetooth dongle is not in the same room as the BMS so it seems Bluetooth Proxy is not working with bluetoothctl?

@patman15
Copy link
Owner

I think I have the same problem.

Can I assume that the BMS type detected is correct? If so, have you checked that you enabled active connections on the Bluetooth Proxy?

@andreas-bulling
Copy link

This I need to check. Which ESPHome device do I need to activate the "active" mode on -the one closest do the BMS?

@patman15
Copy link
Owner

There is dynamic allocation between different proxies based on signal strength as far as I understood. So in theory, the closest should be ok.

@andreas-bulling
Copy link

I just checked - "active" was/is set. Still, no devices can be found. :/

@patman15
Copy link
Owner

Upon installing the add-on it directly detected the two BMS (Seplos v3) but these cannot be configured

Can you elaborate on what you mean by "cannot be configured"? Any logs or error message you can share?

@andreas-bulling
Copy link

andreas-bulling commented Nov 28, 2024

Sorry - this is all I can see

image

I couldn't find anything in the logs for HA core. BP00 and BP01 were automatically added after installing the integration for the first time. I have two Seplos BMS.

@patman15
Copy link
Owner

Please enable debug logging (on the left) wait ~3 minutes and provide me the log so that I can check what's the issue.

@andreas-bulling
Copy link

2024-11-28 19:16:56.994 DEBUG (MainThread) [custom_components.bms_ble] BP01: device communication timed out
2024-11-28 19:16:56.995 DEBUG (MainThread) [custom_components.bms_ble] BP01: shuting down BMS device
2024-11-28 19:16:56.995 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP01)
2024-11-28 19:16:57.089 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP01)
2024-11-28 19:17:02.507 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JCE7SHKBH432H57EW9VPGZJT version=1 domain=bms_ble title=BP00 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=60:6E:41:0F:3D:E6>
2024-11-28 19:17:02.507 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP00 (60:6E:41:0F:3D:E6) as Jiabaida Smart BMS
2024-11-28 19:17:02.507 DEBUG (MainThread) [custom_components.bms_ble] device data: {'name': 'BP00', 'address': '60:6E:41:0F:3D:E6', 'rssi': -76, 'manufacturer_data': {}, 'service_data': {}, 'service_uuids': ['0000ff00-0000-1000-8000-00805f9b34fb'], 'source': 'EC:62:60:91:56:F0', 'advertisement': AdvertisementData(local_name='BP00', service_uuids=['0000ff00-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-76), 'device': BLEDevice(60:6E:41:0F:3D:E6, BP00), 'connectable': True, 'time': 2360648.255006528, 'tx_power': None}
2024-11-28 19:17:02.507 DEBUG (MainThread) [custom_components.bms_ble] BP00: BMS data update
2024-11-28 19:17:02.508 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Connecting BMS (BP00)
2024-11-28 19:17:02.508 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connection attempt: 1
2024-11-28 19:17:02.934 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connected after 1 attempts
2024-11-28 19:17:13.848 DEBUG (MainThread) [custom_components.bms_ble] BP00: device communication timed out
2024-11-28 19:17:13.848 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching BP00 data in 11.340 seconds (success: False)
2024-11-28 19:17:13.848 DEBUG (MainThread) [custom_components.bms_ble] BP00: shuting down BMS device
2024-11-28 19:17:13.848 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP00)
2024-11-28 19:17:13.909 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP00)
2024-11-28 19:17:19.343 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JCE7SHKBH432H57EW9VPGZJT version=1 domain=bms_ble title=BP00 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=60:6E:41:0F:3D:E6>
2024-11-28 19:17:19.343 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP00 (60:6E:41:0F:3D:E6) as Jiabaida Smart BMS
2024-11-28 19:17:19.343 DEBUG (MainThread) [custom_components.bms_ble] device data: {'name': 'BP00', 'address': '60:6E:41:0F:3D:E6', 'rssi': -76, 'manufacturer_data': {}, 'service_data': {}, 'service_uuids': ['0000ff00-0000-1000-8000-00805f9b34fb'], 'source': 'EC:62:60:91:56:F0', 'advertisement': AdvertisementData(local_name='BP00', service_uuids=['0000ff00-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-76), 'device': BLEDevice(60:6E:41:0F:3D:E6, BP00), 'connectable': True, 'time': 2360665.063156786, 'tx_power': None}
2024-11-28 19:17:19.344 DEBUG (MainThread) [custom_components.bms_ble] BP00: BMS data update
2024-11-28 19:17:19.344 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Connecting BMS (BP00)
2024-11-28 19:17:19.344 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connection attempt: 1
2024-11-28 19:17:19.809 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connected after 1 attempts
2024-11-28 19:17:30.321 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JCE7T5PRX4BJ1EKXK7G3VQ44 version=1 domain=bms_ble title=BP01 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=60:6E:41:0F:3C:24>
2024-11-28 19:17:30.321 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP01 (60:6E:41:0F:3C:24) as Jiabaida Smart BMS
2024-11-28 19:17:30.321 DEBUG (MainThread) [custom_components.bms_ble] device data: {'name': 'BP01', 'address': '60:6E:41:0F:3C:24', 'rssi': -84, 'manufacturer_data': {}, 'service_data': {}, 'service_uuids': ['0000ff00-0000-1000-8000-00805f9b34fb'], 'source': 'EC:62:60:91:56:F0', 'advertisement': AdvertisementData(local_name='BP01', service_uuids=['0000ff00-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-84), 'device': BLEDevice(60:6E:41:0F:3C:24, BP01), 'connectable': True, 'time': 2360675.890253576, 'tx_power': None}
2024-11-28 19:17:30.321 DEBUG (MainThread) [custom_components.bms_ble] BP01: BMS data update
2024-11-28 19:17:30.321 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Connecting BMS (BP01)
2024-11-28 19:17:30.321 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3C:24 - 60:6E:41:0F:3C:24: Connection attempt: 1
2024-11-28 19:17:30.835 DEBUG (MainThread) [custom_components.bms_ble] BP00: device communication timed out
2024-11-28 19:17:30.835 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching BP00 data in 11.491 seconds (success: False)
2024-11-28 19:17:30.835 DEBUG (MainThread) [custom_components.bms_ble] BP00: shuting down BMS device
2024-11-28 19:17:30.835 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP00)
2024-11-28 19:17:30.971 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP00)
2024-11-28 19:17:30.987 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3C:24 - 60:6E:41:0F:3C:24: Connected after 1 attempts
2024-11-28 19:17:35.416 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JCE7SHKBH432H57EW9VPGZJT version=1 domain=bms_ble title=BP00 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=60:6E:41:0F:3D:E6>
2024-11-28 19:17:35.416 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP00 (60:6E:41:0F:3D:E6) as Jiabaida Smart BMS
2024-11-28 19:17:35.416 DEBUG (MainThread) [custom_components.bms_ble] device data: {'name': 'BP00', 'address': '60:6E:41:0F:3D:E6', 'rssi': -77, 'manufacturer_data': {}, 'service_data': {}, 'service_uuids': ['0000ff00-0000-1000-8000-00805f9b34fb'], 'source': 'EC:62:60:91:56:F0', 'advertisement': AdvertisementData(local_name='BP00', service_uuids=['0000ff00-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-77), 'device': BLEDevice(60:6E:41:0F:3D:E6, BP00), 'connectable': True, 'time': 2360681.007299321, 'tx_power': None}
2024-11-28 19:17:35.416 DEBUG (MainThread) [custom_components.bms_ble] BP00: BMS data update
2024-11-28 19:17:35.416 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Connecting BMS (BP00)
2024-11-28 19:17:35.416 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connection attempt: 1
2024-11-28 19:17:35.979 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connected after 1 attempts
2024-11-28 19:17:38.615 WARNING (MainThread) [aioesphomeapi.connection] presence-bathroom-ff @ 192.168.1.142: Connection error occurred: presence-bathroom-ff @ 192.168.1.142: EOF received
2024-11-28 19:17:39.114 WARNING (MainThread) [aioesphomeapi.connection] presence-bathroom-ff @ 192.168.1.142: Connection error occurred: presence-bathroom-ff @ 192.168.1.142: EOF received
2024-11-28 19:17:42.078 DEBUG (MainThread) [custom_components.bms_ble] BP01: device communication timed out
2024-11-28 19:17:42.078 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching BP01 data in 11.757 seconds (success: False)
2024-11-28 19:17:42.079 DEBUG (MainThread) [custom_components.bms_ble] BP01: shuting down BMS device
2024-11-28 19:17:42.079 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP01)
2024-11-28 19:17:42.221 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP01)
2024-11-28 19:17:46.633 DEBUG (MainThread) [custom_components.bms_ble] BP00: device communication timed out
2024-11-28 19:17:46.633 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching BP00 data in 11.217 seconds (success: False)
2024-11-28 19:17:46.634 DEBUG (MainThread) [custom_components.bms_ble] BP00: shuting down BMS device
2024-11-28 19:17:46.634 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP00)
2024-11-28 19:17:46.761 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP00)
2024-11-28 19:17:46.764 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JCE7SHKBH432H57EW9VPGZJT version=1 domain=bms_ble title=BP00 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=60:6E:41:0F:3D:E6>
2024-11-28 19:17:46.764 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP00 (60:6E:41:0F:3D:E6) as Jiabaida Smart BMS
2024-11-28 19:17:46.764 DEBUG (MainThread) [custom_components.bms_ble] device data: {'name': 'BP00', 'address': '60:6E:41:0F:3D:E6', 'rssi': -80, 'manufacturer_data': {}, 'service_data': {}, 'service_uuids': ['0000ff00-0000-1000-8000-00805f9b34fb'], 'source': 'EC:62:60:8B:EB:F4', 'advertisement': AdvertisementData(local_name='BP00', service_uuids=['0000ff00-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-80), 'device': BLEDevice(60:6E:41:0F:3D:E6, BP00), 'connectable': True, 'time': 2360681.51730388, 'tx_power': None}
2024-11-28 19:17:46.764 DEBUG (MainThread) [custom_components.bms_ble] BP00: BMS data update
2024-11-28 19:17:46.764 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Connecting BMS (BP00)
2024-11-28 19:17:46.765 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connection attempt: 1
2024-11-28 19:17:47.234 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connected after 1 attempts
2024-11-28 19:17:54.214 WARNING (SyncWorker_24) [py.warnings] /usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py:1064: InsecureRequestWarning: Unverified HTTPS request is being made to host 'luke.local'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
  warnings.warn(

2024-11-28 19:17:58.054 DEBUG (MainThread) [custom_components.bms_ble] BP00: device communication timed out
2024-11-28 19:17:58.055 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching BP00 data in 11.290 seconds (success: False)
2024-11-28 19:17:58.055 DEBUG (MainThread) [custom_components.bms_ble] BP00: shuting down BMS device
2024-11-28 19:17:58.056 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP00)
2024-11-28 19:17:58.183 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP00)
2024-11-28 19:18:07.069 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JCE7SHKBH432H57EW9VPGZJT version=1 domain=bms_ble title=BP00 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=60:6E:41:0F:3D:E6>
2024-11-28 19:18:07.070 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP00 (60:6E:41:0F:3D:E6) as Jiabaida Smart BMS
2024-11-28 19:18:07.070 DEBUG (MainThread) [custom_components.bms_ble] device data: {'name': 'BP00', 'address': '60:6E:41:0F:3D:E6', 'rssi': -75, 'manufacturer_data': {}, 'service_data': {}, 'service_uuids': ['0000ff00-0000-1000-8000-00805f9b34fb'], 'source': 'EC:62:60:91:56:F0', 'advertisement': AdvertisementData(local_name='BP00', service_uuids=['0000ff00-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-75), 'device': BLEDevice(60:6E:41:0F:3D:E6, BP00), 'connectable': True, 'time': 2360712.837583873, 'tx_power': None}
2024-11-28 19:18:07.070 DEBUG (MainThread) [custom_components.bms_ble] BP00: BMS data update
2024-11-28 19:18:07.070 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Connecting BMS (BP00)
2024-11-28 19:18:07.070 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connection attempt: 1
2024-11-28 19:18:07.497 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3D:E6 - 60:6E:41:0F:3D:E6: Connected after 1 attempts
2024-11-28 19:18:17.309 DEBUG (MainThread) [custom_components.bms_ble] Setup of <ConfigEntry entry_id=01JCE7T5PRX4BJ1EKXK7G3VQ44 version=1 domain=bms_ble title=BP01 state=ConfigEntryState.SETUP_IN_PROGRESS unique_id=60:6E:41:0F:3C:24>
2024-11-28 19:18:17.309 DEBUG (MainThread) [custom_components.bms_ble] Initializing coordinator for BP01 (60:6E:41:0F:3C:24) as Jiabaida Smart BMS
2024-11-28 19:18:17.309 DEBUG (MainThread) [custom_components.bms_ble] device data: {'name': 'BP01', 'address': '60:6E:41:0F:3C:24', 'rssi': -88, 'manufacturer_data': {}, 'service_data': {}, 'service_uuids': ['0000ff00-0000-1000-8000-00805f9b34fb'], 'source': 'EC:62:60:8B:EB:F4', 'advertisement': AdvertisementData(local_name='BP01', service_uuids=['0000ff00-0000-1000-8000-00805f9b34fb'], tx_power=-127, rssi=-88), 'device': BLEDevice(60:6E:41:0F:3C:24, BP01), 'connectable': True, 'time': 2360722.147667102, 'tx_power': None}
2024-11-28 19:18:17.309 DEBUG (MainThread) [custom_components.bms_ble] BP01: BMS data update
2024-11-28 19:18:17.309 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Connecting BMS (BP01)
2024-11-28 19:18:17.309 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3C:24 - 60:6E:41:0F:3C:24: Connection attempt: 1
2024-11-28 19:18:18.037 DEBUG (MainThread) [bleak_retry_connector] 60:6E:41:0F:3C:24 - 60:6E:41:0F:3C:24: Connected after 1 attempts
2024-11-28 19:18:18.254 DEBUG (MainThread) [custom_components.bms_ble] BP00: device communication timed out
2024-11-28 19:18:18.254 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching BP00 data in 11.184 seconds (success: False)
2024-11-28 19:18:18.254 DEBUG (MainThread) [custom_components.bms_ble] BP00: shuting down BMS device
2024-11-28 19:18:18.254 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP00)
2024-11-28 19:18:18.356 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP00)
2024-11-28 19:18:29.105 DEBUG (MainThread) [custom_components.bms_ble] BP01: device communication timed out
2024-11-28 19:18:29.105 DEBUG (MainThread) [custom_components.bms_ble] Finished fetching BP01 data in 11.796 seconds (success: False)
2024-11-28 19:18:29.106 DEBUG (MainThread) [custom_components.bms_ble] BP01: shuting down BMS device
2024-11-28 19:18:29.106 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnecting BMS (BP01)
2024-11-28 19:18:29.227 DEBUG (MainThread) [custom_components.bms_ble.plugins.jbd_bms] Disconnected from BMS (BP01)

@patman15
Copy link
Owner

This is not a Seplos V3 BMS (which is currently the only supported Seplos version) but something else, it's (most likely) wrongly detected as JBD BMS. Do you have any further information about this BMS? If so, please open a new feature request and add it there so we can track it separately from this topic. Thanks!

@andreas-bulling
Copy link

Indeed, they are Seplos v2... Thanks for your help!

@andreas-bulling
Copy link

#101

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants