From 6d254e1dab2311949b5756f1c82a66d8345c6804 Mon Sep 17 00:00:00 2001 From: Giovanni Condello Date: Sat, 17 Oct 2026 14:50:34 +0200 Subject: [PATCH] docs: document vehicle and charging data availability --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index b12f440..06c2e23 100644 --- a/README.md +++ b/README.md @@ -273,3 +273,17 @@ This device provides visibility into the gateway's status even when no vehicles ### Vehicle devices Each vehicle registered to your account appears as a separate device with sensors for drivetrain, climate, location, and more. + +#### Availability + +Two topics control when vehicle entities show as unavailable. Both publish `online` or `offline`, and both tolerate +short glitches: they switch to `offline` only after 3 consecutive failures, and back to `online` on the next success. + +| Topic | Goes `offline` when | Entities affected | +|------------------------------------------|------------------------------------------------------|-----------------------------------------------------------------------------------------| +| `/available` | 3 consecutive polls of the vehicle API fail | All vehicle entities (unless `HA_SHOW_UNAVAILABLE` is disabled) | +| `/drivetrain/chargingDataAvailable` | 3 consecutive charge status requests fail | Battery Charging, Remaining charging time and Charging finished | + +The charge status request is the one that fails when the car goes into deep sleep right after a charge. The vehicle stays +`online` in that case, so the two topics are separate. Other entities keep their last known value. The **Charging** +switch stays available, so you can still start or stop charging from Home Assistant while the car is asleep.