Today, I set up the dgthomson / 35e node-red flow to automate starting/stopping of shell recharge (advanced charger) sessions. It works, testing phase started .
Note to other people trying this and who use Double Quotes ", Single Quotes ', Parentheses (), and Square Brackets [ ] in their passwords: I had to change my shell account password. Although there was no issue to login at https://account.shellrecharge.com through browser and app, there seems to be something sketchy with the way that dgthomson/nodered escapes these characters, resulting in parsing errors “Unexpected string in JSON at position” etc. (using sr-2-50.json).
Anyway, it works after using a password without the above mentioned special characters.
Thanks a lot for sharing this project, dgthomson/@35e !
Hopefully, some day, shell will allow all end users to use their api directly… But until then, this is the best solution when you can’t wire a UTP cable to your charger.
Very interesting topic. I have a Newmotion Home Advanced 2.1 charger connected with an UTP ethernet cable. I can monitor the charging in home assistant using the setup by @joopmartens which works perfectly (thanks Joop!).
Next step for me would be to automate start/stop in Home Assistant. @drizzle you mention that there is an easier solution than the sophisticated node-red workflow by @35e and others when you have a LAN connection with an UTP cable like I do? I couldn’t find it in this topic. Any suggestions for that would be appreciated.
I wanted to use @joopmartens solution to monitor power consumption. My wallbox has been installed with ethernet and I can see the status via the app. But I’m not able to see the wallbox on my router or acess it via. http://charger.local:12800/user/status
any ideas?
Tom
Do you mean with “wallbox” the brand/vendor Wallbox?
This thread is about the brand/vendor Shell Recharge (Previously New Motion) chargers and probably not applicable to your Wallbox.
Sorry yes it’s a New Motion home Advanced. It was installed one Year ago and is connected via. ethernet. So I did expect I could see the Home Advanced in my Network via my fritzbox router but I’m not able to. Therefore my question.
I asked Shell Recharge to remove minimum charging current limitation. They refused at first, stating that 8A is minimum according to standard. I found the standard IEC 61980-1 and showed them that it’s actually 6A and not 8A, after which hey agreed to adjust it in the charger. After few bumps down the road, they eventually found which setting had to be adjusted and set it to 6A. Worked like a charm happily ever after
From Shell:
“Our team specialist has set the chargepoint.min.amp.per.phase to 6A, this is the minimum current and also set the Overcurrent protection to 40A.”
Possibly you have an issue that is causing mdns to malfunction on your local network.
You could try to verify which IP address has been assigned to the charger by your dhcp service (Probably your Fritzbox router) and use the url with the IP address instead http://<ip address>:12800/user/status.
In case this is working you can configure a dhcp reservation to make sure your charger always will receive the same IP address from the dhcp service.
One thing i’m still hesitant about is the move from 1phase to 3 phase charging. Whereas technically this is fully possible (both for my home connection as well as the connection and configuration by Shell) i’m reading very mixed results for the controlling of the charge. Is there anyone that managed to properly get 3-phase charging going?
I read through most of the content here and I can read the values via the /user/status endpoint. As I want to integrate the wallbox with EVCC and the REST API from Shell “Cloud”, I need to know, if the car is plugged into the wallbox or not. Unfortunately, I cannot see this in the status response.
@Zdr , I am starting to implement the solution from @thomase1234 (fake-xemex), and I am using the same board as you. Did you manage to use RX/TX via GPIO18/19? Is this the best option?
@thomase1234 , your fake-xemex-csmb solution on github looks very interesting. I have a question: my current measurement device looks exactly the same as the xemex, but it is from ShellRecharge (see picture). Will your code work as well on my setup? Thanks.
.
