Hi Lucian,
thanks for your answer.
What i have observed is, that the normal polling cycle for the cars continues. However, for a short time, the information is not synchronized with the charging station at the start or end of charging. This isn’t a real problem, but it creates an inconsistency in the VRM’s real-time display. If possible, it would be preferable if the car status query were retriggered when the charging station’s charging process switches.
Let’s see if that can be improved from our side, I’m not sure
Goodmorning,
Do xpeng and zeekr also work in this beta version?
I see that BMW (and Mini) is still disabled in the beta car brand selection. I know that Enode supports the BMW properly, since it works fine in the “Frank Energie” app via the Enode backbone.
Isn’t it just falsely disabled in the dashboard due to closing down for home automation usage what BMW did last year? There was a period of time that nothing worked. But via Enode it should work fine now.
it’s coming soon !
Xpeng yes, zeekr no
you can find the list on Enode website - Enode Developers
My car (MG4) doesn’t have the option to stop charging at 80% State of Charge. Now with this integration, is there an easy way to tell the charger to stop when it reaches 80%?
it’s coming ! but until then, you can do it in nodered , 5 min 
Please do!! It would be very useful to add the EV and charger as a virtual device.
Another good option would be to provide an input in d-ess where the user can indicate expected EV consumption, for example: “I expect to use 20 kWh for EV charging.” Then d-ess could take that expected usage into account in its planning and optimization.
At the moment, EV charging can have a major impact on overall energy usage, so being able to include it would make forecasting and control much more accurate.
adding EVs as virtual devices will be possible soon. Adding EV chargers - no.
Good to hear this!!! Thanks!
I tried this feature last night for the first time. My experience:
Short version:
Within hours, Ford disabled my Ford account login because of suspicious activity and forced me to reset my Ford account password.
=======
Long version:
I added my Mazda MX-30 via the Beta VRM website. No problem. The Mazda showed up on the dashboard.
I tried to add my Ford Mustang Mach-e via the Beta VRM website. It told me I needed to use the mobile app, because a Bluetooth connection is needed.
I installed the VRM iOS Beta app on my iPhone via TestFlight. It never asked for Bluetooth access. When I check now, the VRM app still does not have Bluetooth access: see screenshot.
The Ford now showed up on my dashboard, but the Mazda was no longer shown. It was still in the list of devices, but no longer on the dashboard.
This morning I woke up and saw an email from Ford. See screenshot
Hi, we will check on our side why this is happenning, thanks for reporting!
Thx, Lucian.
When registering the car in the Beta VRM, I did get a very clear warning beforehand that this (account being blocked) could happen. So it was no surprise.
Ok, thanks! Maybe Ford is doing this by default, and you need to allow it first time.
Hi all,
Today we enabled support for BMW & Mini. The flow is the same as for all the other brands.
Best regards,
Alex Imbrea
Hi,
Good news!
I do see no test payment option anymore even though it is still in beta.
Is it already full payment now?
Hi,
The test payment option is still there. Just with Stripe now instead of Paddle: BETA: Connect your Electrical Vehicle to VRM - #121 by Lucian
We will update the original message at the top of this thread to reflect that as well.
How often is a read request made to the car? I’m asking because in some MG forums there are cases where users, using Home Assistant, were making so many requests to the car that it drained the 12V battery when the car was parked for a long period (holidays). I don’t know if this value might be configurable. Thanks.
