I think we can use the existance of a active charge card to detect charing status. Does that update for you all also?
Hi iâm using the app for my NewMotion EV charger. Since yesterday I have a working homey energy dongle and able to act on energy levels. My goal is to create two charging modes:
- Charge the car as soon as possible by using the load balancing features of NewMotion itself
- Create a mode where I will charge dependent on the sunpower which is available in my home
I have the card âupdate the charge powerâ which could do the magic, but what will this do with the load balancing feature of my charger?
The newmotion does not support live output of power levels nor control them. That card only changes the calculation in the Homey app.
So you wonât be able with the newmotion charger. At least not the one I have.
Thanks for your fast reply!
28948fe1-b874-4a3f-8151-386f7ee516c2
Since 14:38 the app was updated and as of that moment the charge power is continuesly on. Nomatter what I do it reports the configured charging power (3.45kW). Even if the car is not connectedâŚ..I suppose it has something to do with the change in charging state handling?
@Kaoh could you please look into this?
Update again please
1 Like
Yep, looks ok now, 1W power now (as it should be). Thx for this fast service 
Unfortunately not completely correct
26279217-1489-48ea-9987-a89e33f0a9aa
After charging complete (but chargepoint in homey still active ) power is still reported.
(After putting device to off, the power goes to 1)
Yes, the active card based workaround keeps the status charging while a session is active. Even if the car is not charging anymore. There is no real way for me to solve this unless shell fixes the api data 
Ok, I understand, but before the app-update of 2 days ago it worked ok. Or did something on the api side change in this 2 days?
Did the charging state work for you still?
I am getting reports, and suffer myself, from the fact that the api stopped sending the charging state since a week or two.
Yep, still worked for me. I saw the messages here in this topic, and thought, strange, I donât have that problemâŚ.
Almost every day a charge cycle (10kWh, PHEV) without problems.
Hmm, OK so workaround needs te be done differently then. Iâll work on something this weekend.
I gave it some more looks;
for me (and obviously some others) the shell web site nor mobile app show the state of my sessions correctly anymore, and so they suffer from the same faulty data coming from the API as we do.
An active session is only shown as occupied, charging is never activated anymore. Ending the session will show it as available again.
I now linked the charging to an active session but indeed when the car stops by itself without us stopping the session the homey app now continueâs to think the car is drawing power while it does not anymore.
Based on the data from the API there is no real workaround possible. So I will revert my change to ensure it keeps working as before and hope they fix the API status of the chargepoint.
@Torch1969 what newmotion point do you own? I have a Lolo3, I am now focusing on determining why it still works like before for you.
@Kaoh I have a shell recharge home advanced point. Based on pictures is suppose itâs the same as new motion lolo3.
I almost never look in shell recharge app and website. Always in homey app and in home asssitant energy dashboard (I forward the charge point to home assistant where charge point power is logged, so Iâm sure the starting and stopping of power consumption of last weeks was correct).
You have a newer model I see, the model of your CP is NA22-603S212100L while mine really logs LOLO3 in the data. I also see yours gives more states than just the available, connected, charging. Yours also gives a preparing and a suspendedev state.
Interesting. So indeed it still works for you. So that points us that older, like the original LOLO3, are falling out of their support.
Ill give mine a proper powercycle, and charge some tomorrow, lets see if that changes the bavior.
Its sad that they are not aligning those states, the suspendedev one is really nice.
Ok, thatâs interesting indeed. I did send another debug report for the disconnected situation.
My charging point was installed on 21 April 2023. It also has a load balancer connected (with ct-clamp). Maybe the extra states are because of that?
If you need me to do check-out/debug/test some things, let me know.
Perhaps it has already been asked, but why doesnât the app report the actual usage but the usage as set in the settings?
For example mine charges at a maximum of 11KW and as soon as it starts charging, it reports 11KW, whereas I have set the car to charge with 5 Ampère. So I would think the actual usage of the charger is about 2.8 KW
Because the charger doesnât report the actual value through the api.
Thatâs too bad⌠And to be honest: pretty stupid. Not blaming you of course, because you are not in control of the API.
But the sole purpose of a charger is handling energy⌠so I would think reporting energy usage should be top priority if youâre creating an API
