Mark Avenius

0x30 in renogy_battery_bc is your battery ID, right? So 48 in base 10?

Perfect; thanks! I have three batteries daisy chained that I can access as 48, 49, and 50 via renogy-bt. Having the breakdown of the bytes is super helpful. On Mon,...

Yep, I figured that. I'll play with it ASAP; possibly today. Thanks again! On Mon, Jul 29, 2024, 09:57 Mateusz Drab ***@***.***> wrote: > Perfect; thanks! I have three batteries...

I have played with the code a bit and pulled some of the logic into a function that can be reused per-battery. Sorry for the possibly-garbage code; I'm very rusty...

Well I found a way _not_ to do it. Setting up three ble_clients is not the way to make it work. But as I think about it now, that's obviously...

@cyrils is this something you want as part of this project, or should it be spun off? It's obviously related (and heavily influenced) by what you've done, but it's also...

Actually, that was easy and reliable: ``` interval: - interval: 30s then: - ble_client.ble_write: characteristic_uuid: "FFD1" service_uuid: "FFD0" id: renogy_battery_esp32_bc value: !lambda |- vector request = GetBatteryRequest(0x30); return request; -...

BTW, huge thanks to @mateuszdrab for getting this moving; without what you shared, I wouldn't have been anywhere near getting this working.

Oh, snap:  ``` sensor: # Renogy battery 48 - platform: template name: "Renogy Battery 48 Current" id: renogy_battery_48_current device_class: current unit_of_measurement: A accuracy_decimals: 1 - platform: template name: "Renogy...

As soon as I get some more esp32s, I'm going to configure one for pulling Rover data.