Renault Picture

Features

• One sensor.<vehicle>_picture per vehicle, attached to the existing Renault device
• The official picture URL as entity_picture (shown as the entity thumbnail) and in attributes
• One image.<vehicle>_picture per vehicle that serves the picture through Home Assistant
• No credentials, no extra API calls: the data comes from the renault integration already running
• Diagnostics with the VIN, account details, tokens and picture URL keys redacted
• English, French, German, Spanish, Serbian (Cyrillic and Latin), Italian, Dutch, Portuguese (European and Brazilian), Polish, Romanian, Danish, Swedish, Bulgarian, Russian, Ukrainian, Hungarian, Slovak, Czech, Slovenian, Latvian and Greek

Supported integrations

The picture is shown by Renault Card, see Use with ha-renault-card.

Prerequisites

• Home Assistant 2025.8 or later
• The core renault integration configured and loaded

Configuration

Settings → Devices & services → Add integration → Renault Picture. There is nothing to fill in; it finds the vehicles from the Renault integration.

Entities#

Two entities per vehicle, attached to the existing Renault device. Both become unavailable while the Renault integration is not loaded (disabled, reloading), so they never show stale data.

Sensor#

Image#

image.<vehicle>_picture serves the large picture from Home Assistant (/api/image_proxy/...): Home Assistant downloads it once and the browser never loads the Renault URL itself. Use it in any card that takes an image entity:

type: picture-entity
entity: image.espace_picture
show_state: false

It is unavailable when the vehicle exposes no picture.

Use with ha-renault-card

ha-renault-card picks the picture up automatically: it finds this integration's sensor on the vehicle's device and uses its picture_large URL. Leave the card's image option empty; set it only to override the MyRenault photo with a plain URL (the option does not render templates):

type: custom:renault-card
image: /local/renault/clio.png

How it works

The core renault integration loads each vehicle's details from Kamereon, which include a PICTURE asset with ONE_MYRENAULT_LARGE and ONE_MYRENAULT_SMALL renditions. This integration reads those straight from the loaded data (entry.runtime_data), so it adds no API calls and needs no credentials. If a future change of the Home Assistant renault integration moves the picture assets, the sensor reports no_picture instead of breaking, and available_renditions shows what the car actually exposes. While no renault entry is loaded with vehicles (startup, reauth, integration removed), the entry shows Retrying setup and Home Assistant retries it on its own.

To report a problem, download the diagnostics from Settings → Devices & services → Renault Picture → ⋮ → Download diagnostics and attach them to the issue. The VIN, account details, tokens and the query strings of picture URLs are redacted; host and path stay readable.

To debug:

logger:
  logs:
    custom_components.renault_picture: debug

Support

If you find this project useful, you can support its development:

Fixes

• Integration icon redrawn in the shared ha-* style (rounded yellow tile, white car glyph, camera badge), with the SVG source and logo.png variants added.

Fixes

• The setup description now mentions the image entity as well as the sensor, in every language.

Features

• Added an image entity per vehicle that serves the MyRenault picture through Home Assistant; the sensor stays.

Fixes

• The entities now become unavailable while the Renault integration is not loaded, instead of keeping stale data.

Features

• Added diagnostics: the VIN, account details, tokens and the query strings of picture URLs are redacted.

Fixes

• The vin attribute is no longer written to the recorder history; it stays available in the live state.
• A sensor whose vehicle has no Renault device is now named "Renault <last 4 VIN characters> Picture" instead of showing the full VIN. Existing entity IDs are unchanged.

Documentation

• README: images and links use absolute URLs, so the screenshots, icons, badges and links display in HACS (relative paths broke there).