API/Encryption Key

I have an outstanding ticket requesting the encryption key so I can use API to connect via BLE. I have not gotten any response. I was told this forum is strangely a more responsive way to get assistance for issues like these. My specific unit is an AC50b. Great device otherwise and I do appreciate Bluetti’s ability to allow users to communicate with their equipment!

Hi @sambes06

You mean to use the Bluetooth Integration that Bluetti provides on github right?

There is a integration that runs on Rasperry Pi too and can decode itself for every unit, without the need of the file from support.

Oh, interesting. I’ll give this a try in the short-term, but does this present a bit of a security risk? I imagine Bluetti will patch/update their firmware to nix this path in the future. The device license CSV path has to be preferrable by Bluetti as to control third party access to BLE? Or am I thinking about this wrong?

Im not 100% sure how the encryption work on this integration, it think the creator just reverse engineered the encryption and found a way to decrypt it. Unlikly they patch it since its hardware based encryption.

The Official and supported way is to request the encryption file for each unit