PyCupra
WulfgarW/homeassistant-pycupra · vv0.2.24
A home assistant plugin using the pycupra library to add integration for your Cupra or Seat car
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
climate | Thermostat | |
lock | Lock | Needs its own HomeKit Bridge in accessory mode |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
device_tracker | Presence (as an occupancy sensor) |
3 reports below say how a device from this integration behaves in the Home app.
What people report
Cupra/Seat cloud integration; HomeKit-bridged entities may show wrong state of charge; API blocks occurred in June 2026.
- Works1
- Partly works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Cupra Born | Works Cloud | Works in Home Charge attribute correct for first vehicle | State of charge shows correctly in HomeKitSaved copy@zomtec kannst du mal schauen ob das bei dir auch so aus sieht? Geräte & Dienste -> Integrationen -> bei Pycupra auf 1 Gerät oder x Geräte klicken. hier mein beispiel. Beim Born ist es ok, der hat wirklich 80% im Moment. Der Terramar hat 0% wird aber mit 100% angezeigt. Wenn ich jetzt auf den Terramar drauf klicke und in der Geräte-Ansicht bin wir oben rechte korrekt 0% angezeigt. Habe zum Testen mal den TargetSOC angepasst. da Excerpt saved from GitHub on 2026-10-23. | Issue #17 · 2025-10 |
| Cupra Tavascan | Partly works Cloud | Partly in Home Climatisation and unlock entities show wrong state of charge (80%) | Works; HomeKit shows odd charge attributesSaved copyHi, I have some Entities of my Tavascan Bridged to HomeKit. In the Device-Details of these Entities in HomeKit, there is a state of charge shown, which is not correct. The value 80% is shown while my car currently has only 69%. I assume the value shown is taken from the target state of charge for charging. Excerpt saved from GitHub on 2026-10-23. | Issue #17 · 2025-10 |
| Cupra Terramar | Partly works Cloud | Partly in Home Shows 100% charge while vehicle at 0% | Works; HomeKit shows wrong charge valueSaved copy@zomtec kannst du mal schauen ob das bei dir auch so aus sieht? Geräte & Dienste -> Integrationen -> bei Pycupra auf 1 Gerät oder x Geräte klicken. hier mein beispiel. Beim Born ist es ok, der hat wirklich 80% im Moment. Der Terramar hat 0% wird aber mit 100% angezeigt. Wenn ich jetzt auf den Terramar drauf klicke und in der Geräte-Ansicht bin wir oben rechte korrekt 0% angezeigt. Habe zum Testen mal den TargetSOC angepasst. da Excerpt saved from GitHub on 2026-10-23. | Issue #17 · 2025-10 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Details
| Installs (analytics) | 73 (0.01%) |
|---|---|
| GitHub stars | 59 |
| Latest version | v0.2.24 (2026-10-17) |
| Set up in the UI | Yes |
| Maintainers | @WulfgarW |
| License | Apache-2.0 |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
