Closed bigbadbitbasher closed 6 months ago
This has nothing to do with the new authentication. Volvo may work on the API. Just wait and maybe restart the addon some times.
Correct, this is unrelated to the OTP authentication. Despite many restarts since this behaviour popped up in version 1.9.0 the issue has remained; that's why I opened the bug report. I also tried removing/adding the add-in, but based on the log message it appears to be a misdirected API call maybe?
The 404, comes from the Volvo API. Your "Charging connection status" isn't supported by your car.
Willing to concede on that property - although it did work in 1.8.9. But that doesn't explain why V60 Battery Charge Level doesn't work, while V60 Distance to Empty Battery does. Is it maybe a different/older API call that these (non-AAOS) cars use? What changed in 1.9.0 causing these properties to stop being filled?
Nothing else, than the auth changed in 1.9.0. Charging connection status comes form the energy API, which only works for fully electric cars.
That leaves a Volvo API change as the culprit I suppose. Too bad, it was a working and welcome function. I'll work around it via another calculation trick using the remaining km in Home Assistant for now. Thanks for your responses!
Describe the bug Some battery properties for my 2014 V60 D6 Plug-in Hybrid are broken since version 1.9.0. They used to work fine in 1.8.9. These properties are populated correctly in 1.9.1:
But these are broken since 1.9.0:
To Reproduce: Steps to reproduce the behavior: (add a 2014 V60 D6 in the Volvo account being used :-)) -- I am aware this cannot be easily reproduced -- please contact me if you need debug data --
Expected behavior: The properties:
Should be populated correctly, like they used to do in 1.8.9.
Version info:
1.9.0 and 1.9.1 in Homeassistant as Add-On.
Logs: ... May 27 18:33:44 volvo2mqtt [106] - INFO: Failed, Charging Connection Status is unfortunately not supported by your vehicle. May 27 18:33:44 volvo2mqtt [106] - ERROR: API Call failed. Status Code: 404. Error: { "status" : 404, "operationId" : "790e23db-6a2f-4636-ae0c-2403c9042644", "error" : { "message" : "NOT_FOUND", "description" : "Car model is not supported" } } ...