core
core copied to clipboard
home-assistant
Enel X migrating from JuiceNet to JuicePass
The problem
Enel X is migrating from JuiceNet to JuicePass.
Received email stating:
To provide you with the best user experience and new functionalities, we are transitioning to a new and improved platform for charging management. Your charging station will be migrated to the new JuicePass app (Enel X Way app). The EV JuiceNet app along with web browser access to your charger via home.juice.net will no longer be supported after February 20, 2023. Configurability and control of your chargers must be done via the new JuicePass app (Enel X Way app) which can be downloaded on iOS or Android.
since migrating my account, the JuiceNet app shows “disconnected” while their new app JuicePass shows the current data.
Is there a plan to update the Home Assistant core JuiceNet integration to work with JuicePass?
What version of Home Assistant Core has the issue?
2022.12.5
What was the last working version of Home Assistant Core?
2022.12.5
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
I have the same issue with Home Assistant. The EV JuiceNet app is also showing “disconnected” as well as the browser web login at home.juice.net/Portal
Yeah I received an email notification from them saying they are shutting down the Juicenet portal and the Juicenet App which I assume meant the API that Home Assistant is using. Considering the API is mostly undocumented and I started this integration based on reverse engineering, I don't think it will be easy to migrate/update to use their new API.
I myself also do not use (or even have) a juicenet charger any more so I am not going to be of any use here.
- Jesse
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
Let's hope that a developer was using this integration and will be updating it to the new api #fingerscrossed
I took a look using a SSL/MITM proxy and couldn't make much sense of the APIs used. They seem to issue POSTs with no response and then possibly receive (gRPC?) data over Google APIs, maybe a firebase offering. I can't see too much further as the SSL isn't transparent between Google Play Services and their servers.
Spoke with support and they confirmed the API is going away and they have no plans in offering a similar product. I asked if they could submit a suggestion/request for one in the future This is one of the reasons I went with a JuiceBox. 😢
I'm guessing no API doesn't mean no integration. Is there still hope for this?
At this point, no. I hope enough customers request this feature so they see the demand and bring a new API online.
My chat with support on Jan 30th:
(09:37:31 PM) *** Spencer Simpson joined the chat *** (09:40:53 PM) Spencer Simpson: Hello Barry,
Your devices not connecting to home.juice.net is normal, and the phantom device in your app is a common product of the migration. After JuiceBoxes are moved to the server, they cease all communications with the home.juice.net server, and we are still moving on a timeline of completely shuttering it from Feb. 20th on. We can resolve the phantom JuicePass box by removing the unit from your home.juice.net account, leaving only the entry for your JuicePass account. (09:41:35 PM) Barry Michels: Ok. thank you. (09:42:24 PM) Barry Michels: So, is home.juice.net going away? I'm using that API to integrate the data into my Home Assistant server to log/monitor the energy delivered to my car. (09:43:01 PM) Spencer Simpson: Yes, it is going away, and there is definitely not a planned browser/web-based dashboard replacement. As for the status of a general residential user API, I am not able to confirm whether it is a planned feature at this time.
A decrease in the features will certainly affect customers experience, I contacted them to know if they plan on working on it since I primary bought it for that case and if they are offering a refund regarding this problem.
We also lost the ability to manage load groups, so I complained about that and the API being unavailable. I was about to buy a 2nd charger and wire it to the same circuit. In the old system, it would limit the total amperage of the group to the rated amperage through software, and that isn't a feature in the new app... so fire risk, tripped breakers if you had that setup during the migration? yikes.
We also lost the ability to manage load groups, so I complained about that and the API being unavailable. I was about to buy a 2nd charger and wire it to the same circuit. In the old system, it would limit the total amperage of the group to the rated amperage through software, and that isn't a feature in the new app... so fire risk, tripped breakers if you had that setup during the migration? yikes.
I lost the ability to control charge current via juice pro but figured out a way to control it from Tesla.
Got this today, so they don't seem to have their story straight but maybe there is hope.
We have a load group of 2 JB40 and still seem to be on the old system. Haven't received any migration email yet.
I did copy source locally and hard code max amp value at 40. That value was not being fetched correctly and would error (unable to set, valid range 6-0). Didn't want to dig too deep and fix properly due to the unknown status of the API.
If you have been impacted by this change, you can request support move you back to the old platform. It took a few weeks and requires a new token. It appears they know this migration has been a huge issue for their customers and they offered to move my system back. Not only did the new app/platform break the API, but it's TOU scheduling is broken, as well as load sharing capability doest not exist anymore either.
I started a reverse-engineering effort of the new Enel X Way API and have put my findings in a public Gist. Help is very much welcome! So far I have the endpoints, but need to understand authentication, potentially request signing, etc.
I started a reverse-engineering effort of the new Enel X Way API and have put my findings in a public Gist. Help is very much welcome! So far I have the endpoints, but need to understand authentication, potentially request signing, etc.
Looks promising, is there a way to request an API after the migration?
[I]s there a way to request an API after the migration?
Not that I know of. It’s all private.
I don’t want to share their code, since it’s probably copyrighted, but what I did was download the app’s .apk, and then decompiled it with an online tool. I think it’s written in Flutter, so more targeted techniques could potentially reveal better results, but I didn’t get to that yet.
Any update on this one? I just got forced to the Enel X Way app and lost JuiceNet access including the mobile app, webapp, and HA integration.
Happy to help contribute if I can. Wondering if there is any additional understanding of the auth component. I believe JuiceNet creds work for the Enel X app, so wondering if the JuiceNet tokens still work with Enel X. Enel X appears to have their own account system at my.enelx.com but the JuiceNet creds don't work there, and there's no apparent way to create an account. It would seem at first glance like the Enel X Way app is still using JuiceNet for auth, but I have not really looked at it all. Just at the point of realizing I got migrated and everything broke.
I don't know if this is helpful, but port 2000 is open for telnet to the Gecko OS of the JuiceBox - I tried to expose the web server on the wlan interface, and reboot, but the Juicebox seems to reset it to the softap/default on reboot. Maybe someone more industrious can figure out a way to expose something useful? I suspect you could really screw things up if you tried, so play around at your own risk...
$ telnet 192.168.35.xxx 2000
Trying 192.168.35.xxx...
Connected to gecko_os-afb.xxx.net.
Escape character is '^]'.
EMWERK-JB201-1.0.46, Gecko_OS-STANDARD-4.2.7-11064, WGM160P
> get ht s i
get ht s i
default
> set ht s i wlan
set ht s i wlan
Set OK
> network_restart -i wlan
network_restart -i wlan
Connection closed by foreign host.
I played around with Gecko as well, but I don't think it's going to get you anywhere. The Gecko OS itself is only aware of the GPIO pins on the Gecko chip, what matters is the custom software that Enel is running under Gecko OS and how that's interacting with the GPIO pins and the data that it's sending up to the cloud. Even if you could reverse engineer that piece of software, I doubt you could run something on the Gecko system to monitor it.
FWIW, I was told by Enel X support that I could no longer request to be switched back to JuiceNet once I switch to the new app. I decided to sell my charger, and get one that remains open for integrations, but soon found that in Enel X Way there is no longer a way to transfer ownership of a device. I wrote to support again and asked that they remove my ownership of the device so that I could resell it, at which point they were nice enough to move me back to JuiceNet.
kindly note that I have been successful in motivating that you be migrated back to EV JuiceNet so that you can continue using the web platform home.juice.net and API functions as you normally did, at least up unit the Enel X Way app is updated to support these features.
So there is hope. I busted out a new automation that automatically sets the amperage of my charger based on the remaining charge of my Powerwall. Works great except that charge_now off does not seem to work. It toggles in HA, but does not actually turn off. Oh well. Glad to have this much of an integration working so that car charging does not burn through my battery overnight or on cloudy days.
It looks like I've been moved automatically to the new platform. I never even installed their new app, the charger just started showing "unavailable" a few days ago.
@cgraf I just got off the chat with support, and they told me they ended the contract with the provider for the old platform. I would assume they'll probably force everyone on the new platform in the next few weeks.
This is very frustrating, as I bought that device specifically for the Home Assistant integration... I imagine I'm not the only one in that situation.
This is very frustrating, as I bought that device specifically for the Home Assistant integration... I imagine I'm not the only one in that situation.
Yuck. Now that I've been using the HA integration to control amperage of the Juice Box based on remaining Powerwall charge, I will sell the Juice Box and get something that can be integrated. Sucks, but what can you do.
@cgraf Any idea what can be integrated? The most promising integration I can see is OpenEVSE, but they say they won't export to Canada (missing UL listing, I believe).
Heh. I was just reading the forum to see what I would buy, and was specifically looking at OpenEVSE. Where do you read that they don't export to Canada? I was reading their discussion forums, and it looks like lots of users with with outdoor installations in Canada.
My charger is in the garage in Texas, so not the same level of concern. I did find an interesting thread about UL listing https://openev.freshdesk.com/support/discussions/topics/6000068314. It appears that all of their components are UL listed, but the device itself cannot be without expensive recertification each time they update the firmware, which kind of defeats the purpose of an open platform. They also mention that electrical inspection is not required for plug-in devices, only for hard-wired.
Please do share if you find some other Home Assistant compatible for North America.