Just a note to others that my be using this cheaper battery than the other thread, as it took me forever (two days of searching and trying - so forever) to find something that worked with the BT enabled Eco-Worthy 100ah 12v battery. What ended up working for me is this:
I simply tweaked it for my board, MAC, and removed the MQTT / enabled the API and it worked right off the bat. These apparently use the āJBDā BMS setup, so it talks like that.
Mine is running on a D1 Mini 32, but Iām sure it would work on any ESP32 with BT.
I removed all the extra cell sensors as the 12v only has the four, but otherwise the data looks correct so far (a couple of days). Down side is you cannot connect the phone app at the same time I believe, but with this I never use it anyhow. Key data to me was voltage, capacity, and temperature.
[10:19:12][W][jbd_bms_ble:170]: [xx:xx:xx:xx:xx:xx] Not connected
[10:19:12][D][esp32_ble_client:416]: [0] [xx:xx:xx:xx:xx:xx] Event 46
[10:19:12][D][esp32_ble_client:191]: [0] [xx:xx:xx:xx:xx:xx] ESP_GATTC_SEARCH_CMPL_EVT
[10:19:12][I][esp32_ble_client:337]: [0] [xx:xx:xx:xx:xx:xx] Connected
[10:19:12][E][jbd_bms_ble:084]: [xx:xx:xx:xx:xx:xx] No notify service found at device, not an JBD BMS..?```
Just signed up to the forums so I could thank you for this tip! Worked like a charm with my ECO-WORTHY 12V 100AH LiFePO4 and a Seeed Xiao ESP32-C3. Simultaneously reading BLE data from my Victron SmartSolar charger 100/30 too!
Which one worked fine, the one at the top, or the HACS at the bottom?
Just got an Eco-Worthy 12v 100ah, and the one at the top keeps saying it canāt connect to the MAC address (Iām using the one the Eco-Worthy Android App shows), the HACS one says it canāt do those that appear as ECOxxxx as they are regular Bluetooth not BLE.
Does your battery identify as ECOxxxx? See the screen shot I posted above and that HACSā integration comment that those are not supported. Mine does, and doesnāt seem to show up in my ESPHome Bluetooth proxy.
Just a thought, but make sure the app is not connected to the battery as it will only talk to one device. My stuff has worked great for about a year now with two bluetooth batteries and 6 non BT versions in a bank. Just a thought.
I see, mine advertises as BLE and is relayed with esphome BT proxy
Unfortunately - the system is remote so I canāt see the BT advertisment
ESPHome proxy logs didnāt show much
I keep forgetting where this is, but if y ou have not see it go to the Bluetooth integration (NOT the BT Home), any device (not entity) line use the gear symbol and thereās an advertisement monitor as well as a visualization tool.
The latter is kind of scary how many things it āseesā, at least in my house. I have no idea what most of those are. My understanding is those are all BLE and regular BT combined. I think. I donāt know how to tell from what it shows if itās regular BT or BLE.
My office is too far to connect, so I was not. Unless itās necessary to explicitly disconnect (i.e. the BMS thinks it is still connected), but I see no such option.
So I donāt think thatās it. You are talking the ESPHOME code, right, not the HACS integration.
Yes - ESPHome is what Iām running and talking about. I donāt think you have to disconnect the app, it just cannot be connected or the unit doesnāt allow other connections. I ended up setting up another end point to monitor my second battery as it was getting messy reading the battery and the KP1100 inverter and slowing things down.
I discovered something interesting. When running the ESPHOME that fails to connect (above), it does prevent connection from the eco-worthy Android app.
