NissanConnect
dan-r/HomeAssistant-NissanConnect · vv0.8.2
Unofficial Home Assistant integration for interacting with Nissan Connect vehicles 🚗
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 |
|---|---|---|
climate | Thermostat | |
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) |
What people report
NissanConnect cloud works for Leaf, Ariya, Juke and the new Micra; Townstar and Patrol/Armada still need endpoint work.
- Works3
- Not working1
- Requested1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Nissan Ariya | Works Cloud | Model name casing fix mergedSaved copyMy 2024 Ariya reports modelName as "ARIYA" in caps, not "Ariya", so the check in fetch_battery_status never matched and it always went to the v1 endpoint. v1 doesn't return rangeHvacOn for this car, so Range (AC On) was stuck on unknown. Made that comparison case-insensitive. MICRA is in the same if statement so it gets the same treatment. Tested on my car: range now shows 182 km, battery level still fine at 58%. Haven't tested a Micra or a Leaf. There's a separate MICRA check in fetch_all() that I left as it is, I have no way to test that one. Edit: also updated the fetch_all check as … Excerpt saved from GitHub on 2026-10-23. | PR #127 · 2026-09 | |
| Nissan Juke (2021 petrol, EU) | Works Cloud | Works; added to tested list by ownerSaved copyHello Dan, 1/FYI the integration works fine with 2021 Nissan Juke Petrol -EU 2/ What is the API on Nissan Server (EU) that the integration connects to ? (I would like to see what information is available for my car model and maybe request additonal entities. Thanks for your work 👍 Excerpt saved from GitHub on 2026-10-23. | Issue #69 · 2024-11 | |
| Nissan Micra EV | Works Cloud | Initial support via newer battery endpointsSaved copyAdds initial support for the new Nissan Micra EV. The new Micra does not support the legacy cockpit/Leaf battery endpoints currently used by the integration. Battery data is available through the newer v3 battery endpoint already used for the Ariya. This change: bypasses the unsupported legacy cockpit/Leaf battery path for Micra routes Micra directly to the v3 battery endpoint adds battery SOC parsing retains range, charging-time and plug-state data where available handles unknown charging/plug-state values without failing the whole update Tested against my Nissan Micra EV with NissanConnect … Excerpt saved from GitHub on 2026-10-23. | PR #120 · 2026-08 | |
| Nissan Townstar | Not working Cloud | Data fetch fails; needs different API endpoints, no merged fixSaved copyI tested the integration with a Nissan Townstar (non-EV) and it unfortunately fails when trying to fetch the data. The info that is provided in the Nissan Connect App is also very limited (distance driven, estimated range left, last known location), but it would be helpful to visualize this info in HA. Maybe there's a different API endpoint needed to get this information? ``` Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 762, in async_setup_with_context result = await component.async_setup_entry(hass, self) … Excerpt saved from GitHub on 2026-10-23. | Issue #109 · 2026-02 | |
| Nissan Patrol / Armada Y63 | Requested Cloud | Support PR open for lock, climate and healthSaved copyThe Y63 platform (Nissan Patrol/Armada 2024/2025, EU region) uses high-range feature IDs (835–922) that are unrecognised by the existing `Feature` enum, leaving `self.features` empty and gating all functionality. This PR adds full Y63 support, confirmed working on a 2025 Nissan Patrol Y63 (Saudi Arabia, EU region, `carGateway: AVN`). ### Changes #### Feature detection - Map confirmed Y63 service IDs to existing `Feature` enum values: `866→MY_CAR_FINDER`, `871→LOCK_STATUS_CHECK`, `875→HORN_AND_LIGHTS`, `876→APP_DOOR_LOCKING`, `880→CLIMATE_ON_OFF`, `882→INTERIOR_TEMP_SETTINGS`, … Excerpt saved from GitHub on 2026-10-23. | PR #111 · 2026-06 |
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) | 647 (0.09%) |
|---|---|
| GitHub stars | 105 |
| Latest version | v0.8.2 (2026-10-12) |
| Set up in the UI | Yes |
| Maintainers | @dan-r |
| License | MIT |
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.
