Renault / Dacia smart home integration, free and open source
Renault and Dacia electric and plug-in hybrid cars: battery, charging, preconditioning.
Published by guim31
- Devices
- Version 1.0.1
- Requires Gladys >=5.1.0
- ★ 0
Follow your Renault and Dacia electric and plug-in hybrid cars in Gladys: battery, range, charging, preconditioning, mileage, and the position if you want it. The integration uses the cloud of the MY Renault / MY Dacia apps, like the official app and the Home Assistant integration.
Not affiliated with Renault or Dacia. Developed without the hardware: feedback welcome.
Requirements
- Gladys 5.1.0 or later.
- A car linked to a MY Renault or MY Dacia account, visible in the official app, with its connected services active: Zoe, Megane E-Tech, Scenic E-Tech, Renault 5, Renault 4, Twingo Electric, Master E-Tech, Dacia Spring, Captur and Megane plug-in hybrids… Hybrid and petrol cars of the account also appear, with what the cloud gives for them (mileage, fuel range).
- The e-mail address and password of the account.
Configuration
In Gladys, Integrations → Renault / Dacia → Configuration:
| Field | What to enter |
|---|---|
| Country of the account | The country and language of your app (e.g. "France — Français"). It decides the servers of the account. |
| E-mail address | The e-mail address of the account. |
| Password | Its password. It is used to sign in only: the session it opens is then kept in the integration's storage. |
| Account (optional) | Empty: the cars of every account of the person. To keep one account, enter the id shown by "Test the connection". |
| Device names language | The language of the feature names (French by default). Gladys keeps a name once the device is created. |
| Refresh | How often the cloud is read: every 10, 15 (default), 30 or 60 minutes. |
| GPS position | Off by default. On: the last position the car sent is read and shown. |
Save, then click Test the connection: it lists the cars of the account, or says in red what is wrong. Then open the Discovery tab and add your cars.
Two-step verification
Some accounts ask for a code sent by e-mail at each new sign-in. The configuration page then shows "Your account asks for a code sent by e-mail":
- click Send the verification code: the result shows the (masked) address it was sent to;
- within a few minutes, click Enter the code and type the code of the e-mail.
The installation is then remembered by the account for about 30 days, and the session is kept: no code is asked at each restart. A wrong code can be typed again; an old one needs a new Send the verification code.
Devices
One device per car, named after the model and the plate (e.g. "Renault Zoe (AB-123-CD)"). Each car gets the features its model offers:
| Feature | Meaning |
|---|---|
| Battery level | State of charge, in %. |
| Range | Electric range estimated by the car, in km. |
| Charging state | Charging, plugged in, waiting for the charger, unplugged (Gladys charging station states). |
| Plugged in | 1 when a cable is connected. |
| Charging | 1 while the car charges. A command on the models whose app can start the charge (and stop it on some). |
| Charging power | In kW, while charging (models that report it). |
| Charging time remaining | In minutes, while charging (models that report it). |
| Battery temperature | In °C (models that report it). |
| Charge mode | Immediate or scheduled charging, a command (models that offer it, e.g. Zoe, Captur and Megane plug-in hybrids). |
| Preconditioning | 1 while the car heats or cools its cabin. A command: on starts it, off stops it. |
| Preconditioning temperature | The temperature sent with the next preconditioning (15 to 25 °C, 21 °C by default), kept by the integration. |
| Outside / inside temperature | In °C (models that report it). |
| Mileage | In km. |
| Fuel range | In km (hybrids). |
| Locked / door or tailgate open | The few models that report their locks (no remote locking: the cloud does not offer it). |
| GPS position | "latitude, longitude", only when the GPS position is on. |
A command accepted by the cloud is not a command carried out by the car. The car does it on its own, often a minute or two later. The integration holds the requested value for up to ten minutes, reads the car again two and six minutes after the command, and then publishes what the car reports. When the car never reports it, the real state comes back and the widget says "Not reported by the car".
Starting a charge on the Renault 5, Renault 4, Scenic E-Tech, Megane E-Tech, Master E-Tech and Alpine A290 turns the charge programs off, as the official app does: switch them on again in the app if you use them. These models cannot stop a charge remotely: stop it from the charger or the car.
Widget
Renault / Dacia car (choose the vehicle in its settings): battery and range, a status list (charge, charge mode, preconditioning, locks, last update) and up to four buttons, labelled with what a tap does now: precondition (asks for confirmation) or stop it, start or stop charging, charge now or use the schedule, refresh. A command shows "Requested, waiting for the car" until the car reports it.
Scene trigger
Charge finished: the car stopped charging while still plugged in (charge complete, or stopped by the car or the charger). Optional filter: the vehicle. Variables: battery level (%) and range (km). A charge stopped from Gladys does not fire it.
Plugged in, unplugged, battery under a threshold: use the device features in a "device state" trigger, they already do it.
Scene actions
- Refresh a Renault / Dacia: reads the state the car last sent to the cloud now (it does not wake the car), and gives the battery level, the range, plugged in and charging to the next actions.
- Precondition a Renault / Dacia: starts the preconditioning at the temperature of the action (15 to 25 °C; empty: the preconditioning temperature of the vehicle). Output: the temperature sent.
The charge (Charging) and the charge mode are device features: a scene sets them with "Control a device".
Scene examples
- Warm car at 7:30 on weekdays: at 7:15, Monday to Friday, "Precondition a Renault / Dacia" at 21 °C.
- Charge during off-peak hours: at 22:00, if Plugged in is 1, set Charge mode to Immediate; at 6:00, set it back to Scheduled. Or with a Tempo/EDF condition: Scheduled on red days.
- Reminder to plug in: at 20:00, "Refresh a Renault / Dacia", then if the battery level output is under 30 and plugged in is false, send a message "Remember to plug the car in".
- Charge finished: send a message "The Zoe is charged ({{triggerEvent.data.battery_level}} %)".
Refresh and cloud quota
The integration reads the cloud on its own timer (it does not rely on Gladys polling). Each read returns the state the car last sent to the cloud: it never wakes the car. A car sends its state when it is switched off, while it charges and after a command; parked and asleep, it may stay hours without news, whatever the refresh chosen.
A read costs one call per endpoint the car offers (battery, mileage, climate, charge mode, locks, position: 1 to 6). Like Home Assistant, the integration stays under 60 calls an hour per account: with several cars, the reads are spaced out beyond the chosen refresh if needed. When the cloud answers "quota reached", the reads pause for 15 minutes. A value that does not change is sent to Gladys again every 12 hours, so it never shows as stale.
Privacy and stored data
- The password stays in the Gladys configuration; it is used to sign in only.
- The session (sign-in token, account id, the identifiers of this installation after a two-step
verification) and the preconditioning temperatures are stored in the integration's
/datavolume, file readable by the integration only. None of it, nor the e-mail address, ever appears in the logs. - The GPS position is off by default; when off, it is never read.
- The integration talks to the Renault cloud only (Gigya for the sign-in, Kamereon for the cars).
Troubleshooting
- "The account refused the sign-in": check the country, the e-mail address and the password (the ones of the app), then save. The integration does not try again on its own, to avoid locking the account.
- "Your account asks for a code sent by e-mail": see Two-step verification.
- "The sign-in service refuses the connection for now": too many attempts; wait a few hours, then save again.
- A car is missing: check that it appears in the official app with the same account and country; with several accounts, empty the Account field.
- A feature is missing: the model does not offer it, or never sent the value. The cloud answers "forbidden" or "not found" for what a model lacks; such an endpoint is no longer read.
- "The privacy mode of the car is on": switch it off in the car.
- Old values: the car has not sent its state since (asleep, no network where it is parked). The "Last update" row of the widget gives the date of the last state.
- More details: set
LOG_LEVEL=debugon the container.
Limits
- Developed without a car or an account, from the protocol and the real answers collected by
renault-api: feedback welcome on the forum or in the issues. - No remote lock, horn or lights: the cloud does not offer locking, and horn and lights were left out (a dashboard button is easy to press by mistake).
- No charge schedule editing, no charge limit, no charge history.
- The commands go through the Renault cloud: when it is down, nothing works, and it may change without notice.
- The position is published as text; no distance from home.
Credits
The protocol, the per-model endpoint table and the test fixtures come from
hacf-fr/renault-api (MIT), the library of the Home
Assistant renault integration, whose behaviour (quota, endpoints refused per model) was followed.
Configuration settings
These are the settings Renault / Dacia asks for in its configuration screen in Gladys.
| Setting | Type | Required | Description |
|---|---|---|---|
| Before you start | section | No | This integration signs in to your MY Renault or MY Dacia account, like the official app, and reads the state your cars last sent to the cloud (it never wakes them). If your account asks for a code sent by e-mail: save, click “Send the verification code”, then “Enter the code”. Not affiliated with Renault or Dacia. |
| Country of the account | select | Yes | The country and language of your MY Renault / MY Dacia app: they decide the servers of the account. |
| E-mail address | string | Yes | The e-mail address of your MY Renault or MY Dacia account. |
| Password | secret | Yes | Used to sign in only: the session it opens is then kept in the integration's storage. |
| Account (optional) | string | No | Empty: the cars of every account of the person. To keep one account, enter the id shown by “Test the connection”. |
| Device names language | select | No | Language of the feature names given to new devices (Gladys keeps a name once the device is created). |
| Refresh | select | No | How often the cloud is read. It never wakes the car; several cars stretch it to stay within the cloud quota. |
| GPS position | boolean | No | Off by default (privacy). On: the last position the car sent is read and shown in Gladys. |
How to install Renault / Dacia in Gladys
- In Gladys, open Integrations: Renault / Dacia appears in the catalog, next to the native integrations, with a community badge.
- Click Install. Gladys pulls the Docker image (
ghcr.io/guim31/gladys-renault:1.0.1), starts it in a sandbox isolated from the core, and generates the integration's interface (devices, discovery and configuration). - Open the Configuration screen of the integration, fill in the settings, and save.
- You can also install it directly from its repository URL: https://github.com/guim31/gladys-renault.
Renault / Dacia requires Gladys >=5.1.0. The catalog inside Gladys refreshes every hour, so a new version becomes available at most one hour after its release.
Not running Gladys yet? It is free and open source: follow the installation guide to get started.
About external integrations
Renault / Dacia is an external integration: a community integration packaged as a Docker container and published on GitHub, that Gladys installs in one click and runs in a sandbox isolated from its core. It is published and maintained by guim31, not by the Gladys core team.
- Browse all external integrations
- Discover the native integrations built into Gladys
- Build and publish your own external integration
- Source code on GitHub — source of this documentation