--- title: "Toyota EU community integration" description: "Toyota EU community integration is a Marketplace integration for Home Assistant. It has 1.5k installs sharing analytics, needs the vendor's cloud and was last updated October 26, 2026." canonical: "https://vulpo.app/integrations/marketplace/pytoyoda-ha-toyota" url: "https://vulpo.app/integrations/marketplace/pytoyoda-ha-toyota.md" last-updated: "2026-10-22" version: "1.4" --- # Toyota EU community integration > Toyota EU community integration is a Marketplace integration for Home Assistant. It has 1.5k installs sharing analytics, needs the vendor's cloud and was last updated October 26, 2026. Toyota EU community integration connects Home Assistant to Toyota Connected Services Europe through the vendor's cloud. It adds sensors for odometer, fuel, battery, range and charging status, plus binary sensors for doors, windows, hood and lock state. Remote control covers door lock and unlock, climate start and stop with target temperature, defrosters, seat heater levels, the steering wheel heater and hazard lights. A parking location entity and a recent trips sensor with route data are included, and buttons trigger a manual status refresh or sound the buzzer. Status refresh can wake the vehicle on demand or after it has just stopped, so lock and door state does not stay stale. Options cover the polling interval, keeping last good data during temporary API failures, and diagnostic sensors for fetch health; setup is done in the UI with Toyota account details. Automatic summary of the README and code of pytoyoda/ha\_toyota. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=pytoyoda&repository=ha_toyota&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=pytoyoda&repository=ha_toyota&category=integration) ## Supports - **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Connect - **Vehicle Brand** - **Email** - **Password** - **Use metric units (e.g. km instead of miles)** ### After setup - **Polling interval (minutes)**: How often the integration polls Toyota for fresh data (0-1440 minutes; default 6; 0 = disable automatic polling, use the manual refresh services/buttons only). Lower values may hit rate limits. - **Retain last good data on transient failures (recommended)**: When enabled, a temporary Toyota API failure (HTTP 429, timeout, connection error) keeps the last successful per-vehicle data in place instead of marking every Toyota entity as unavailable. The new 'Last successful fetch', 'Last error' and 'Last error code' diagnostic sensors show the true state of the integration. - **Refresh vehicle status remotely (recommended)**: Toyota's API gateway often returns stuck-stale lock and door state unless the car's modem is woken explicitly. When enabled, the integration sends a wake request before reading status, mimicking the Toyota mobile app. Each wake uses a small amount of cellular airtime and 12V battery; the smart triggers (just-stopped detection, optional idle wake) keep the cost low. Disable for vehicles whose Toyota account does not support refresh-status; the integration auto-disables this for you if it detects unsupported responses. Note: this scope is only the /v1/global/remote/status endpoint (door, window, lock and hood state); other data (odometer, fuel, location, etc.) is fetched every cycle regardless. When this option is OFF, the four options below (idle wake, failed-wake threshold, status cache age, wake POSTs per stop) have no effect. Manual refreshes (the toyota.refresh\_vehicle\_status service or the refresh button) bypass this toggle and any auto-disable, and a successful manual wake re-enables the automatic strategy. - **Wake idle vehicle every N hours (0 = disabled)**: Wake the car periodically even if it has not moved. Useful for cars that sit unused for days where you still want fresh lock state. 0 (default) disables this entirely; 1-72 = wake every N hours. Each wake costs cellular airtime and a small amount of 12 V battery. Note: the wake only refreshes the /v1/global/remote/status endpoint (door, window, lock and hood state). Other data (odometer, fuel, location, etc.) is fetched on every cycle independently and does not need a wake. - **Mark unreachable after N failed wakes**: If a vehicle stops responding to wake requests this many times in a row, it is marked unreachable per-VIN until it shows any sign of life (driving event, external app refresh, manual service call). Default 3. - **Refresh status cache if older**: Maximum acceptable age of the cached status data before issuing a fresh GET (5-180 minutes; default 30). Note: this controls only the /v1/global/remote/status endpoint, which carries door, window, lock and hood state. Other data (odometer, fuel, location, etc.) is fetched on every cycle independently. - **Wake POSTs per stop event**: How many wake POSTs to fire when the vehicle is detected as just-stopped, one per coordinator cycle. 1 = single POST. 2 (default) = an additional POST on the next cycle, which typically catches state the user changes shortly after stopping (locking the doors, opening the trunk, etc.) - those events trigger fresh modem reports that the second POST's poll loop picks up. Higher values rarely help and burn 12 V battery. - **Recent trips to keep in cache (0 = disabled)**: Populates a per-vehicle 'Recent trips' sensor with the last N trips (route waypoints + per-trip stats), suitable for journey-viewer custom cards. 0 (default) disables auto-fetch entirely (no extra API calls). 1-20 enables auto-fetch on stop events; the cache survives HA restart. The toyota.refresh\_recent\_trips service and the per-vehicle 'Refresh recent trips' button work regardless of this setting, so you can keep auto-fetch off and drive fetches via daily automations. Texts from the code of [pytoyoda/ha\_toyota](https://github.com/pytoyoda/ha_toyota). ## Entities - **Binary sensors**: Over all status, Hood, Key in car, Front defogger, Rear defogger, Driverseat window, Passengerseat window, Leftrearseat window, Rightrearseat window, Driverseat door, Driverseat lock, Passengerseat door, and 12 more - **Buttons**: Refresh vehicle status, Refresh recent trips, Refresh electric realtime status, Sound buzzer - **Presence**: Parking location - **Locks**: Door lock - **Selects**: Driver seat heater, Passenger seat heater, Rear driver seat heater, Rear passenger seat heater - **Sensors**: Vehicle-Identify-Number, Recent trips, Odometer, Fuel level, Fuel range, Battery level, Usable battery level, Battery range with AC, Battery range, Total range, Charging status, Remaining charging time, and 16 more - **Switches**: Steering wheel heater, Hazard lights ## Troubleshooting - **Diagnostics**: Downloads a diagnostics file to attach to a bug report. ## From the README > - VIN (Vehicle Identification Number) sensor > - Fuel, battery and odometer information > - Current day, week, month and year statistics. > - Door and door lock sensors, including hood and trunk sensor. > - Remote door lock/unlock. > - Remote climate control (start/stop, target temperature, front/rear defrost, seat-heater levels, steering-wheel heater). > - Recent trips (rolling per-vehicle cache with route data). > - Diagnostic sensors for fetch health and cache freshness. > - Smart status refresh: wake the vehicle on demand or automatically when it has just stopped, mimicking the Toyota app's two-stage protocol so that lock/door/window/hood state reflects reality instead… > - Per-vehicle button to trigger a manual wake from the dashboard, plus a toyota.refresh\_vehicle\_status service for use in automations. From the README of [pytoyoda/ha\_toyota](https://github.com/pytoyoda/ha_toyota#readme), [MIT License](https://spdx.org/licenses/MIT.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Vehicles and transport](https://vulpo.app/integrations/category/vehicles-and-transport.md), Cars and EVs - Brand: [Toyota](https://vulpo.app/integrations/toyota.md) - Number: 1.5k installs sharing analytics; 172 GitHub stars - Connection: Needs the vendor's cloud - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v3.3.0, last updated October 26, 2026 - Domain: `toyota` - Source: - Issues: In Vulpo: Quick Toggle card, Climate card, Lock card, Button card, Apple Watch, Control Center, Climate Live Activity (Pro) [Widgets & Live Activities in Vulpo](https://vulpo.app/features/widgets-and-live-activities) ## Other ways in for Toyota | Name | Kind | Installs or stars | Connection | Upkeep | | --- | --- | --- | --- | --- | | [Toyota (North America)](https://vulpo.app/integrations/marketplace/widewing-ha-toyota-na.md) | Marketplace integration | 711 installs sharing analytics | Needs the vendor's cloud | Updated in the last 6 months | | [Toyota LATAM](https://github.com/xnetinho/ha-toyota-latam) | Marketplace integration | No installs sharing analytics yet | Needs the vendor's cloud | Updated in the last 6 months | | [Toyota Connected Services](https://github.com/DurgNomis-drol/ha_toyota) | Marketplace integration | Installs not shown: shared domain toyota | Needs the vendor's cloud | Removed from the Marketplace: Repository has been abandoned | Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/pytoyoda-ha-toyota --- - HTML version of this page: https://vulpo.app/integrations/marketplace/pytoyoda-ha-toyota - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml