Just filled the form. Let’s see what happens. Actually I just bought a bluetti checking first at the home assistant bluetti2MQTT add on. I could not get it to run on my new AC70P yet though. A clean API might make life easier. I hope this API will be seamless if you connect BT, BT through Proxies (which seems not to work today) and Wifi. The trick that they just played activating encryptions seems to have made life to many more difficult than necessary. In any case such a device that cannot be controlled/supervised is a no go for me. It is cool to have a device to get power on the run but I cannot let it sit doing nothing while I am home and therefore must be integrated UPS some devices and/or increase solar energy own usage. Stopping charging is key for me and do not understand why the AC70P cannot do this. The 3 level of AC charging speed is also limiting: why not setting the ac charging power at the level you actually need (100W granularity would be fine). An efficient AC passthrough when there is enough AC input power to charge and satisfy the AC load but I guess the limit of the AC70P (or is this for all devices) to always run off the inverter is first a hardware issue.
At this time I will return my AC70P and will see if this API will increase the value I can extract of such a device.
Thanks to have suggested this poll.
I would like to have it as well.
Hi, this is great! Where exactly did you make these changes? In the filesystem somewhere?
Yes, i made those changes directly on the Filesystem of my HAOS installation via root accesss.
The files are stored somewhere under /mnt/data/docker/overlay2/.../diff/usr/local/lib/python3.13/site-packages/bluetti_mqtt/bluetooth/__init__.py
the exact location might differ for each installation, so i cant tell you the exact path. you should use find to locate the __init__.py python script and then you can edit it using vi
Or when you dont want to get Headache from using vi, than better use nano xD
Hi all,
I’ve been fighting in the past 3 days with my brand new Elite 200 V2 unit to integrate with HomeAssistant. As reported here the data communication channel is now encrypted and the protocol is updated to V2, so all the modbus registers are different now. I’ve forked and extended in the past warhammerkid/bluetti_mqtt to add support for my other unit, AC240, to be able to add the max grid current adjustments. Of course this has been invalidated by the new changes with V2 machines 
BTW, I also tried the bluetti crypt lib does not work on my raspiberry PIs, as it’s only available for x86_64.
HOWEVER… thanks for someone who pointed here to the nhurman/bluetti_mqtt repository, I’ve been able to include his changes and its preliminary implementation of the V2 protocol as well, and I spent the past 2 days reverse engineering the new Modbus registers and the protocol in general, and I think I finally have a working version for V2 units and encryption.
Now at least I’m able to switch on ac, dc, eco mode, grid charge and update the max grid charge current from HomeAssistant, and in general the modbus registers are now identified.
If someone is interested, the code it’s here, in the v2devices branch:
I’ve been testing this with my Elite 200 V2, so I cannot tell you if it works with other models too but should be fairly generic.
The updated server in github is also exposing prometheus metrics, for those who are interested.
Hi @desalvo
Thanks for letting us know! The Hassio plugin from Patrick als implement the code from nhurman recently. He is a real goat!
So, sadly but as expected: not much happening here in terms of a cloud or local API. @Bluetti, just to let you know: just did a project for 6 small off-grid holiday housing units, would have done it with Bluetti equipment, but one requirement was data integration into a billing system, so I had to use other stuff. (Can´t sell a hacked bluetooth connection to a commercial customer…)
Just to add it, heres a test from a EP760. The only thing thats missing for him are the MQTT capabilities.
This is exactly what i´m running in my own home too; works perfectly fine! For myself, using the bluetooth hack via a Raspberry Pi is OK (though not totally stable; I would still prefer a proper API!); I just can´t use that for any commercial customers.
I also need a 100% stable system, my BT via mqtt works fine with HA and my EP500pro, but I want a safer control for the shelly which makes the emergency charging if the battery is low (<20%).
Why not insert a WLan control funktion for shelly or other WLan switches with the Bluetti App?
So many other systems can manage it, why not here? The EP500pro is a great device, but the software is odd, the only thing which works perfekt for me is the advertising part in the App.
Cause the BT connection with HomeAssistant works until the BT device in my EP500 crashes, so the safety is gone 
Anyone building home assistant integration that will working with V2?