JBD via BLE only working after first firmware flash, not connecting to BMS after ESP32 restart or wifi loss

[dan-cristian]

Hi @syssi , I think I need your help again!

I was able to run successfully yesterday the JBD EspHome component on an ESP32 WROOM, connecting to various JBD boards via BLE (5 battery packs):
JBD-SP04S020A-L4S-80A-B-U
JBD-SP10S009-L8S-100A-B
All went fine for about a day.

After restarting the router I noticed ESP32 did not reconnect so I did a reset for each board . After that reset the boards stopped working and never connected to the BMS via BLE.

I flashed again all boards with default firmware, then with the EspHome firmware. After flash, I noticed the board connects OK via BLE to BMS and starts sending data. However, after I restart the board (RST or Power Off), I can see it only connects to Wifi, then never connects to BMS via BLE.

I don't know why this is happening. I tried flashing several times, different ESP32 boards, same behaviour.

I have attached the log & config files.

Any help will be greatly appreciated.

STEP 1 - Build / upload firmware (did a clean before):

Linking .pioenvs/jbd-bms-ble/bootloader.elf
Building .pioenvs/jbd-bms-ble/bootloader.bin
Creating esp32 image...
Successfully created esp32 image.
Linking .pioenvs/jbd-bms-ble/firmware.elf
RAM: [== ] 16.9% (used 55432 bytes from 327680 bytes)
Flash: [======== ] 75.4% (used 1383789 bytes from 1835008 bytes)
Building .pioenvs/jbd-bms-ble/firmware.bin
Creating esp32 image...
Successfully created esp32 image.
esp32_create_combined_bin([".pioenvs/jbd-bms-ble/firmware.bin"], [".pioenvs/jbd-bms-ble/firmware.elf"])
Wrote 0x163400 bytes to file /home/dcristian/esphome/esphome-jbd-bms/.esphome/build/jbd-bms-ble/.pioenvs/jbd-bms-ble/firmware-factory.bin, ready to flash to offset 0x0
============================================= [SUCCESS] Took 30.08 seconds =============================================
INFO Successfully compiled program.
INFO Connecting to 192.168.0.74
INFO Uploading .esphome/build/jbd-bms-ble/.pioenvs/jbd-bms-ble/firmware.bin (1389568 bytes)
Uploading: [============================================================] 100% Done...

INFO Waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.0.74 using esphome API
INFO Successfully connected to 192.168.0.74
[23:05:55][V][mqtt.idf:073]: Event dispatched from event loop event_id=3
[23:05:55][V][mqtt.idf:093]: MQTT_EVENT_SUBSCRIBED, msg_id=24403
[23:05:55][I][app:102]: ESPHome version 2022.12.3 compiled on Jan 24 2023, 23:05:00
[23:05:55][I][app:104]: Project syssi.esphome-jbd-bms version 1.3.0
[23:05:55][C][wifi:504]: WiFi:
[23:05:55][C][wifi:362]: Local MAC: EC:62:60:9D:57:2C
[23:05:55][C][wifi:363]: SSID: 'iot'
[23:05:55][C][wifi:364]: IP Address: 192.168.0.74
[23:05:55][C][wifi:366]: BSSID: C4:6E:1F:87:D7:6C
[23:05:55][C][wifi:367]: Hostname: 'jbd-bms-ble'
[23:05:55][C][wifi:369]: Signal strength: -69 dB ▂▄▆█
[23:05:55][V][wifi:371]: Priority: 0.0
[23:05:55][C][wifi:373]: Channel: 11
[23:05:55][C][wifi:374]: Subnet: 255.255.255.0
[23:05:55][C][wifi:375]: Gateway: 192.168.0.1
[23:05:55][C][wifi:376]: DNS1: 0.0.0.0
[23:05:55][C][wifi:377]: DNS2: 0.0.0.0
[23:05:55][V][mqtt.idf:073]: Event dispatched from event loop event_id=3
[23:05:55][V][mqtt.idf:093]: MQTT_EVENT_SUBSCRIBED, msg_id=37194
[23:05:55][C][logger:293]: Logger:
[23:05:55][C][logger:294]: Level: VERY_VERBOSE
[23:05:55][C][logger:295]: Log Baud Rate: 115200
[23:05:55][C][logger:296]: Hardware UART: UART0
[23:05:55][C][logger:298]: Level for 'scheduler': DEBUG
[23:05:55][C][logger:298]: Level for 'component': DEBUG
[23:05:55][C][logger:298]: Level for 'esp32_ble_tracker': DEBUG
[23:05:55][C][logger:298]: Level for 'sensor': DEBUG
...
[23:05:57][C][esp32_ble_tracker:870]: BLE Tracker:
[23:05:57][C][esp32_ble_tracker:871]: Scan Duration: 300 s
[23:05:57][C][esp32_ble_tracker:872]: Scan Interval: 320.0 ms
[23:05:57][C][esp32_ble_tracker:873]: Scan Window: 30.0 ms
[23:05:57][C][esp32_ble_tracker:874]: Scan Type: ACTIVE
[23:05:57][C][esp32_ble_tracker:875]: Continuous Scanning: True
[23:05:57][C][ble_client:027]: BLE Client:
[23:05:57][C][ble_client:028]: Address: A4:C1:38:EC:1B:B0
[23:05:57][C][mdns:103]: mDNS:
[23:05:57][C][mdns:104]: Hostname: jbd-bms-ble
[23:05:57][V][mdns:105]: Services:
[23:05:57][V][mdns:107]: - _esphomelib, _tcp, 6053
[23:05:57][V][mdns:109]: TXT: version = 2022.12.3
[23:05:57][V][mdns:109]: TXT: mac = ec62609d572c
[23:05:57][V][mdns:109]: TXT: platform = ESP32
[23:05:57][V][mdns:109]: TXT: board = wemos_d1_mini32
[23:05:57][V][mdns:109]: TXT: network = wifi
[23:05:57][V][mdns:109]: TXT: project_name = syssi.esphome-jbd-bms
[23:05:57][C][api:138]: API Server:
[23:05:57][C][api:139]: Address: 192.168.0.74:6053
[23:05:57][C][api:143]: Using noise encryption: NO
[23:05:57][C][mqtt:065]: MQTT:
[23:05:57][C][mqtt:067]: Server Address: 192.168.0.12:1883 (192.168.0.12)
[23:05:57][C][mqtt:068]: Username: 'xxx'
[23:05:57][C][mqtt:069]: Client ID: 'jbd-bms-ble-ec62609d572c'
[23:05:57][C][mqtt:071]: Discovery prefix: 'homeassistant'
[23:05:57][C][mqtt:072]: Discovery retain: YES
[23:05:57][C][mqtt:074]: Topic Prefix: 'esphome/A4:C1:38:EC:1B:B0'
[23:05:57][C][mqtt:076]: Log Topic: 'esphome/A4:C1:38:EC:1B:B0/debug'
[23:05:57][C][mqtt:079]: Availability: 'esphome/A4:C1:38:EC:1B:B0/status'
[23:05:57][C][mqtt.binary_sensor:022]: MQTT Binary Sensor 'jbd-bms-ble charging':
[23:05:57][C][mqtt.binary_sensor:023]: State Topic: 'esphome/A4:C1:38:EC:1B:B0/binary_sensor/jbd-bms-ble_charging/state'
...
[23:06:04][W][jbd_bms_ble:172]: [A4:C1:38:EC:1B:B0] Not connected
[23:06:10][VV][api.service:470]: on_ping_request: PingRequest {}
[23:06:10][VV][api.service:043]: send_ping_response: PingResponse {}
[23:06:14][W][jbd_bms_ble:172]: [A4:C1:38:EC:1B:B0] Not connected
[23:06:24][W][jbd_bms_ble:172]: [A4:C1:38:EC:1B:B0] Not connected
[23:06:25][VV][api.service:470]: on_ping_request: PingRequest {}
[23:06:25][VV][api.service:043]: send_ping_response: PingResponse {}
[23:06:34][W][jbd_bms_ble:172]: [A4:C1:38:EC:1B:B0] Not connected
[23:06:36][D][esp32_ble_client:048]: [0] [A4:C1:38:EC:1B:B0] Found device
[23:06:36][D][esp32_ble_tracker:216]: Pausing scan to make connection...
[23:06:36][I][esp32_ble_client:064]: [0] [A4:C1:38:EC:1B:B0] 0x00 Attempting BLE connection
[23:06:36][V][esp32_ble_client:111]: [0] [A4:C1:38:EC:1B:B0] gattc_event_handler: event=40 gattc_if=3
[23:06:36][V][esp32_ble_client:111]: [0] [A4:C1:38:EC:1B:B0] gattc_event_handler: event=2 gattc_if=3
[23:06:36][V][esp32_ble_client:126]: [0] [A4:C1:38:EC:1B:B0] ESP_GATTC_OPEN_EVT
...
[23:06:37][I][jbd_bms_ble:091]: Request device info
[23:06:37][VV][jbd_bms_ble:434]: Send command: DD.A5.05.00.FF.FB.77 (7)
[23:06:37][D][esp32_ble_tracker:327]: Starting scan...
[23:06:37][V][esp32_ble_client:111]: [0] [A4:C1:38:EC:1B:B0] gattc_event_handler: event=9 gattc_if=3
[23:06:37][V][esp32_ble_client:111]: [0] [A4:C1:38:EC:1B:B0] gattc_event_handler: event=4 gattc_if=3
[23:06:40][VV][api.service:470]: on_ping_request: PingRequest {}
[23:06:40][VV][api.service:043]: send_ping_response: PingResponse {}
[23:06:44][VV][jbd_bms_ble:434]: Send command: DD.A5.03.00.FF.FD.77 (7)
[23:06:44][V][esp32_ble_client:111]: [0] [A4:C1:38:EC:1B:B0] gattc_event_handler: event=4 gattc_if=3
[23:06:45][V][esp32_ble_client:111]: [0] [A4:C1:38:EC:1B:B0] gattc_event_handler: event=10 gattc_if=3
[23:06:45][VV][jbd_bms_ble:101]: Notification received: DD.03.00.1D.05.51.00.00.1D.31.27.10.00.02.2A.E2.00.00.00.00 (20)
[23:06:45][V][esp32_ble_client:111]: [0] [A4:C1:38:EC:1B:B0] gattc_event_handler: event=10 gattc_if=3
[23:06:45][VV][jbd_bms_ble:101]: Notification received: 00.00.20.4B.03.04.03.0B.96.0B.97.0B.91.FB.A6.77 (16)
[23:06:45][VV][jbd_bms_ble:251]: Hardware info frame (29 bytes):
[23:06:45][VV][jbd_bms_ble:252]: 05.51.00.00.1D.31.27.10.00.02.2A.E2.00.00.00.00.00.00.20.4B.03.04.03.0B.96.0B.97.0B.91 (29)
[23:06:45][D][jbd_bms_ble:272]: Hardware info:
[23:06:45][D][jbd_bms_ble:273]: Device model:
[23:06:45][D][sensor:127]: 'jbd-bms-ble total voltage': Sending state 13.61000 V with 2 decimals of accuracy
[23:06:45][V][mqtt:415]: Publish(topic='esphome/A4:C1:38:EC:1B:B0/sensor/jbd-bms-ble_total_voltage/state' payload='13.61' retain=1)

It connects to BMS BLE and starts sending data, ALL OK so far.

STEP 2 - RST the board (or reconnect to same / different power source)

LOG FROM esphome run ...yaml command below:

INFO 192.168.0.74: Error while reading incoming messages: Error while reading data: [Errno 104] Connection reset by peer
INFO 192.168.0.74: Ping Failed: Error while reading data: [Errno 104] Connection reset by peer
INFO Disconnected from ESPHome API for 192.168.0.74
WARNING Disconnected from API
INFO Successfully connected to 192.168.0.74
INFO 192.168.0.74: Error while reading incoming messages: Error while reading data: [Errno 104] Connection reset by peer
INFO 192.168.0.74: Ping Failed: Error while reading data: [Errno 104] Connection reset by peer
INFO Disconnected from ESPHome API for 192.168.0.74
WARNING Disconnected from API
INFO Successfully connected to 192.168.0.74
[23:13:01][I][ota:113]: Boot seems successful, resetting boot loop counter.
[23:13:01][D][esp32.preferences:113]: Saving 1 preferences to flash...
[23:13:01][D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed

Complete silence, not connecting to BMS BLE.

Also logs from web.esphome.io terminal (with board connected via USB). Sending data ok, then reset, then nothing.

[D][sensor:127]: 'jbd-bms-ble min voltage cell': Sending state 2.00000 with 0 decimals of accuracy
[V][mqtt:415]: Publish(topic='esphome/A4:C1:38:EC:1B:B0/sensor/jbd-bms-ble_min_voltage_cell/state' payload='2' retain=1)
[D][sensor:127]: 'jbd-bms-ble delta cell voltage': Sending state 0.02300 V with 4 decimals of accuracy
[V][mqtt:415]: Publish(topic='esphome/A4:C1:38:EC:1B:B0/sensor/jbd-bms-ble_delta_cell_voltage/state' payload='0.0230' retain=1)
[D][sensor:127]: 'jbd-bms-ble average cell voltage': Sending state 3.40275 V with 4 decimals of accuracy
[V][mqtt:415]: Publish(topic='esphome/A4:C1:38:EC:1B:B0/sensor/jbd-bms-ble_average_cell_voltage/state' payload='3.4028' retain=1)
ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13132
load:0x40080400,len:3036
entry 0x400805e4
[I][logger:258]: Log initialized
[C][ota:469]: There have been 1 suspected unsuccessful boot attempts.
[D][esp32.preferences:113]: Saving 1 preferences to flash...
[D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[I][app:029]: Running through setup()...
[C][esp32_ble:026]: Setting up BLE...
[D][esp32_ble:040]: BLE setup complete
[D][esp32_ble_server:033]: Setting up BLE Server...
[D][esp32_ble_server:070]: BLE server setup successfully
[C][wifi:037]: Setting up WiFi...
[C][wifi:038]: Local MAC: EC:62:60:9D:57:2C
[D][wifi:048]: Loaded saved wifi settings: iot
[D][wifi:386]: Starting scan...
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:201]: Setting Improv to start
[D][esp32_improv.component:076]: Service started!
[D][wifi:401]: Found networks:
[I][wifi:445]: - 'iot' [redacted]▂▄▆█
[D][wifi:446]: Channel: 11
[D][wifi:447]: RSSI: -58 dB
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[D][wifi:450]: - [redacted] [redacted]▂▄▆█
[I][wifi:257]: WiFi Connecting to 'iot'...
[I][wifi:518]: WiFi Connected!
[C][wifi:362]: Local MAC: EC:62:60:9D:57:2C
[C][wifi:363]: SSID: [redacted]
[C][wifi:364]: IP Address: 192.168.0.74
[C][wifi:366]: BSSID: [redacted]
[C][wifi:367]: Hostname: 'esphome-web-9d572c'
[C][wifi:369]: Signal strength: -71 dB ▂▄▆█
[C][wifi:373]: Channel: 11
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.0.1
[C][wifi:376]: DNS1: 192.168.0.1
[C][wifi:377]: DNS2: 0.0.0.0
[D][wifi:527]: Disabling AP...
[C][web_server:092]: Setting up web server...
[C][ota:093]: Over-The-Air Updates:
[C][ota:094]: Address: esphome-web.local:3232
[C][api:025]: Setting up Home Assistant API server...
[I][app:062]: setup() finished successfully!
[I][app:102]: ESPHome version 2022.12.6 compiled on Jan 24 2023, 02:29:12
[I][app:104]: Project esphome.web version 1.0
[C][wifi:504]: WiFi:
[C][wifi:362]: Local MAC: EC:62:60:9D:57:2C
[C][wifi:363]: SSID: [redacted]
[C][wifi:364]: IP Address: 192.168.0.74
[C][wifi:366]: BSSID: [redacted]
[C][wifi:367]: Hostname: 'esphome-web-9d572c'
[C][wifi:369]: Signal strength: -63 dB ▂▄▆█
[C][wifi:373]: Channel: 11
[C][wifi:374]: Subnet: 255.255.255.0
[C][wifi:375]: Gateway: 192.168.0.1
[C][wifi:376]: DNS1: 192.168.0.1
[C][wifi:377]: DNS2: 0.0.0.0
[C][logger:293]: Logger:
[C][logger:294]: Level: DEBUG
[C][logger:295]: Log Baud Rate: 115200
[C][logger:296]: Hardware UART: UART0
[C][esp32_ble:206]: ESP32 BLE:
[C][esp32_ble_server:160]: ESP32 BLE Server:
[C][esp32_improv.component:215]: ESP32 Improv:
[C][esp32_improv.component:217]: Status Indicator: 'NO'
[C][captive_portal:088]: Captive Portal:
[C][web_server:125]: Web Server:
[C][web_server:126]: Address: esphome-web.local:80
[C][mdns:103]: mDNS:
[C][mdns:104]: Hostname: esphome-web-9d572c
[C][ota:093]: Over-The-Air Updates:
[C][ota:094]: Address: esphome-web.local:3232
[C][api:138]: API Server:
[C][api:139]: Address: esphome-web.local:6053
[C][api:143]: Using noise encryption: NO
[C][improv_serial:032]: Improv Serial:

AND it hangs here, nothing happens after.

esp32-ble-example_1b_b0.zip
esp32-ble-example-debug_1b_b0.zip

[dan-cristian]

Also, from time to time I get these errors on compiling/uploading firmware:

[C][api:143]: Using noise encryption: NO
[C][improv_serial:032]: Improv Serial:
[D][ota:147]: Starting OTA Update from ::FFFF:192.168.0.90...
[D][ota:316]: OTA in progress: 0.1%
[D][ota:316]: OTA in progress: 3.0%
[D][ota:316]: OTA in progress: 8.7%
[D][ota:316]: OTA in progress: 10.1%
[D][ota:316]: OTA in progress: 16.8%
[D][ota:316]: OTA in progress: 22.8%
[D][ota:316]: OTA in progress: 28.6%
[D][ota:316]: OTA in progress: 33.6%
[D][ota:316]: OTA in progress: 39.2%
[D][ota:316]: OTA in progress: 45.1%
[D][ota:316]: OTA in progress: 48.4%
[D][ota:316]: OTA in progress: 54.9%
[D][ota:316]: OTA in progress: 60.6%
[D][ota:316]: OTA in progress: 66.4%
[D][ota:316]: OTA in progress: 71.6%
E (55028) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (55028) task_wdt: - loopTask (CPU 1)
E (55028) task_wdt: Tasks currently running:
E (55028) task_wdt: CPU 0: IDLE
E (55028) task_wdt: CPU 1: IDLE
E (55028) task_wdt: Aborting.

abort() was called at PC 0x400f5544 on core 0

Backtrace:0x40083725:0x3ffbe9bc |<-CORRUPTED

ELF file SHA256: 0000000000000000

Rebooting...
ets Jun 8 2016 00:22:57

[syssi]

The ESP is pretty busy doing stuff and is unable to handle the OTA in parallel. I had the same issue with another setup and added a "safe mode button". Before doing an OTA I reboot the ESP into the safe mode using this toggle/switch to free resources. Does this help alread?

[dan-cristian]

How can I reboot in safe mode? Is that a physical button, if yes connected to what GPIO?
Thanks

[syssi]

[C][web_server:125]: Web Server:
[C][web_server:126]:` Address: esphome-web.local:80
[C][mdns:103]: mDNS:
[C][mdns:104]: Hostname: esphome-web-9d572c
[C][ota:093]: Over-The-Air Updates:
[C][ota:094]: Address: esphome-web.local:3232
[C][api:138]: API Server:
[C][api:139]: Address: esphome-web.local:6053
[C][api:143]: Using noise encryption: NO
[C][improv_serial:032]: Improv Serial:

AND it hangs here, nothing happens after.

The JBD component should try to connect to the BMS periodically. If the log output stops something bad is happening. Could you remove the improv component and hardcoded the WiFi credentials just for testing? I would like to rule out the improv component is the root cause.

Some more ideas:

• The JBD BMS is able to handle a single BLE connection. If your ESP crashs it's possible the old connection needs some time to get dropped. In between the ESP won't be able to talk to the BMS.
• If you have the chance please replace the BLE modules with UART connections. This will free a lot of resources and increase the stability of the setup. The ESP32 is able to handle 3 UART connections in parallel.

[dan-cristian]

I cannot find any "improv:" section in the YAML file, see below file content.

substitutions:
name: jbd-bms-ble
device_description: "Monitor and control a Xiaoxiang Battery Management System (JBD-BMS) via BLE"
external_components_source: github://syssi/esphome-jbd-bms@main
mac_address: A4:C1:38:EC:1B:B0

bms portable 12V 100AH

esphome:
name: ${name}
comment: ${device_description}
project:
name: "syssi.esphome-jbd-bms"
version: 1.3.0

esp32:
board: wemos_d1_mini32
framework:
type: esp-idf
version: latest

external_components:

• source: ${external_components_source}
  refresh: 0s

wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
manual_ip:
static_ip: 192.168.0.74
gateway: 192.168.0.1
subnet: 255.255.255.0
ota:
logger:

baud_rate: 0

level: DEBUG

If you don't use Home Assistant please remove this api section and uncomment the mqtt component!

api:

The MQTT component is ESP-IDF compatible since ESPHome version 2022.4.0. If

ESPHome suggests to use the arduino framework instead because of missing ESP-IDF

framework support you should update your setup.

mqtt:
broker: !secret mqtt_host
username: !secret mqtt_username
password: !secret mqtt_password
id: mqtt_client
topic_prefix: esphome/${mac_address}

esp32_ble_tracker:

ble_client:

• mac_address: ${mac_address}
  id: client0

jbd_bms_ble:

• ble_client_id: client0
  id: bms0
  update_interval: 10s

binary_sensor:

• platform: jbd_bms_ble
  balancing:
  name: "${name} balancing"
  charging:
  name: "${name} charging"
  discharging:
  name: "${name} discharging"

sensor:

• platform: jbd_bms_ble
  battery_strings:
  name: "${name} battery strings"
  current:
  name: "${name} current"
  power:
  name: "${name} power"
  charging_power:
  name: "${name} charging power"
  discharging_power:
  name: "${name} discharging power"
  state_of_charge:
  name: "${name} state of charge"
  nominal_capacity:
  name: "${name} nominal capacity"
  charging_cycles:
  name: "${name} charging cycles"
  capacity_remaining:
  name: "${name} capacity remaining"
  battery_cycle_capacity:
  name: "${name} battery cycle capacity"
  total_voltage:
  name: "${name} total voltage"
  average_cell_voltage:
  name: "${name} average cell voltage"
  delta_cell_voltage:
  name: "${name} delta cell voltage"
  min_cell_voltage:
  name: "${name} min cell voltage"
  max_cell_voltage:
  name: "${name} max cell voltage"
  min_voltage_cell:
  name: "${name} min voltage cell"
  max_voltage_cell:
  name: "${name} max voltage cell"
  temperature_1:
  name: "${name} temperature 1"
  temperature_2:
  name: "${name} temperature 2"
  temperature_3:
  name: "${name} temperature 3"
  temperature_4:
  name: "${name} temperature 4"
  temperature_5:
  name: "${name} temperature 5"
  temperature_6:
  name: "${name} temperature 6"
  cell_voltage_1:
  name: "${name} cell voltage 1"
  cell_voltage_2:
  name: "${name} cell voltage 2"
  cell_voltage_3:
  name: "${name} cell voltage 3"
  cell_voltage_4:
  name: "${name} cell voltage 4"
  cell_voltage_5:
  name: "${name} cell voltage 5"
  cell_voltage_6:
  name: "${name} cell voltage 6"
  cell_voltage_7:
  name: "${name} cell voltage 7"
  cell_voltage_8:
  name: "${name} cell voltage 8"
  cell_voltage_9:
  name: "${name} cell voltage 9"
  cell_voltage_10:
  name: "${name} cell voltage 10"
  cell_voltage_11:
  name: "${name} cell voltage 11"
  cell_voltage_12:
  name: "${name} cell voltage 12"
  cell_voltage_13:
  name: "${name} cell voltage 13"
  cell_voltage_14:
  name: "${name} cell voltage 14"
  cell_voltage_15:
  name: "${name} cell voltage 15"
  cell_voltage_16:
  name: "${name} cell voltage 16"
  cell_voltage_17:
  name: "${name} cell voltage 17"
  cell_voltage_18:
  name: "${name} cell voltage 18"
  cell_voltage_19:
  name: "${name} cell voltage 19"
  cell_voltage_20:
  name: "${name} cell voltage 20"
  cell_voltage_21:
  name: "${name} cell voltage 21"
  cell_voltage_22:
  name: "${name} cell voltage 22"
  cell_voltage_23:
  name: "${name} cell voltage 23"
  cell_voltage_24:
  name: "${name} cell voltage 24"
  cell_voltage_25:
  name: "${name} cell voltage 25"
  cell_voltage_26:
  name: "${name} cell voltage 26"
  cell_voltage_27:
  name: "${name} cell voltage 27"
  cell_voltage_28:
  name: "${name} cell voltage 28"
  cell_voltage_29:
  name: "${name} cell voltage 29"
  cell_voltage_30:
  name: "${name} cell voltage 30"
  cell_voltage_31:
  name: "${name} cell voltage 31"
  cell_voltage_32:
  name: "${name} cell voltage 32"
  operation_status_bitmask:
  name: "${name} operation status bitmask"
  errors_bitmask:
  name: "${name} errors bitmask"
  balancer_status_bitmask:
  name: "${name} balancer status bitmask"
  software_version:
  name: "${name} software version"

text_sensor:

• platform: jbd_bms_ble
  errors:
  name: "${name} errors"
  operation_status:
  name: "${name} operation status"
  device_model:
  name: "${name} device model"

switch:

• platform: ble_client
  ble_client_id: client0
  name: "${name} enable bluetooth connection"

• platform: jbd_bms_ble
  charging:
  name: "${name} charging"
  discharging:
  name: "${name} discharging"
  balancer:
  name: "${name} balancer"

[dan-cristian]

I tried again, flashed the ESP32 with default firmare using "https://web.esphome.io/".
Then I configured ESP to connect to home wifi.
The wifi address I get via router is always the same, fixed. It is also set in the yaml file.
Wifi credentials are also in yaml secrets.

Then I run comand: esphome run esp32-ble-example-debug_1b_b0.yaml
The firmare is uploaded via OTA to ESP32 via wifi (192.168.0.74).
Upload is succesfull, the command above does not show the logs right after upload, then it starts to show the logs after a while.

---

INFO Successfully uploaded program.
INFO Starting log output from 192.168.0.74 using esphome API
WARNING Can't connect to ESPHome API for 192.168.0.74: Timeout while connecting to ('192.168.0.74', 6053)
INFO Trying to reconnect to 192.168.0.74 in the background
INFO Successfully connected to 192.168.0.74
[18:48:02][I][app:102]: ESPHome version 2023.2.3 compiled on Feb 21 2023, 20:09:36

However it hangs again at improv:

[18:54:02][C][mdns:109]: Hostname: esphome-web-9d572c
[18:54:02][C][ota:093]: Over-The-Air Updates:
[18:54:02][C][ota:094]: Address: esphome-web.local:3232
[18:54:02][W][ota:103]: Last Boot was an unhandled reset, will proceed to safe mode in 7 restarts
[18:54:02][C][api:138]: API Server:
[18:54:02][C][api:139]: Address: esphome-web.local:6053
[18:54:02][C][api:143]: Using noise encryption: NO
[18:54:02][C][improv_serial:032]: Improv Serial:
[18:58:37][I][ota:113]: Boot seems successful, resetting boot loop counter.
[18:58:37][D][esp32.preferences:113]: Saving 1 preferences to flash...
[18:58:37][D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed

Not sure what else to do? Cannot find any "improv:" line in any file in the esphome folder so not sure how can I disable "improv".

[dan-cristian]

I would like to solve the connection via BLE as I do not have easy access / wiring done to connect via UART.

[syssi]

I will try to provide some support tomorrow. Do you have access to a linux host at your network?

[dan-cristian]

I think I found a cause of the problem. So far I was using OTA for firmware flash. I switched to Ubuntu and serial connection and flashed the ESP32 via serial, also disabled OTA component in config and now it seems to work much better, less problems. I'll run over night and let you know how stable it is. Clearly flashing via wifi/OTA is a problem with esphome.

[dan-cristian]

I can confirm that the setup works well now, after running it for several hours.
Concluding, I think these are the key things to do to avoid the issues I was having:

• only flash via serial, do not use OTA
• keep the ESP32 device very close to the batteries, 1 to 2 meters away maximum
• make sure you have good wifi signal, install a repeater nearby
• use good cables to power the ESP32, ideally power it via the 5V pin with a good transformer, avoid using the USB plug
• disable OTA in the config file
• use a 10 seconds delay between reads (throttle: 10s)

Hope this helps others that had similar issues.

[syssi]

I'm pretty sure you can add the ota component again without issues. The ota component doesn't interfere here for sure!

[dan-cristian]

OK, will try. thanks for your support!

[syssi]

If an OTA isn't possible because the ESP32 is under load you should add this safe mode switch to the YAML: https://esphome.io/components/switch/safe_mode.html

So you have the chance to boot into safe mode in future before doing an OTA. At the safe mode all resource intensive components like BLE are disabled.