[APP][Pro] We Connect / myAudi / MyŠKODA / My SEAT / My Cupra

New app update (TEST: 1.15.3) vw

Changelog:

  • NEW: update library
  • FIX: invalid capability

New app update (TEST: 1.15.3) Audi

Changelog:

  • NEW: update library
  • FIX: invalid capability

New app update (TEST: 1.15.3) Skoda

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • NEW: update API

New app update (TEST: 1.15.3) Seat

Changelog:

  • NEW: update library
  • FIX: invalid capability

New app update (TEST: 1.15.3) Cupra

Changelog:

  • NEW: update library
  • FIX: invalid capability


If you find any issues, send a report via the mobile homey app

More - apps - AppName - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)




You can install the TEST version by clicking the link above and press install

Don’t want to be part of this TEST version? Install the LIVE version → vwAudiSkodaSeatCupra

1 Like

Same here on v10.0.0-rc61 / Skoda App version 1.14.

  • no status updates after a little while.
  • the cards to trigger behaviour (e.g. climatisation) do not work.
  • no cards are triggered e.g. charging started/stopped.

A restart of the app resolves things temporarily w.r.t status updates, but not the rest.

Moving to 1.15.3 TEST to see whether this might resolve some things.

1 Like

New app update (TEST: 1.15.4) vw

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed

New app update (TEST: 1.1543) Audi

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed

New app update (TEST: 1.15.4) Skoda

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • NEW: update API
  • FIX: handleErrors - status update failed @Martijn_C @RogerSt

New app update (TEST: 1.15.4) Seat

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed

New app update (TEST: 1.15.4) Cupra

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed


If you find any issues, send a report via the mobile homey app

More - apps - AppName - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)




You can install the TEST version by clicking the link above and press install

Don’t want to be part of this TEST version? Install the LIVE version → vwAudiSkodaSeatCupra

1 Like

I am being served v1.15.3 repeatedly. I will try again tonight.

@RogerSt if you install from this page you should get 1.15.4: MyŠKODA | Homey

1 Like

Tried that. Tried it again. I suspect the pushing of the update does not work on my office PC. Will try home PC tonight.

Yup, it is the office PC issue. When I use my phone, it DOES install. Will test later today - thanks again for the support Martijn!

Dear Martijn, versions of the app come and go faster than I move or charge my cars, so I can’t give you full feedback yet, but as soon as I see a problem (or not) I’ll let you know :wink:

1 Like

Still not really working. Although at this moment the Skoda app itself is also not working very well. I have made an alternative flow to start and stop the charge from the charger instead of the car. That seems to work for now.

See logs: eeed34aa-092e-4329-a935-54fe6cecaaf8

1 Like

Nope does not work with the status updates.
1de438c1-48fe-4829-a761-f95004e15755

Tried charging around 21.57 today - charger reports charging; mySkoda App shows I am charging. No flow cards are triggered about this.
Also, although I took it off the charger a few hours ago, drove, plugged it back in to charge and started charging, no values for the Enyaq get updated.

1 Like

Update, some values DID get updated a few hours ago. But not everything. The measurements are not coherent. For example,

  • the range and estimated max range got updated;
  • the %charged status not.
  • plug connected not
  • is charging not

Hope this helps.

1 Like

Is someone willing to share their enyaq with me?
It’s really hard to debug this at the moment.

Not sure if it’s due to the API update or changes in the Skoda api itself, but I’m a bit guessing here.

Would be really helpful!

Check PM

1 Like

New app update (TEST: 1.15.5) vw

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed

New app update (TEST: 1.15.5) Audi

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed

New app update (TEST: 1.15.5) Skoda

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • NEW: update API
  • FIX: handleErrors - status update failed

New app update (TEST: 1.15.5) Seat

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed

New app update (TEST: 1.15.5) Cupra

Changelog:

  • NEW: update library
  • FIX: invalid capability
  • FIX: handleErrors - status update failed


If you find any issues, send a report via the mobile homey app

More - apps - AppName - settings wheel right top - send diagnostic report (put your email in the input field to make it easier)




You can install the TEST version by clicking the link above and press install

Don’t want to be part of this TEST version? Install the LIVE version → vwAudiSkodaSeatCupra

24f7a1ea-ff84-4c48-bd90-1b49a5e8939b

Skoda Octavia IV

Climatisation is reaching max limit and will not start, “to save the battery. Please drive the car before trying again”. I get this message in the real MySkoda app on the phone.

I have disabled all 3 versions of climatisation in Homey but this still happens.

If I disable the MySkoda app i Homey the problem doesn’t retur after a drive in the car.
If I Enable the MySkoda app in Homey - with or without the climatisation options activated - it will break climatisation again with too many request.

The app in Home Assistant doesn’t have this problem.

This isn’t a New problem. I tried this MySkoda app for Homey for about 6 months ago and also got this problem back then.

@WebLock
Just saw the report and sent you this answer: :slight_smile:

Report looks fine, no errors what so ever.

What you can do: enable debug in the device settings and send a new report. It might show some error messages in the logs.

Did you change anything to the force update interval?
Setting it lower than 360 might cause issues on your Car.
Increasing the normal interval might be a good idea too.

I guess it’s not only the climatisation, but the API calls in generic. As the Homey app will only call climatisation whenever the user requests it.


Edit: only difference between the Homey app and Home Assistant integration seems to be that Homey also fetches the temperature and calling the climatisation endpoint to return the temp.

Hi Martin

Than you for the answer.

I increased the force update interval from 360 to 3600 just before sending the report.

Enabled debug yesterday.

It is 2 hours since I came home from a 1 hour trip in my car and allready I cannot start climatisation.

I can lock and unlock from the Homey app.

Maybe you are right that the api calls in generel is hitting a limit and disables climatisation.

@WebLock

Hmm this is really strange, :confused:

Can you try to trigger climatisation from the Homey app and send a new report after that? (just to see some extra logs)

But have to dive into this why it’s behaving like this. It shouldn’t “wake” the car when it’s only refreshing the data. Only with a force refresh it should do that…

@WebLock

API response:

So seems like it taking too much energy from the car.

[error] 429
[error] {"error":{"errorCode":"mbbc.dispatcher.obd.rejectedJob","description":"The command was rejected because of energy concerns"}}

Not sure what your intervals are in the app.
But these are the default:

It was 1 minut and 360 minutes.

I changed it to 1 minut and 3600 minutes before sending the first report.

Will change it to 5 and 3600 minutes from now on and see if helps :slightly_smiling_face:

1 Like