audi_connect_ha: Login to Audi service failed: 503, message='Service Unavailable', url=URL('https://app-api.live-my.audi.com/azs/v1/token'

2021-11-26 10:50:56 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] Login to Audi service failed, trying again in 10 seconds 2021-11-26 10:51:16 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] Login to Audi service failed, trying again in 10 seconds 2021-11-26 10:51:28 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] Login to Audi service failed: 503, message='Service Unavailable', url=URL('https://app-api.live-my.audi.com/azs/v1/token') 2021-11-26 11:00:02 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] Login to Audi service failed, trying again in 10 seconds 2021-11-26 11:00:13 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] Login to Audi service failed, trying again in 10 seconds 2021-11-26 11:00:25 ERROR (MainThread) [custom_components.audiconnect.audi_connect_account] Login to Audi service failed: 503, message='Service Unavailable', url=URL('https://app-api.live-my.audi.com/azs/v1/token')

Debug of custom component does not provide more details… HTTP component neither.

providing URL directly in browser does render some error response: no healthy upstream

I have no clue though if it can be fixed through code by providing a new/correct endpoint, or if the problem is at audi side…

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 4
  • Comments: 52 (12 by maintainers)

Most upvoted comments

see #95

I fixed the nickname issue. sorry for that.

That made sense, yes. I changed the graphql query to retrieve more information --> see new commit.

Beside renderings and technical specs, the following items can be queried:

  "data": {
    "userVehicles": [
      {
        "vin": "WAUZxxxxxxxx",
        "mappingVin": "WAUZxxxxxxxx",
        "csid": "%csid%",
        "commissionNumber": null,
        "devicePlatform": "MBB",
        "mbbConnect": true,
        "userRole": {
          "role": "PRIMARY_USER"
        },
        "vehicle": {
          "classification": {
            "driveTrain": "PHEV"
          }
          "core": {
            "modelYear": 2020,
            "modelCoding": "4KA0WY"
          },
          "hifa": {
            "factoryPickupDateFrom": "2020-xx-yyT06:00:00.000+00:00",
            "factoryPickupDateTill": "2020-xx-yyT08:00:00.000+00:00",
            "fbDestination": "DEU760   B"
          },
          "media": {
            "shortName": "Audi A7 Sportback TFSI e",
            "longName": "Audi A7 Sportback TFSI e 50 TFSI e quattro S tronic"
          },
          "pdw": {
            "pdwVehicle": false
          },
        },
        "nickname": null
      }
    ]
  }

I personally don’t use home assistant. I just use the code as a systemd service that forwards the received values using Telnet/SSH to a different home automation system. That means testing on my side is limited. But what I got from the error message is, that Requests class seems to be not usable in that way. So I changed the code to use aiohttp requests provided by AudiAPI class instead of Requests class.

xxx@i3serv:/usr/share/hassio/homeassistant/custom_components$ python3 test.py Traceback (most recent call last): File “test.py”, line 5, in <module> from audiconnect.audi_connect_account import AudiConnectAccount File “/usr/share/hassio/homeassistant/custom_components/audiconnect/init.py”, line 3, in <module> import voluptuous as vol ModuleNotFoundError: No module named ‘voluptuous’

Edit: I resolved the dependencies, but now test.py will not even accept the parameters. Seems like I’m becoming old. python3 test.py --user “x.y@web.de” --password “my-super-password” --spin “9876” --country “DE”

Unfortunately i have to confirm the issue.