Uconnect
hass-uconnect/hass-uconnect · vv1.0.2
Home Assistant integration for FCA/Stellantis cars (Fiat, Chrysler, Dodge, Jeep, Ram, Alfa Romeo, Maserati)
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 | |
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) | |
select | Mode picker (as switches) | |
device_tracker | Presence (as an occupancy sensor) |
What people report
Stellantis Uconnect cloud works for Jeep, Ram and Fiat vehicles; sporadic cloud timeouts and dependency breakages.
- Works2
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Jeep Grand Cherokee | Works Cloud | Oil life sensor reported (mislabelled oil level)Saved copyHello! I have an entity called `sensor.jeep_grand_cherokee_oil_level` however, I believe it should be Oil Life. It currently tracks what that app says for oil Life. thanks Excerpt saved from GitHub on 2026-10-23. | Issue #81 · 2026-02 | |
| Ram 1500 | Works Cloud | Vehicle model returned and registered; model type fixedSaved copyThe Uconnect API returns the vehicle model as an int (e.g. `1500` for a Ram 1500), which is passed straight through to `DeviceInfo(model=...)`. Since HA 2026.10, every startup logs: [code] (repeated for `binary_sensor.py`, `device_tracker.py` and `image.py`). This casts the model to `str` in `UconnectEntity.device_info`, keeping `None` as `None` so a missing model isn't shown as the literal text "None". Tested on HA 2026.10.1 with v0.5.4 (Ram 1500): after a restart the warnings are gone, the integration loads normally, all entities update, Excerpt saved from GitHub on 2026-10-23. | PR #132 · 2026-10 | |
| Fiat electric vehicle (Deep Refresh) | Partly works Cloud | Deep refresh needs charger plugged; cloud updates sporadic with 408 timeoutsSaved copy… keep getting sporadically and always for multiple days at the time the issue that updates are not working anymore. Closing the doors for example forces a refresh of the sensors, its not a great solution however. The error provided is the following: Error: 408 Client Error: Request Timeout for url: https://channels.sdpr-01.fcagcv.com/v1/accounts... I noticed also that in the app, at the battery status the refresh button was removed so i cant trigger a deep refresh. Excerpt saved from GitHub on 2026-10-23. | Issue #57 · 2025-11 |
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) | 775 (0.11%) |
|---|---|
| GitHub stars | 69 |
| Latest version | v1.0.2 (2026-10-21) |
| Set up in the UI | Yes |
| Maintainers | @blind-oracle |
| 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.
Sources
- Documentation: https://github.com/hass-uconnect/hass-uconnect
- Source code: https://github.com/hass-uconnect/hass-uconnect
- Issues: https://github.com/hass-uconnect/hass-uconnect/issues
- HACS: https://hacs.xyz
