I am happy to launch the “Shell Recharge” (formerly my New Motion) app.
Its inspired and forked from The New Motion app . However I quickly found that the use case is completely different than the original app by Jaimie Visser. So decided to include the name change to cover the new use cases better.
This new app is aimed to include your private Shell Recharge/New Motion chargers into your home automation. So it requires you to have an active account for account.shellrecharge.com with at least a single charger registered in that account and with at least one active charge card registered.
I believe that all owners of a lolo should meet these requirements anyway. But just to be clear.
So what does it do for you?
Start and stop charging sessions (using your default charge card)
Flow integration for starting/stopping action cards
Flow integration for changing charger status (also when triggered by website or physical charge cards)
You can find the app in the store now:
Well I am hoping someone else will enjoy the benefits of making your car charging smart and automated. I know it was a wish of mine for over a year now. Very happy that its working with Homey.
So first time using the new app store system for this. Not sure what the link should be for the app. Its officially in Test status now (replacing the previous Beta option). https://developer.athom.com/apps/app/com.newmotion.my
So lets see if this is what they mean with the link that is available in my dev dashboard.
ok, so how to start that review process? This app has been converted from an approved beta app to Test. No review is listed indeed. But the only option I have is to submit it for certification.
I submitted it now but not sure how long this would take.
That will depend on Athom. Normally, when there is no holidays, it takes a few days.
When u have some pics not looking sharp enough or a changelog in the README then it takes a copple of extra days.
All i have is what i could snif from website to their api communication. So no public api or docs. And since there is no way to set the amp from the website i am not sure how or if this can be done.
I know they use a api maintained by a foundation behind theirs, but the foundation does not open their generic charger api to persons only to chargepoint organisations.
So cant help you out there.
It was rejected due to some changes in store policies (there is a new place for change logs) so I just created a new build (with some new features in there). Its now in test, still now way to get a link as far as I can see though :(. So I will submit this version 2.1
The app itself installs without any issues, but when I try to add a chargepoint (initial setup) and it asks me for my NewMotion credentials, it gives me the message “Unexpected token F in JSON at position 0” when I click “inloggen” or “volgende”. Could you recommend a workaround for this?
You sure you installed the my new motion app? Sounds like the bug in the ‘the new motion’ app.
Can you confirm that you can use these credentials to login the the my new motion website, there is a chargepoint registered there and a chargecard setup? So can you use that site to start a charging session without any input?
I’ve checked again and I can confirm that I’ve installed your “My New Motion” app.
See screenshot:
I can also confirm that the credentials I am using are the same I am using to log into the official NewMotion website and I can start and stop charging sessions from their website using my account there.
So you get the same error?
Very strange that it works for me. What i do at that moment is try to get a bearere token by posting the login form to the website. To do that i first collect the form element names from the login form. Can you open the site from your location without loggin in and send me the source it generated?
Hi Kaoh, I’ve tried but got the same result. I would like to add something I see briefly before I get the error message. Aftet filling in my login credentials, the app goes to “Aan het zoeken naar nieuwe apparaten” and then to the message “Unexpected token F in JSON…”. So maybe the login form isn’t the issue but the step after that?
I’ve also generated an diagnostic report in the app config section. I don’t know if you received that in your developer portal at Homey, but maybe you can use that to see what is going wrong.
