Hi, Iâm having issues regarding this configurations.
I created my account at Developers Volvo, created the Applications and request the publish ( *Status:*Publication under review).
In the Volvo2Mqtt in my home-assistant I added the user and password (from volvo) and the two keys from the applications. But i receive this error: [15:59:51] ERROR: Got unexpected response from the API: Service not enabled
Update: without any change now Iâm having success in the log file. Smoth and clean, but when I check the sensors (add it in the dashboard) it tells me that is unknow.
No, it doesnât work in the US. It used to â then sometime last year Volvo took the API entirely offline for North America. It worked great before that. Super frustrating.
I took the opportunity to send a note to the API support group about North America access when I got the email above about moving to API 2. Just crickets back. Email address in the note you see above.
Was trying to set this up myself a few weeks ago and ran into the âallowed marketâ issue too (Iâm in the US). Disappointing that a big market like the US is shut down. Maybe the US (and Australia, etc.) is moving to API 2 before other markets and thatâs why weâre shut down?
I just received a notice in my Volvo app that two factor authentication is coming. Hopefully that doesnât add another hurdle to getting this integration to work again.
Just getting back to a new HA install and finding that my previously-solid Volvo integration is no longer working (in the U.S.)!? This sucks.
Does anyone have suggestions for who at Volvo to contact about this? Iâm sure my dealer wouldnât care, but is there a team (with contact info) at Volvo Cars US and/or Volvo in Sweden who might listen??
A couple posts above is a note from Volvo about the change from API 1 to version 2. In that note is a developer support email address. I sent a couple of notes there but received no reply.
Thanks, @billraff ! I just realized after you pointed that out that Iâd received that email, as well. I just replied (not that I expect a prompt response).
I see that thereâs an issue with Babel locale = sl_SL.
Traceback (most recent call last):
File â/volvoAAOS2mqtt/main.pyâ, line 16, in
update_loop()
File â/volvoAAOS2mqtt/mqtt.pyâ, line 227, in update_loop
update_car_data()
File â/volvoAAOS2mqtt/mqtt.pyâ, line 237, in update_car_data
last_data_update = format_datetime(datetime.now(util.TZ), format=âmediumâ, locale=settings[âbabelLocaleâ])
File â/usr/lib/python3.11/site-packages/babel/dates.pyâ, line 719, in format_datetime
locale = Locale.parse(locale)
File â/usr/lib/python3.11/site-packages/babel/core.pyâ, line 391, in parse
raise UnknownLocaleError(input_id)
babel.core.UnknownLocaleError: unknown locale âsl_SLâ
I have a solar system integrated into HA and have installed a non-smart EV charger (3-phase 11kw) that was a gift from the dealership. I would love to be able to change Vehicleâs charging current limit (in ampere) in order to maximize my âself-useâ of power.
Is it possible to get the batteryChargeLevel out? It seems to be returned together with the fuel level on my car but there is no sensor or attribute with the value:
It will be very nice when the two new sensors (energy:charging_current_limit and energy:target_battery_level) are available.
After that my HomeAssistant can calculate the cheapest charging time by using the values; SoC, Target SoC, Charging Current and Spot price.
At the moment I have to enter the Target Soc and Charging Current manually.
(I use Volvo Cars app to set the Charging time.)
Re: the connection issue in North America and the transition to API 2, I got this message. I am not a developer of the integration; can anyone who is comment on whether this might be good news for North American drivers who would like a working HA integration again?
Important Notice: Deprecation of Connected Vehicle API Version 1 and Migration to Version 2
Dear Users,
With regards to the previous notice, this is a formal reminder of the imminent deprecation of Connected Vehicle API Version 1 on April 30, 2024. Kindly transition to Version 2 promptly to ensure uninterrupted service.
Explore the latest updates of Connected Vehicle API Version 2 [here]
[Connected Vehicle API Version 2]
For questions/assistances regarding this, contact us at [email protected].
@ajfi-droid2 Came here to research the same. They are definitely deprecating version 1 of the api now in favor of version 2 so im sure some updates are in order.
In regards to NA If you scroll down in the notification it explains that NA is not supported explicitly in production however that their api works globally in test.
I am not sure what âin testâ affects this integration but it makes me hopeful this project might be able to hit the test instance for us NA folk