Hi, thanx for your hit, I was no aware about vrm ios app BETA at all. So I just tried vrm at IOS as vehicle integration in production app was not possible. Now installed and all fine.
Odesláno z iPhonu
Hi @anttivaan ,
I can see that you are trying to connect to the NissanConnect US-specific backend. It might be that you are trying to log in with the wrong region. You can select the appropriate region for your account during the linking process, as shown in the screenshot:
Hope it helps!
Kind regards,
Lucian
Why do you request all Telsa car permissions? That seems like going to far, further than needed?
Also, why (especially if this is will be a paid feature) is this limited to customers with Victron EV Charger?
thanks,
Hi @tukutt1 , yes, this is a known issue where some Tesla’s don’t properly send over the unit they use for the car.
So the 332 is your range in miles, but Tesla does not specify that to VRM. We are working on fixing this!
You can select what permisions you allow, and based on that, you will have more or less info about your car. For example you can deny location. But then, some features are not going to work, like detecting if the car is connected to the home charger or not. Or trip reports. Or many other features that are location related.
Second question - Because some of the most important features will work only with our charger - like Dinamic ESS integration
I am not really sure. I drove some km.I have now 325 miles → 523km.
On Tesla App and Teslamate (installed my own home server) it’s is 422km.
Actually in my case it wouldn’t let me disable permissions. It said I needed all permissions in order to proceed, if I unchecke any then next button was made inactive. Very much looked like Victron was requesting all permissions.
Given you can start/stop charging and potentialy even control charge speed via Telsa API, why would integration not be possible? If integration was purely via the Victron charger, then why are you needing to connect via car API?
See the picture, you can select permisions. The communication with the vehicle is only one way, we are not controlling the vehicle, we are controlling our chagers. Why? For Dynamic ESS to properly work, we need to know how much energy is needed to finish charging. The location of the vehicle is needed to know if the car that is charging is at site or not
First, very cool addon.
Can report, have successful added Skoda Enyaq and Fiat 500e.
So far only find a minor translation issue for german language on remote console/settings/device : State of charge and charging state is both named/translated as “Ladezustand”. SOC should be “Ladestatus” or “Batteriestatus” otherwise it’s confusing.
One question left: Is it possible to use the device data within Node Red and if yes, how?
Thanks
Thanks dognose for your speedy answer. 
It’s working using the custom input node
BMW kann nicht verknüpft werden. Liegt aber sicher wieder an BMW 
Hi all,
We have switched to a new payment backend for the EV integration paid feature. You can use the same test card as before (see https://docs.stripe.com/testing for more details).
Besides the payment backend, everything should work as before. Please let us know if you encounter any bugs!
Kind regards,
Lucian from the VRM team
Hi @Victroniker,
Currently, the BMW and MINI integrations are not yet enabled. We hope to have it set up soon!
Kind regards,
Lucian
Looks like car links are lost today in the afternoon (5th of March). Must relink. Anyone else here?