Update Neey/EnerKey EK-24S4EB balancer support Version ZH-2.x

[svergata]

Hello,
I bought some new Versions of NEEY EK-24S4EB
Product Model: HW-3.2.0
Software Version: ZH-2.0.8
Production Date: 20240920

With this Version the detection an Readings from the Balancer does not nespond correctly and is not working.
No Device is found for quite log time.
Sometimes the device is found but no connect occurs.

Here some Debug Output.

[21:51:49][V][esp32_ble:331]: (BLE) gap_event_handler - 3
[21:51:49][V][esp32_ble:331]: (BLE) gap_event_handler - 3
[21:51:49][VV][esp32_ble_tracker:434]: Parse Result:
[21:51:49][VV][esp32_ble_tracker:451]:   Address: E3:36:4C:03:2E:97 (RANDOM)
[21:51:49][VV][esp32_ble_tracker:453]:   RSSI: -76
[21:51:49][VV][esp32_ble_tracker:454]:   Name: ''
[21:51:49][VV][esp32_ble_tracker:462]:   Ad Flag: 6
[21:51:49][VV][esp32_ble_tracker:477]:   Manufacturer ID: 0x02E1, data: 10.02.89.A3.02.C2.22.BD.14.F6.F8.EA.7B.F2.90.2E.10.0B.EF.C9.59.02.DE (23)
[21:51:49][VV][esp32_ble_tracker:486]:   Adv data: 02.01.06.1A.FF.E1.02.10.02.89.A3.02.C2.22.BD.14.F6.F8.EA.7B.F2.90.2E.10.0B.EF.C9.59.02.DE (30)
[21:51:49][VV][esp32_ble_tracker:434]: Parse Result:
[21:51:49][VV][esp32_ble_tracker:451]:   Address: 3C:A5:51:9C:11:0C (PUBLIC)
[21:51:49][VV][esp32_ble_tracker:453]:   RSSI: -67
[21:51:49][VV][esp32_ble_tracker:454]:   Name: ''
[21:51:49][VV][esp32_ble_tracker:462]:   Ad Flag: 6
[21:51:49][VV][esp32_ble_tracker:465]:   Service UUID: 0xFFE0
[21:51:49][VV][esp32_ble_tracker:465]:   Service UUID: 0xFEE7
[21:51:49][VV][esp32_ble_tracker:477]:   Manufacturer ID: 0x301C, data: 88.A0.3C.A5.51.9C.11.0C (8)
[21:51:49][VV][esp32_ble_tracker:486]:   Adv data: 02.01.06.05.02.E0.FF.E7.FE.0B.FF.1C.30.88.A0.3C.A5.51.9C.11.0C (21)
[21:51:49][D][esp32_ble_client:110]: [0] [3C:A5:51:9C:11:0C] Found device
[21:51:49][D][esp32_ble_tracker:674]: Found device 3C:A5:51:9C:11:0C RSSI=-67
[21:51:49][D][esp32_ble_tracker:695]:   Address Type: PUBLIC
[21:51:49][D][esp32_ble_tracker:222]: Pausing scan to make connection...
[21:51:49][D][esp32_ble_tracker:222]: Pausing scan to make connection...
[21:51:49][V][esp32_ble:331]: (BLE) gap_event_handler - 18
[21:51:49][V][esp32_ble:331]: (BLE) gap_event_handler - 18
[21:51:49][I][esp32_ble_client:067]: [0] [3C:A5:51:9C:11:0C] 0x00 Attempting BLE connection
[21:51:53][VV][scheduler:226]: Running interval 'update' with interval=5000 last_execution=672886 (now=677886)
[21:51:53][W][heltec_balancer_ble:226]: [3C:A5:51:9C:11:0C] Not connected
[21:51:58][V][mqtt.idf:121]: Event dispatched from event loop event_id=7
[21:51:58][V][mqtt.idf:124]: MQTT_EVENT_BEFORE_CONNECT

would appreciate to help in getting it running.

[syssi]

Is this your first balancer? Could you provide some details about your ESP32 module?

[svergata]

Yes my first one with BLE.

It's an AZ-Delivery ESP32 Wroom-32

[syssi]

Are you sure 3C:A5:51:9C:11:0C is the MAC address of your BMS? This MAC address is advertised without a BLE name which is uncommon. Could you try to use this YAML to find out the MAC address of your device?

https://github.com/syssi/esphome-jk-bms/blob/main/esp32-heltec-balancer-ble-scanner.yaml

[svergata]

Hi,
yes im pretty sure that the MAC addresses are right.
Sadly both Balancers only Send some time their name via BLE.
Here the Output of the scanner, and a screenshot from the Neey App.

[08:47:17][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495269,"address":"3C:A5:51:9C:14:EB","rssi":-62,"name":""}'               <-------NEEY-B01
[08:47:17][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495269,"address":"E3:FE:1A:B0:0B:5E","rssi":-87,"name":"MPPT 450/100"}'
[08:47:18][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495269,"address":"3C:A5:51:9C:11:0C","rssi":-62,"name":""}'               <-------NEEY-B02
[08:47:18][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495269,"address":"E3:36:4C:03:2E:97","rssi":-75,"name":""}'
[08:47:18][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495269,"address":"E3:FE:1A:B0:0B:5E","rssi":-90,"name":"MPPT 450/100"}'
[08:47:18][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495270,"address":"E3:FE:1A:B0:0B:5E","rssi":-91,"name":""}'
[08:47:18][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495270,"address":"E3:36:4C:03:2E:97","rssi":-75,"name":"SmartShunt "}'
[08:47:18][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495270,"address":"3C:A5:51:9C:14:EB","rssi":-57,"name":"Neey-B02'         <-------NEEY-B02
[08:47:18][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495270,"address":"E3:36:4C:03:2E:97","rssi":-74,"name":"SmartShunt"}'
[08:47:19][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495270,"address":"3C:A5:51:9C:11:0C","rssi":-83,"name":""}'               <-------NEEY-B01
[08:47:19][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495271,"address":"E3:FE:1A:B0:0B:5E","rssi":-85,"name":""}'
[08:47:19][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495271,"address":"E3:36:4C:03:2E:97","rssi":-75,"name":"SmartShunt"}'
[08:47:19][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495271,"address":"67:2C:62:37:CE:C5","rssi":-68,"name":""}'
[08:47:19][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495271,"address":"E3:36:4C:03:2E:97","rssi":-75,"name":"SmartShunt"}'
[08:47:20][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495272,"address":"E3:FE:1A:B0:0B:5E","rssi":-90,"name":"MPPT 450/100"}'
[08:47:20][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495272,"address":"3C:A5:51:9C:14:EB","rssi":-58,"name":""}'               <-------NEEY-B02
[08:47:20][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495272,"address":"E3:FE:1A:B0:0B:5E","rssi":-87,"name":"MPPT 450/100"}'
[08:47:21][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495272,"address":"E3:36:4C:03:2E:97","rssi":-74,"name":"SmartShunt"}'
[08:47:21][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495273,"address":"E3:36:4C:03:2E:97","rssi":-75,"name":"SmartShunt"}'
[08:47:22][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495274,"address":"E3:FE:1A:B0:0B:5E","rssi":-86,"name":""}'
[08:47:22][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495274,"address":"E3:36:4C:03:2E:97","rssi":-75,"name":"SmartShunt"}'
[08:47:22][D][text_sensor:064]: 'BLE Devices Scanner': Sending state '{"timestamp":4578295495274,"address":"3C:A5:51:9C:14:EB","rssi":-58,"name":""}'               <-------NEEY-B02

[syssi]

Could you provide another VERY_VERBOSE log like above using the esp32-heltec-balancer-ble-example.yaml again. I'm interested in some log messages indicating the advertised services and characteristics (which gets printed to the log):

https://github.com/syssi/esphome-jk-bms/blob/main/components/heltec_balancer_ble/heltec_balancer_ble.cpp#L181-L192

[svergata]

Find attached the generated Debug

logs_jk-bms_run-2.txt