The first investigation suggests they killed the cars api part as it was. Since the site clearly lost support for the new one (site says to use the app instead) its a bit harder to relocate were it went or what the structures are 
They are clearly spending effort on reworking all the features into the app making the newmotion app a bit of a moving target right now.
Robert,
I had the same problem. I managed to solve this problem by deleted all the existing cars and then added a new one.
Then it worked
@Twan You are right, if I remove the car I added through the app, the API works again.
But when I re-add my car in the app, the API breaks again.
So how did you remove the old cars in there since the web is not allowing this in the UI anymore?
I think i added it via the UI at the web, about 2 weeks ago or so.
Is it changed very recently?
Hello new user here. This morning our charge point and account was activated. When trying to add our charge point as device I cannot select a car (which was added in the shell recharge app). Am I running in the same issue as you guys are talking about above? Any suggestions what I could do, or can I be of any help? Or should I just wait for a solution?
Hello @Kaoh , any idea if the current issue with the car selection can be solved? Maybe it’s an idea to remove car selection from adding device (or make it optional) and move this to the device settings? From what I read in the app description the car doesn’t add much functionality and having an account with a charge point and card should be enough to add the device.
I would love to add my charge point to homey, I hope you can solve this.
1 Like
I have been busting my ass on trying to sniff the traffic between the app and its new car api. But modern security really makes me work for it 
.
I agree, removing it makes sense, but i am afraid we might loose more features overtime.
2 Likes
I don’t mean removing it completely, but removing it (or make it optional) during the onboarding process of adding the device (charging point). User can add the car afterwards in advanced settings of device.
1 Like
Hello @Kaoh , any progress or news on this?
Unfortunately not, i decided to make the car selection optional but that means i cant rely on on knowing the car was selected, so not a quick change. And life is keeping me busy, and it will for some more weeks.
1 Like
Ok thx for this update. Good to know you’re working on it. Take it easy 
Ok, the good news is that I received a Pro 2023 model. So I am scheduling some time in fixing this app so it works on all configs for the new model (also with ethernet adapter used) and that means I will also make a add device path that does not force the cars list any more.
I am think of making the car a seperate device for now (so you can link the charge card to it) that you can add. And take it out of the carger part. Just need to consider how to do this without breaking existing implementations.
So it is on my todo list, and most of the stuff that kept me busy is wrapping up.
2 Likes
That is great news.
As a “not yet”-user I don’t understand the importance of the car in this app🤔. What functionality does it add? For me the charger and charge card would be enough to start a charge action. From the viewpoint of the charger the specific attached car isn’t important right? Monitoring/controlling my car can be done by the car specific app (for me KIA/ Hyundai).
If the car device is going to be necessary to start/stop charging, I (and other new users of this app) still cannot use this app as long as adding a car doesn’t work….and maybe you can safe the trouble for some breaking app-changes.
I don’t want to offence or you, but try to help in your thinking process…. 
1 Like
A good challange, so I used it to setup multiple cars in my system that have different charge cards assigned. So when car 1 is in the driveway I enable that car and the flow uses the assigned card to start the session, while if I enable car 2 it would use another card. The other way around also works, when a session with card x is started enable the car that has that card assigned.
We dont need the cars from the shell app for this, it was just ‘handy’ to surface those as options. But indeed not a very strong reason, so not important enough to break it.
ok, so here it is:
This version now removes the car api support. This means you do not need to select a car when adding a chargepoint. Any flow that has a carname token will now show ‘deprecated’ as carname.
Second it should now handle the new HP2023 UTP adapter (I did not test it with the actuall adapter) BUT since the hardware setup of your Homey is part of my salt for the encryption of the password you will have to re-login after switching adapters. You will notice when you run into this problem, the device will become unavailable with the reason ‘Forbidden’. Use the repair function to create a new encrypted password.
Added the try to repair support to make the providing of your credentials a bit more easy.
I also started with updating the text to represent the shell recharge rebrand.
1 Like
Hi @Kaoh , I am new to your app. Thank you for your work on this app! I have a hp2023, with ethernet adapter. I have an active login with shell recharge which originally was a new motion login. i have a personal 2014 lolo 2 charge point actively registered in it. Logging in fails from the start, also with this latest version. Diagnostic report: ae84500f-6629-4944-bf9f-9a2dc77cdcac
Hope it helps
Ok, so the ethernet adapter remains an issue i see in the log. I got one also, but did not use it yet. Will look into that.
I just tried it with my own adapter, i dont get the same issues 
. One question, has your wifi been configured and now you switched to utp or has it never been connected to the wifi at all?
@Twan can you test the new test app with your utp adapter connected?
I have never used wifi on this device
