Check my post above
I am DELIGHTED to have my North America C40 working again! Big thanks to @Dielee and to those who showed that it’s finally working again after it broke last year.
I’m pleased for those of you in the US. Still no love for those of us in Australia. 
1 Like
This is what i get, any idea?
14:39:10] ERROR: Got unexpected response from the API: Service not enabled
Nov 09 14:39:12 volvo2mqtt [107] - INFO: Starting volvo2mqtt version v1.10.5
Traceback (most recent call last):
File “/volvoAAOS2mqtt/main.py”, line 13, in
set_mqtt_settings()
File “/volvoAAOS2mqtt/util.py”, line 159, in set_mqtt_settings
raise Exception(“MQTT connection could not be established. Please check if your MQTT Add-On is running!”)
Exception: MQTT connection could not be established. Please check if your MQTT Add-On is running!
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
have you checked the host and port of MQTT server ?
CONF_mqtt environment parameter
Solved, re-installed all
After a few days of succesfully having this add-on pull data from the APIs I’m now stuck with a non-working state, logs don’t really show anything abnormal except for the service not enabled part?
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[21:44:29] ERROR: Got unexpected response from the API: Service not enabled
Nov 10 21:44:29 volvo2mqtt [107] - INFO: Starting volvo2mqtt version v1.10.5
Nov 10 21:44:29 volvo2mqtt [107] - INFO: Using login from token file
Nov 10 21:44:29 volvo2mqtt [107] - INFO: Refreshing credentials
Nov 10 21:44:29 volvo2mqtt [107] - INFO: Using VCCAPIKEY: *SNIP*
Nov 10 21:44:29 volvo2mqtt [107] - INFO: Vin: ['*SNIP*'] found!
Nov 10 21:44:30 volvo2mqtt [107] - INFO: Success! Battery Charge Level is supported by your vehicle.
Any ideas? I’ve checked the Volvo API page and the key is valid, it’s increasing number of calls when I restart the add-on.
I see some of us got this working in US. I have an XC90 and I have yet to get it working again. The official docs still say US is not supported.
How are you getting this working? My logs show every sensor with the same error:
Nov 11 09:28:42 volvo2mqtt [1] - INFO: Failed, Service warning status is unfortunately not supported by your vehicle.
Nov 11 09:28:42 volvo2mqtt [1] - ERROR: API Call failed. Status Code: 403. Error: {
"error" : {
"message" : "FORBIDDEN",
"description" : "No relationship to UUID"
}
}
Still no luck for me at Hong Kong, even tried with zh_CN and zh_HK
Anyway good to hear some new region got it supported.
I’m in the US with an XC40RC. I was receiving this same error. I saw that the VIN was optional in volvo2mqtt config so I removed the VIN and then it said that no vehicles were found. Using this clue I realized that I needed to pair my phone with the car, but my main phone would not complete the pairing process. Pairing a different phone worked and now volvo2mqtt detects the car (still w/o VIN in config) and everything is working.
Does someone have the climate feature working for EX30 BHEV?
I see there’s an airco feature but it turns on the airco, instead of pre heating the cabin.
1 Like
On my XC40 Recharge I can only toggle the HVAC on or off, it takes whatever the latest setting in the car was, no way to change it. Perhaps your setting was cooling?
1 Like
Same for me (HVAC). During the winter will just leave at 23 degrees, so when the HVAC turns it, it heats up the car 
Anyone else in US seeing electric range not returning correct value? I have a XC90 Recharge that in the last few days even after the Volvo app shows charge as complete and range at 34 miles the addon is showing 21 miles. Just started a couple days ago.
So still chasing this range discrepancy for my Volvo. I turned on debug on the addon and can see the correct value is returned -
Nov 24 10:58:12 volvo2mqtt [106] - DEBUG: {
“status” : 200,
“data” : {
“estimatedChargingTime” : {
“value” : “0”,
“unit” : “minutes”,
“timestamp” : “2024-11-23T15:14:47Z”
},
“batteryChargeLevel” : {
“value” : “100.0”,
“unit” : “percentage”,
“timestamp” : “2024-11-23T15:14:47Z”
},
"electricRange" : {
** “value” : “34”,**
** “unit” : “miles”,**
“timestamp” : “2024-11-23T15:14:47Z”
Yet the sensor at this moment reflects -
[sensor.volvo_yin_removed_electric_range] 21.13
I haven’t driven it this weekend but did reboot the infotainment system in the car to see if it would jog something loose but no luck. So the question is why would the sensor not reflect what the api call returned? Also, just noticed though the api call was done today -
Nov 24 10:58:13 volvo2mqtt [106] - DEBUG: {
All the data returned as a date of yesterday.
Oh it’s converting from km to mi despite the original data being in miles. I wonder why.