EO Mini Pro 2 Smart Features Discontinuation (2025-11-30)

[bfayers]

If you haven't all received the communication from EO they're going to be shutting down the app along with all cloud services, and thus all smart functionality, for EO Mini Pro 2 devices essentially rendering them just a socket providing power all the time.

I'm a little disappointed that they won't even put the effort in to make one final update that adds, at the very least, OCPP support or a basic webserver onboard that could be used to pause/unpause charging.

All is not lost though, since October last year I've had custom software running on my charger for complete local access with a web interface, that also functions as a PWA, and a (slightly janky, but functional) MQTT interface to HASS.

I'll be tidying this up and releasing it soon (certainly before November 30th) along with some instructions for how to install it. Likely the best course of action for installing it will just be to pull the SD card from the Raspberry Pi 0W which is inside the device and reimage it with the latest version of raspbian lite, taking a backup if you really want to hang onto it.

[sjonez]

Not all heroes wear capes! Thank you so much for this!

[tom66]

This is really cool! I am part of a group of three other people developing something similar. Perhaps we could collaborate?

[bfayers]

This is really cool! I am part of a group of three other people developing something similar. Perhaps we could collaborate?

Possibly! You can always drop me an email at ben @ faye.rs if you need to coordinate something or details for another way of communicating.

I'm not sure how far you've got but ultimately all you need to do is talk RS-485 to the charger, I know of one other guy who got into his a while back and was doing write-only control (here: https://walmsley.tech/diy-ish-solar-ev-charging/) but I managed to make use of the Python libraries already on the device that EO had written to get data out of it too.

As it stands, I've got that web interface that provides full control working inside a docker container on the device using very recent (3.13.5) Python rather than the 3.5.3 that shipped with it so I'm confident that a much newer version of the OS could be used, even if I still dockerise the application for easier distribution.

[tom66]

Sent you an email, cheers

[Vikings39]

This is excellent. Mine will go out of service in a few months and I would really like to have some code on it with an interface that is independent of suppliers. I'm keen to know when you have something ready. Many thanks for your efforts so far.

[ndastur]

Had also started a project to do just this. Will email too and can help

[mauriero]

This is really cool! I am part of a group of three other people developing something similar. Perhaps we could collaborate?

Possibly! You can always drop me an email at ben @ faye.rs if you need to coordinate something or details for another way of communicating.

I'm not sure how far you've got but ultimately all you need to do is talk RS-485 to the charger, I know of one other guy who got into his a while back and was doing write-only control (here: https://walmsley.tech/diy-ish-solar-ev-charging/) but I managed to make use of the Python libraries already on the device that EO had written to get data out of it too.

As it stands, I've got that web interface that provides full control working inside a docker container on the device using very recent (3.13.5) Python rather than the 3.5.3 that shipped with it so I'm confident that a much newer version of the OS could be used, even if I still dockerise the application for easier distribution.

[tom66]

This is excellent. Mine will go out of service in a few months and I would really like to have some code on it with an interface that is independent of suppliers. I'm keen to know when you have something ready. Many thanks for your efforts so far.

I think it's ready! Check out https://github.com/minceheid/openeo for a 'beta' release.

[dragon2611]

I don't think it's quite fully ready yet for home assistant integration (unless I missed a release) but control from the local webui works fine (at least on my mini pro 2)

[Vikings39]

I really like the sound of this and I think it does most of what I'm looking for. Some good work!
I have a couple of questions about what's implemented. I'm looking to control the scheduling from a separate home server. Normally I'm making REST calls to control devices and for the charge point I probably just need a start and stop command. I guess I could use the OCPP commands if you have implemented those?
It will also be nice if (unlike the existing EO implementation) when a re-boot occurs (e.g. after a power outage), the device stays in the OFF state until instructed to start charging. Perhaps there's somewhere I could add that feature if you haven't implemented it already?

[dragon2611]

I think it will depend on if you have the application set to autostart or not, and assuming the PI boots ok from an unclean shutdown. (if it was a straight poweroff without the OS being shutdown)

I rebooted the PI just now and openeo loaded the previous configuration I had set.

Someone will correct me if I'm wrong but the behavior I'd observed when setting mine up suggests that if the PI isn't telling it otherwise the EO mainboard defaults to dumb charging/always on mode.

[Vikings39]

Thanks. I can try it out.
I noticed in the code there are some /api requests picked up. Is there a list of the requests this currently supports. Sounds like this might be just what I need.

[tom66]

We can't support that feature unfortunately without replacing the MCU firmware. The controller board defaults to always on unless the Pi is online and tells it otherwise.

Fortunately, the Pi does boot fairly quickly - within about a minute on my unit - so there won't be much charging after a power cut, assuming the Pi does come up correctly.

[Vikings39]

Thanks for the information. I can see the problem. The scenario where it's an issue for me is when there is an outage and then my Powerwall takes over with just a few seconds gap. It then doesn't have enough power to charge the car. I'll probably need to use the car api in that instance to stop the charging.
In other respects the EO code here looks good for me. I'm definitely going to try it. Any information on the /api format?

[Rubenconzels]

If you log onto EO charger broadcast WIFI and then allocated IP, it does come up with a web UI username and PW. I am not sure how functional this would be for control as I don’t have the required username and PW. I thought I mention this as it seems this is an alternative to the app based setup and another port of access to evaluate.