[NEW DEVICE] EP2000

[MegaBarf]

General

Device Name: EP2000
Device Bluetooth Prefix (EB3A*** f. ex., please remove the serial number after the prefix!):
Device IoT protocol: seems to be v2, see my fork, link below
Device with encryption (yes/no): runs without encryption, I can turn this on or off via the Device, could test this after adding
Similar device if available: EP800

Long time ago i forked your project version 0.1.5 and did a lot of trial and error until the EP2000 ran. I would like to use your project again because I'm no fit enough to maintain something like that.
Could you please add the EP2000?
Also please take a look at my fork if you have questions:
https://github.com/MegaBarf/hassio-bluetti-bt-EP2000

What I did (as of version 0.1.5):

• I have seen that in "custom_components\bluetti_bt\manifest.json" there is something called { "local_name": "PBOX*" } The EMS-Controller from the EP2000 is named EBOX* so I changed PBOX* to EBOX*.
• added { "local_name": "EP2000*" }, too
• I also changed all PBOX to EBOX in "config_flow.py"
• Then i added custom_components\bluetti_bt\bluetti_bt_lib\devices\ep2000.py I copied the one from the EP800 and renamed everything "EP800" to EP2000.

Not Tested:
"ADL400 Smart Meter for AC Solar"
This seems to be for coupling multiple EP2000 together. I can not test this.

Not working with my older fork and EP2000.py:

• Statistics (will not show up) not needed
• Battery packs (will not show up) not needed
• maybe because I commented them out somewhere, willing to test again

Thank you very much.

[Elliottmonaghan]

Might have a play around with this tonight to get some power figures to show up. Looking at the ep2000.py/ep800.py and some of the other configurations files you have, the power figure often shows before the voltage. So it may work if fields are added as UIntFields for 1313, 1319, 1325 for grid power per phase. Then 1510, 1517 and 1524 for AC Power per phase. Would be interested to see what happens.

[Elliottmonaghan]

Okay so I finally got a chance to test this out and have worked out that my original assessment and values are correct. I have also discovered that the ep2000 share most of the same values as the ep600 and currently have my own fork that I am using solely for testing purposes and have confirmed I can now see the power output of each phase and more.

[MegaBarf]

Hi,

I really tried to get your fork working but I ran out of time.

Somehow I can add your Repo into HACS and it will show up, but when I go to integrations and add "Bluetti" to the search I seem to get the one from Patrick762 only.
It looks like the one from Patrick762 is listed under "available to download" and I'm not able to remove it. When going to integrations I seems to get only one.

When trying to get back to my own older fork it was the same. As i ran out of time i restored a backup.
Your project seem to miss the issues so I had to report it here.

[Elliottmonaghan]

You may have to remove Patrick's package/repository, restart, install mine and then restart again. However my fork was never really intended as a stable release. While it should work it is the first time I have forked on github and is only to show a proof of concept. I'm also going to scan the actual values and submit an update to bluetti_bt_lib device list for the ep2000 soon.

I have also noticed an error in the way the unsigned integer is used. It is defined as unsigned in the code, when they should be signed integers. This causes the values to widely fluctuate whether importing or exporting. Will be another thing to edit, I have corrected this myself and confirmed with a template in home assistant for now.

[CanberraTinkerer]

I've spent some time working on EP2000, with my latest results here:

https://github.com/CanberraTinkerer/bluetti_mqtt_ep2000/tree/ep2000-support

I don't have time at the moment to update/support it - but it's there for you to use/abuse. The debugger.json is the most interesting thing - it contains a lot of metadata about the fields available, and how to extract them.

My intent was to use the debugger to help define the fields, and then contribute them back to the community to be used in some else's much better looking/better supported code.

A lot of the doco in markdown files represents my knowledge at a certain point in time - it's almost certainly wrong. Use the json file as the latest source of truth.

[Elliottmonaghan]

very interesting. Have had a quick look through the debugger.json and confirms that many of the sensors should be signed like I noticed when trying to correct the values in HA. I will have a more in depth look as some of the values are not lining up, mainly the smart meters and a few others. I have successfully added the ep2000 to my energy dashboard now using bluetti-bt and tested the values against the cloud readings and am happy with the accuracy. I also have a shelly 3pm that reads on my grid directly after my retailers meter which helps me verify the data.