I tried both as string and as int. Debugged in VS code and this is the body for the 403: {"error":{"errorCode":"RS.security.9007","description":"MBB Roles and Rights responded: 403 - Forbidden"}}'
The car is a few days old. Could be something has changed for MY21.
What car is it?
Because starting parking heater (combustion_engine_heater) isnāt available on all models even if the hardwate is there.
Not available on my MY20 Superb iV at least, only electric climatisation.
Edit: just realized you posted a successful(?) start above.
I canāt really help there since I donāt have the rs function.
Perhaps you can debug the skodaconnect lib? āskodaconnect: debugā under logger in configuration.yaml
I have tried to change there message format to XML when server fal-3a.prd.eu.dp.vwg-connect.com is used. Because this server is for newer model year so maybe it needs XML format instead of JSON. On my car for this heating it was using msg.volkswagen.de server and JSON formatā¦ If you confirm it is working, I can commit then this branch as permanent fix.
Is āRequest in progressā supported for anyone with Skoda?
Else I have a plan to implement force refresh of vehicle status data but this will break current implementation that triggers request updates.
I havenāt decided what might be the best approach since I donāt know how many requests are allowed until VW servers starts throttling (hard limit that gets reset after vehicle start).
Either we implement via manual refresh, a switch in HA that can be used manually or in automations.
Or we configure an automatic refresh based on how old the vehicle data is (with configurable age in configuration.yaml?).
The only problem with manual refresh would be we canāt add automations depending on the dataā¦ like give notification when electric battery is fully charged.
Iām going to experiment and see if I can trigger data update for the different functions or if thereās only refresh available for the vsr (vehicle status report) as is implemented for VW.
The App have a separate refresh icon on each section and as far as I can tell the update only updates the current section but Iām not sure if itās only a āGETā for the latest data on the servers or if it actually triggers an update from the vehicle. Will have to debug the app some more.
But so far when my car has been charging then it updates the data on the servers continuously. Not sure if thatās applicable for all sections though.
@Depechie - you are right, but with manual trigger you can create automation to update how often you wantā¦
@Farfar - I think we need to implement both - configurable parameter which will compare data age in received reply and update if older than configured parameter and also have manual trigger available for purpose of automations (like if I want to do something at 6:00 with data, I will schedule some force update for 5:55)ā¦
Yes, will also need to check if we are throttled, and if throttled block refresh until new data is received.
I am testing right now how many refresh I can issue before I get throttled.
@tanelv - you opened my eyes, thank you! During checking this urls I have also found why lock/unlock isnāt working - because SPIN token needs to be requested for specific operations and I am trying to lock/unlock with SPIN token for heatingā¦
Will fix this (but firstly need to fix chimney on my house )
Yes the 429 http code weāve known about, itās common for apis to use it.
The X-RateLimit-Remaining is great to know about! If a check is implemented then a potential automatic refresh can be deactivated so at least a few requests remain.
I successfully sent 15-ish refresh requests over a period of 1.5 hours until I got throttled.
Did you keep count?
Itās harder to keep track in the app since one action doesnāt necessarily wake up the car.