Hey guys,
I will certainly look into this, it sounds promising!
Give me some days to learn more on this.
Mvg
Kenny
Documentation on the new free API:
Sent an email to my point of contact at CARIAD about two hours ago and already in touch with the Skoda team, so if you need any help; let me know! 
Hey @Doekse
Let’s talk about this and see how we can move forward. I’ll send an email later today.
Kind regards
Skoda is moving fast it seems, the latest update to the MySkoda app add the option to create API keys within the app.
Hello guys,
A short update from my side.
I have investigated the api, and it looks very feasible to switch to the new api, also I’m in touch with Doekse to get this app the official Skoda app for Homey.
Some rework will be needed, and initially not everything wil be supported, but I am confident that this is a good move for the community.
Groetjes
Kenny
I will be happy to help testing (might also help in development if necessary) I have a Homey SHS and Skoda Enyaq.
Hello all,
A new version was published to test, v2.0.0, install it from Skoda | Homey
This version switches to the Skoda API Keys and switches to TypeScript again, this should make the app compatible with Homey Pro 2019 and earlier, any tests are welcome!
Please be aware that all devices will be required to use the “repair” option to specify the API key.
The update interval is set to a default of 15 minutes, this might look slow but be aware that you only have 20 API calls per hour!
Some functionality was removed as it was no longer available in the new API.
Thanks for you feedback,
Thanks for the great work @KennyMoens ! What has been removed due to the new API? At first look I’m missing trigger cards.
And what was the update interval in 0.5.x? Is there a refresh button/flow card?
Hey,
The metrics for inspection intervals are removed.
Can you tell me what you are missing from trigger cards, I don’t recall removing anything besides the things above.
The update interval was 5 minutes, now it is configurable. I’ll check to add a refresh flow card.
kind regards
Looking forward to this integration (writing a Python script using the myskoda homeassistent library was fun, but I prefer to to consolidate all in Homey). Sadly it won’t yet work for me, and I want to report 3 issues:
- Connection does not work for me.
- The error messages are missing of incorrect
- The link to the gitlab homepage is broken
As for logging in, this is what I did:
- Installed the app, tried to connect, but that failed.
- Realised it was v 0.5.1 of the app, and deleted the app.
- Installed test version 2.1.0 of the app.
- Tried to add a new “Car” device
- Generated an API key in the MySkoda app, and filled it in the “Connect your Škoda” form
- Filled in the VIN of my car.
- Clicked “Connect”
The result was that the “Connect” button changed to “Connecting…” with spinning wheel, but after about 2-3 seconds it reverted back to “Connect” without providing any warning or error message. Trying again gave the same result. I would have appreciated such an error, so I know if the error was on my side, the app or the Škoda backend. Now I was left in the dark.
I tried with an invalid API key or an invalid VIN, and in both cases, I immediately got an error message stating that “The API key is invalid or has expired.”. This is incorrect: it also displays this message if the VIN is incorrect.
I also found it annoying that the API key was obscured (as a password field), so I could not check for obvious mistakes (like spurious spaces in the front or at the end; I don’t know if the app removed those or not – I checked later in a text editor: my key was fine).
Finally, when I wanted to report this, I found that the link titled “Source code” on the app page ( Skoda | Homey ) leads to https://gitlab.com/functor-solutions/homey/skoda, but that returns a 404: Page not found. (Perhaps you marked the repo as private?)
Hey,
I will check it out tomorrow, could you already make me a diagnostics report?
Did you have devices from the previous version, or is this a first time you install the app?
The error message might be the one I get from the API, I will do some tests to check out and provide feedback to the skoda team if confirmed.
I will check to make the api key during entering visible.
The source code repo should become public again, it is a mistake on my side 
, thanks for reporting.
Thanks.
I created a diagnostics report in the settings. It has code 4A7F8AAC and it says it is for Athom employees. Can you access that, or did you mean some other report?
No I cannot. You should create it from the app settings, then I will get it.
Hey guys,
@macfreek I’ve tried to reproduce you issue without luck, I could really use the diagnostics report or debug output if you run it locally in finding the issue.
I’ve pushed v2.1.1 to test, this makes the API key visible and the error message more generic.
kind regards,
Tried again with v2.1.1, same result. “Connect” changes to “Connect …” and reverts to “Connect” in ±1 second. I now created the diagnostics report in the app settings instead of the general Homey settings (sorry about that). Report has UUID 4b53e865-61a7-40ee-9c18-31d3326d0003. To be sure it is a valid combo, I also tried to directly use it using `curl -H “X-API-Key: msk_db4…meVlr” https://public.api.connect.skoda-auto.cz/api/v1/vehicles/TMBJ....3001` and that works fine. I only did that once and after testing the Homey, to ensure I was well below the rate limit.
Hey @macfreek
I get the impression that the validation logic is not called with you based on the logs.
Are you a bit technical? If so could you try pairing from your browser and open developer tools (F12) and see if you get any errors there.
Thanks
This is getting annoyingly weird.
- I started Chrome (not my usual browser, to ensure it was relative clean; no add blockers or other extensions that may interfere)
- To my surprise, it did connect, and showed my Enyaq. I aborted that last step, so I could try again on my phone.
- I tried again with the Homey app on my iPhone, and this time I was able to connect. I again aborted, and created another diagnostics report from the app settings (0e742216-3652-49e7-be80-17c0aa542207)
- I tried to connect on my phone, and now it did not work. (to my confusion and annoyance)
- I tried again on my computer, and that first failed with an “Another pair session is already active.”. But once I properly aborted my phone session, it still worked on my desktop.
- I tried a few more attempts in the hope I could get a clean recording on my desktop where it did or did not work, but on my desktop it worked all the times so far. I stopped after ±10 attempts (also bearing in mind that I might get other errors if I hit the API rate limit).
- In the end, I did add it from my phone.
To be honest I don’t know how to debug this further. The problem occurred a bit too often to chalk it to a transient connection error, but without proper log it is hard to pinpoint where the problem lies. I guess it is also up to you: do you want to pursue this now, drop it, or perhaps revisit when other people run into the same issue? I’m happy to try a debug version that prints some logs. For one thing, I’m curious what caused the app to move back from the state with the button showing “connecting…” to the state where the button showing “connect”. In my first post, I said 2-3 seconds, but it is shorter than that, likely ± 1 second. That’s fairly fast for a time-out, so I don’t think that was a time-out event. What other event could have caused that?
I gave it some thought: until there are other reports, let’s assume for now this is an issue with my phone. However, I would recommend adding a message why the button changed back from “connecting…” to “connect”, so the user (me) has some indication what’s going on.
