JuicePassProxy Add-On - Control your JuiceBox EV Charger 100% locally

Hi everyone,

I wanted to let you know about a new Home Assistant add-on I just released that lets you run JuicePassProxy inside Home Assistant. If you aren’t familiar with it, JuicePassProxy is a reverse-engineered implementation of the protocol used by JuiceBox EV Chargers. Once you have it set up your JuiceBox charger will think that it’s talking to the cloud, but it will actually be talking to JuicePassProxy which will forward all data to Home Assistant over MQTT. Everything is 100% local with no cloud dependencies, and the JuiceBox charger does not need Internet access.

This does not require opening up the charger or making any modifications to it, all you need to do is override a DNS record or set up some NAT rules on your router. I’ve included instructions on how to up these NAT rules in OPNSense, and I’m happy to review PRs with instructions for other types of routers.

The add-on can be found here: GitHub - jaydeethree/hassio-juicepassproxy: JuicePassProxy as a Home Assistant add-on

Let me know if you have any questions or find any bugs :slight_smile:

3 Likes

For the OPNsense NAT rules, the port forward should be on the WAN interface, right? What about the outbound? I’ve always had a hard time keeping the NAT rules straight.

Thank you for making this available as an add-on.

Since this is an internal port forward you should pick the interface that your JuiceBox is connected to, not your WAN interface. I updated the README to make this more clear.

Let me know if you have any other questions :slight_smile:


What I have so far. I guess that means MQTT is working . . but am I missing stuff?

I think my port forwarding may be the issue. Stupid ISP routers don’t provide much flexibility.

Convinced that’s my issue, so ignore for now. Gonna ditch that PoS before I try this again.

Im trying to get this working but unfortunately the router we use doesn’t support DNS spoofing and changing routers is currently not an option.

I think I have everything configured correctly that UDPC mode should work but I haven’t had any luck so far. Where is the best place to ask for help? Would I ask here, on your GitHub (Since I am using this as a home assistant addon) or on the main JPP github?

Here is a link to the log, I started the addon right after plugging the juicebox in. I confirmed the IP hadnt changed using Advanced Ip Scanner.

image|281x500

Thank you!

You can ask questions here or in my GitHub repo.

The log you posted shows that the add-on is not able to connect to your JuiceBox at 192.168.86.95, so that’s why it isn’t working. You’ll need to make sure that’s the correct IP for your JuiceBox and that you don’t have a firewall blocking traffic from Home Assistant to port 2000 on the JuiceBox.

Thank you for the reply. This turned out to be a hell of a rabbit hole for me, but I did get it working. I deployed this at my dads house, ended up using an old laptop to host pihole and JPP in docker containers. If I get ambitions, I may try getting this all contained within home assistant, but its good enough for now.

I posted my path to sucess on the main Juice Pass Proxy github, here: How I got JPP working with Pi-hole and and a locked down router · Issue #134 · JuiceRescue/juicepassproxy · GitHub

Im not sure if that was the right place to post it, but I think my findings may be helpful for other people so I wanted to post it somewhere before I forgot everything.

Wow, that sounds like a lot of work! I’m glad you were able to get JPP working, and thanks for documenting everything - those kinds of posts are really helpful to the community.

1 Like