Closed pergolafabio closed 3 months ago
The Wakeup/refresh doesnt work either, i get 404 errors ... I can help you with the new endpoints if you want ..., just tell me what you need? WHat car do you have btw?
For the door status, i see the Q4 entities are unsupported in the diag file, however, the overal doorlock is "locked", see below, in diag file, but the entitty itself says "unlocked"
"async_get_selectivestatus": {
"access": {
"accessStatus": {
"value": {
"overallStatus": "safe",
"carCapturedTimestamp": "0001-01-01T00:00:00Z",
"doors": [
{
"name": "bonnet",
"status": [
"unsupported"
]
},
{
"name": "trunk",
"status": [
"unsupported"
]
},
{
"name": "rearRight",
"status": [
"unsupported"
]
},
{
"name": "rearLeft",
"status": [
"unsupported"
]
},
{
"name": "frontRight",
"status": [
"unsupported"
]
},
{
"name": "frontLeft",
"status": [
"unsupported"
]
}
],
"windows": [
{
"name": "sunRoof",
"status": [
"unsupported"
]
},
{
"name": "roofCover",
"status": [
"unsupported"
]
},
{
"name": "sunRoofRear",
"status": [
"unsupported"
]
},
{
"name": "frontLeft",
"status": [
"unsupported"
]
},
{
"name": "frontRight",
"status": [
"unsupported"
]
},
{
"name": "rearLeft",
"status": [
"unsupported"
]
},
{
"name": "rearRight",
"status": [
"unsupported"
]
}
],
"doorLockStatus": "locked"
}
}
},
Tough i see in the appn the states of windows/doors/ ... not sure where its coming from...
Also usefull, command to set the climate temp, seems different also? here is from toolkit...
URL:
https://emea.bff.cariad.digital/vehicle/v1/vehicles/XXX/climatisation/settings
Request:
{
"targetTemperature": 21,
"targetTemperatureUnit": "celsius",
"climatisationWithoutExternalPower": true,
"climatizationAtUnlock": false,
"windowHeatingEnabled": false,
"zoneFrontLeftEnabled": false,
"zoneFrontRightEnabled": false
}
After fort state if succesfull:
https://emea.bff.cariad.digital/vehicle/v1/vehicles/WAUZZZFZ9RP076552/pendingrequests
response:
{
"data": [
{
"id": "ab1cef0e-d047-4fba-9dc3-b3b6691a6336",
"userId": "0e0f02f7-620c-42e5-87d3-35d76f700a75",
"vin": "XXXX",
"httpMethod": "PUT",
"path": "/vehicles/XXXX/climatisation/settings",
"capability": "climatisation",
"operation": "settings",
"operationGroup": "climatisationSettings",
"body": "{\"callback\":\"https://emea.bff.cariad.digital/vehicle/v1/vehicles/callbacks/XXXX/climatisation/settings/PUT\",\"climatisationWithoutExternalPower\":true,\"targetTemperature\":21,\"targetTemperatureUnit\":\"celsius\",\"climatizationAtUnlock\":false,\"windowHeatingEnabled\":false,\"zoneFrontLeftEnabled\":false,\"zoneFrontRightEnabled\":false}",
"vcfRequestId": "94f83793-6c2d-43ce-9f6f-95098b372d53",
"status": "in_progress",
"queuedOperation": null,
"timestamp": "2024-07-24T11:30:13.249758808Z"
}
]
}
After a few, the status changes to:
"status": "successful",
@pergolafabio Just FYI, the "original" Audi integration (https://github.com/audiconnect/audi_connect_ha ) works with my 2023 Q4. At least I can see 39 entities. Maybe restarting HA after logging in into Audi integration will solve your problems too? I have newer tried any services, not sure if they work.
The only problem with that integration (and with other Audi/Audi Q4 integrations I have tested) is that it loses the connection to the Audi servers after some days (I suppose, re-authentication is needed, haven't checked though). I know when this happens because Q4 location updates don't work anymore. Then I need to restart HA and everything works again few days. Luckily there are HA upgrades few times a month, and for me it is usually often enough to keep my Audi connection live.
Hey, i started with that one, but i dont get 39 entities at all , jus a few also climate/door status doesnt work, gps location is missing
What model of car do you have? i have a 2024 model, brand new, maybe stuff is changed ? My endpoints are different if i sniff the app , i also see 404 errors when i use this or the other fork, so audi must have changed something
ok, I'll do that for you next week
ok, I'll do that for you next week
Let me know if you need more info/endpoints? Maybe its only needed for 2024 models? not sure
@pergolafabio Just FYI, the "original" Audi integration (https://github.com/audiconnect/audi_connect_ha ) works with my 2023 Q4. At least I can see 39 entities. Maybe restarting HA after logging in into Audi integration will solve your problems too? I have newer tried any services, not sure if they work.
The only problem with that integration (and with other Audi/Audi Q4 integrations I have tested) is that it loses the connection to the Audi servers after some days (I suppose, re-authentication is needed, haven't checked though). I know when this happens because Q4 location updates don't work anymore. Then I need to restart HA and everything works again few days. Luckily there are HA upgrades few times a month, and for me it is usually often enough to keep my Audi connection live.
for info, if i use that integration, i can only see these entities...
My Q4 is model year 2023.
audi_connect_ha integration is more active nowadays, they implemented support for Q4 (at least for older model years) few months ago. Maybe you want to ask if they want to add support for 2024 Q4 so that there would be only one common audi integration?
My diagnostics part has more entities (mainly related to doors, windows and position):
Yeah, i also have a issue open there to provide more info about the API , probably something changed in API for 2023 vs 2024 models What i'm missing in your sensor list , is the climate state? like "off"/ "heating" ? ... ? do you also have the "device" entity with GPS coordinates?
Where are you located btw?
I can't find anything related to the climate, but I have this:
My position entity has latitude and longitude as attributes.
And the location is Finland.
Can you do a remote lock/unlock? I don't have that feature on my car... The climate state is possible in the fork, I request to add it also on the other integration
Can you do a remote lock/unlock?
As far as I know lock/unlock has never been possible for Q4 using myAudi app.
I just tested unlocking via HA and didn't work:
Unable to unlock xxx: object of type 'NoneType' has no len()
Also start climatisation (as a service call 'Audi Connect: Execute Vehicle Action') did not work (404, ...vwg-connect.com)
yeah, they are also fixning it now in this fork : https://github.com/audiconnect/audi_connect_ha
they already fixed the climatisation state already, that wasnt working either
quick update , my GPS location is now working, seems an issue with my license!
hey @cyr-ius , you dont need to add it here, its already be worked on in the official repo once added there, maybe you can compare the code to integrate it later, so you know the other endpoints as well for other regions.., gonna close here
Describe the bug Hi @cyr-ius , i got a new Q4 model 2024 this week, testing your fork, since the original fork doesnt provide all sensors, seems yours can do more First of all, i see the doors/windows/trunk status "open" while its closed? CLimater start/stop doesnt work, see error below
2024-07-24 09:01:56.957 ERROR (MainThread) [custom_components.audiconnect.services] ('Service not found: %s -%s (%s)', 'https://fal-3a.prd.eu.dp.vwg-connect.com/fs-car/bs/climatisation/v1/Audi/BE/vehicles/XXXX/climater/actions', {'error': {'errorCode': 'climatisation.auth.forbidden', 'description': 'The referenced vehicle with VIN: XXXXcould not be found or has no association to the given User'}}, 403)
Location doesnt work, see error below:
Additional context I have Frida enabled on my Laptop, so i can sniff/trace the API from the myAudi app, i think some endpoints are changed... For climate start/stop for example, i see below:
https://emea.bff.cariad.digital/vehicle/v1/vehicles/xxx/climatisation/start
with request
for stop:
https://emea.bff.cariad.digital/vehicle/v1/vehicles/xxx/climatisation/stop
For response:
https://emea.bff.cariad.digital/vehicle/v1/vehicles/XXX/pendingrequests
with response:
eventually:
"status": "successful",
@moritzwiechers : What is still working/nor working for you?