Is discovered there is a difference between the two flow cards to stop charging. “Stop active charging session” is declined every time by 50five portal. “Stop charging” is working ok. So I suspect there is a difference between the two of them in the way you send the command to the portal? I can’t tell the difference anyway between the two of them, so maybe remove the not working one?
Thanks, I’ll give that a check up this weekend also. I am stuck at home due to kids care while my wifi is on business trip, so should have more time for the laptop 
1 Like
I hope you mean your wife is on business trip, else your laptop won’t have internet connection
If your kids are to demanding, take a trial account on disney+ (if you don’t have already) and put your kids in front of tv. We won’t tell your wife 
haha, auto correct keeps messing things up, yes I meant my wife :D.
All streaming services are already part of the media options for the kids, but unfortunatly they did not get so addicted like the adverstisemnt promised 
.
I merged the country support and fixed the stop workflow action.
Ill look at the log history when I have new sessions in my own log again
1 Like
It looks like the name of the app in the homey app changed back from “50five” to “shell recharge”. Was that intentional?
I think you got pushed to the main release instead of the test version. Make sure to install the test version.
I still see it as 50five there
1 Like
Jep again, did update from within homey app…..
Forget my last debug report 
the this nights version should really have a big imrpovement on the different states. It includes the preperation detection (text based unfortunatly, so may fail for people in different countries, let me know if it does). When you plugin the car without starting the session it will show connected now.
The main charging capability button is our session state, so it will enable to start a session, the charging is linked to actuall power delivery, so it may turn of if the car stops charing (like full state), the main charging will remain active so you can stop the session and the connected remains true.
When you unplugg the car side with an active session I dont seem to get another state than full.
I also spend more time on trying out to iron out the peaks and negatives from the currentsession and usage meaters that happen if your session gets paused.
Be also aware of the recent charging state enum capability, it is a usefull multi state value that combines the other (connected, active charging, active session) into a single enum.
Country support is working perfect, thx
1 Like
I think reporting of charging power not working in 4.1.6 version?
6f142fd2-84c6-432d-85cf-08af7263b723
We are at 4.1.9 now
You’re so fast, I can’t keep up . Have to enable Automatic update….
Hi,
I’ve used the belux URL to log in but failed. I can log in with user & pass on the BeLux website so credentials are correct. What am I doing wrong?
Tnx
Try to put https:// in front.
1 Like
This night I had planned a charging session. This morning I discovered the car isn’t charged. In the loglines on portal I see this:
So “Laden (geen vermogen beschikbaar)” seems to be the cause. The rest of the night the lines show “Laden(vol)” and 0 kW power and 0 kWh energy. This is correct because the charging didn’t work. When I checked the car I discovered the charging connector wasn’t connected properly to the car. So everything is working as expected given this situation.
I would like to make an alert on this situation. In log of entity “charging status” I see “plugged_in_paused” a couple of times. Is this status raised when this error occurs?
It is set to that state when the charger logs the vol state for example. So when we have an active session, a connected plug but there is no car pulling current. After x minutes 50five starts reporting vol. I think it’s a conclusion their system makes
But that also happens when your car reached it’s limits
Yes, it’s hard to distinguish what”s really happening. Is it possible to have a separate state for the “geen vermogen beschikbaar” logline? I would like to raise an alert on that to check what’s happening.
For the normal situations this release version is working very well for me. 
I need to have it happen to me first, so I can use my inspect tools to capture the logine reuqest from the backend to see what status value it has at that point, for exmample idle is 0, pauzed 5000 etc
Just like offline or any other event state they might throw, I need to know the error code to implement it.
Hi, app Works fine en even better than with Shell. But would there come a way in the future tho see realtime power ussage? Thx
That should be working already in the 50five version. Is it not for you?
Can you pm me a details view from the 50five portal for an active session? Click on the +magnifying glass behind the session details on the charger overview, I harvest those details.
It works for my 1st Gen lolo3 and I have confirmation from others with mire recent models.
