This release is a pre-release and may not be stable for production use.
CarConnectivity Connector for Skoda Vehicles
CarConnectivity will become the successor of WeConnect-python in 2025 with similar functionality but support for other brands beyond Volkswagen!
CarConnectivity is a python API to connect to various car services. This connector enables the integration of Škoda vehicles through the official Škoda Public API (public.api.connect.skoda-auto.cz). Look at CarConnectivity for other supported brands.
Getting an API key
Every request needs an API key. Keys are created and managed in the MyŠkoda app.
Are you on a mobile phone with MyŠkoda installed? Manage API keys
Reading this on a computer? Scan the QR code below with your phone to open key management in the app:
Don't have MyŠkoda? Download it here.
Prerequisites
This connector uses the official Škoda Public Vehicle API (beta). To use it you need:
- MyŠkoda app v8.16+ — create an API key in the app's key-management screen / QR flow.
- A list of VINs — the public API is vehicle-bound and has no list-vehicles endpoint; you must supply your VIN(s) explicitly.
Rate limit: The public API allows 20 requests per hour per API key. The default poll interval of 300 s (5 min) leaves headroom for commands. Do not lower the interval below 300 s.
Features supported by the public API
| Feature | Status |
|---|---|
| Vehicle status (doors, windows, lights) | ✅ |
| Fuel / battery level and range | ✅ |
| Odometer | ✅ |
| Parking position (GPS) | ✅ (requires Remote Access licence) |
| Air conditioning status + start/stop | ✅ |
| Window heating status | ✅ |
| Charging status + start/stop | ✅ (EV/hybrid only) |
| Charging settings (target SoC, mode, etc.) | ✅ read-only |
| Honk & flash | ❌ not in public API |
| Lock / unlock | ❌ not in public API |
| Wake-up | ❌ not in public API |
| Maintenance / inspection info | ❌ not in public API |
| MQTT push events | ❌ not in public API |
Configuration
In your carconnectivity.json add a section for the skoda connector:
{
"carConnectivity": {
"connectors": [
{
"type": "skoda",
"config": {
"api_key": "your-api-key-from-myskoda-app",
"vins": ["TMBJB9NY5RF999999"]
}
}
]
}
}
Configuration options
| Key | Required | Default | Description |
|---|---|---|---|
api_key |
see below | — | API key created in the MyŠkoda app |
vins |
✅ | — | List of VINs (or comma-separated string) the key covers |
interval |
❌ | 300 |
Poll interval in seconds (minimum 300) |
max_age |
❌ | interval - 1 |
Maximum cache age in seconds for vehicle data |
max_age_static |
❌ | 86400 (24 hours) |
Maximum cache age in seconds for vehicle images |
netrc |
❌ | ~/.netrc |
Path to a netrc file containing the API key |
Credentials
The API key can be provided either directly in the config file or via a .netrc file.
Option 1 — config file:
{
"carConnectivity": {
"connectors": [
{
"type": "skoda",
"config": {
"api_key": "your-api-key-from-myskoda-app",
"vins": ["TMBJB9NY5RF999999"]
}
}
]
}
}
Option 2 — netrc file (API key in the password field):
# ~/.netrc
machine skoda
login unused
password your-api-key-from-myskoda-app
With netrc the config can omit api_key:
{
"carConnectivity": {
"connectors": [
{
"type": "skoda",
"config": {
"vins": ["TMBJB9NY5RF999999"]
}
}
]
}
}
You can also point to a custom netrc path:
{
"carConnectivity": {
"connectors": [
{
"type": "skoda",
"config": {
"netrc": "/some/path/on/your/filesystem",
"vins": ["TMBJB9NY5RF999999"]
}
}
]
}
}
Known issues
Unexpected keys found
Not all items that are presented in the data from the server are already implemented by the connector. Feel free to report interesting findings in your log data in the Discussions section or as an Issue (Enhancement). My time is very limited, so usually new features take some time to get into the library, also because I need to align functionality between the connectors of all brands.
Skoda, if you want to talk, contact me. I have some ideas how this can be improved for Skoda as well as the users!
1 maintainer
Metadata
1 maintainer
Release files for carconnectivity-connector-skoda 0.13.2a2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| carconnectivity_connector_skoda-0.13.2a2.tar.gz | 32.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| carconnectivity_connector_skoda-0.13.2a2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.9 kB
Release files / carconnectivity_connector_skoda-0.13.2a2.tar.gz
| Download URL | carconnectivity_connector_skoda-0.13.2a2.tar.gz |
|---|---|
| Size | 32.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d871b2700dd174fe1bc883c9b48401c82e854fe99eaf6d515c6e70b26888ab7
|
|
BLAKE2b-256 checksum How to use checksums |
a1c143cee7c0216715b4e242f8095db06043eae6dcc5d7358243d2e05915da2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency logRelease files / carconnectivity_connector_skoda-0.13.2a2-py3-none-any.whl
| Download URL | carconnectivity_connector_skoda-0.13.2a2-py3-none-any.whl |
|---|---|
| Size | 28.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96f34ca8fbb99d316a7c3e3c7d05a99de824ff3be5bd44b1e782b2f13d98e8f6
|
|
BLAKE2b-256 checksum How to use checksums |
e8b48a7571d9ff36ca51787a189c045d976c01cc2f195eb9327f614afc65f6fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.
Transparency log
