Data Grand Lyon

The Data Grand Lyon integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] lets you monitor data from the Grand Lyon open data platform (city of Lyon, France).

With this integration, you can:

• Track upcoming departure times at transit stops.
• Monitor real-time bike and dock availability at Vélo’v bike-sharing stations.

Prerequisites

This integration uses data from the Grand Lyon open data platform.

You need an account on data.grandlyon.com. Sign up for a free account if you don’t have one. You can find more information about how to properly create an account and set a password in their documentation (fr).

If you want to monitor transit stops, you also need to request access to the realtime next departures dataset. This is not required for Vélo’v stations.

Configuration

To add the Data Grand Lyon service to your Home Assistant instance, use this My button:

After setting up the integration, you can add transit stops and Vélo’v bike-sharing stations as sub-entries from the integration’s configuration page.

Adding a transit stop

1. Go to Settings > Devices & services and select the Data Grand Lyon integration.
2. Select Add transit stop.
3. Enter the following information:

Adding a Vélo’v station

1. Go to Settings > Devices & services and select the Data Grand Lyon integration.
2. Select Add Vélo’v station.
3. Enter the following information:

Supported functionality

Entities

The Data Grand Lyon integration provides the following entities.

Transit stop sensors

For each transit stop you add, the following sensor entities are created:

• Next departure 1

  • Description: The departure time of the next vehicle at this stop.

• Next departure 1 direction

  • Description: The direction (destination) of the next vehicle at this stop.

• Next departure 1 type

  • Description: Whether the departure time is estimated (based on real-time vehicle tracking) or theoretical (based on the scheduled timetable).

• Next departure 2

  • Description: The departure time of the second vehicle at this stop.

• Next departure 2 direction

  • Description: The direction (destination) of the second vehicle at this stop. Disabled by default.

• Next departure 2 type

  • Description: Whether the departure time is estimated or theoretical. Disabled by default.

• Next departure 3

  • Description: The departure time of the third vehicle at this stop.

• Next departure 3 direction

  • Description: The direction (destination) of the third vehicle at this stop. Disabled by default.

• Next departure 3 type

  • Description: Whether the departure time is estimated or theoretical. Disabled by default.

Vélo’v station binary sensors

For each Vélo’v station you add, the following binary sensor entity is created:

• Station open
  • Description: Whether the Vélo’v station is open. On means the station is open and available for use. Off means the station is closed.

Vélo’v station sensors

For each Vélo’v station you add, the following sensor entities are created:

• Available bikes

  • Description: The total number of bikes currently available at the station.

• Available mechanical bikes

  • Description: The number of mechanical (non-electric) bikes available at the station.

• Available electrical bikes

  • Description: The number of electrical bikes available at the station.

• Available stands

  • Description: The number of free docking stands available at the station.

• Capacity

  • Description: The total number of docking stands at the station. Disabled by default.

• Electrical internal battery bikes

  • Description: The number of electrical bikes with an internal battery available at the station. Disabled by default.

• Electrical removable battery bikes

  • Description: The number of electrical bikes with a removable battery available at the station. Disabled by default.

Examples

Refresh data more frequently during a time window

Get fresher upcoming-departure data before your commute without raising the polling rate the rest of the day. This blueprint refreshes a transit stop’s sensors at a configurable interval inside a time window — by default, every minute between 8:00 and 9:00.

triggers:
  - trigger: time_pattern
    minutes: "/1"
conditions:
  - condition: time
    after: "08:00:00"
    before: "09:00:00"
actions:
  - action: homeassistant.update_entity
    target:
      entity_id: sensor.my_stop_next_departure_1

Data updates

The integration polls data from the Data Grand Lyon API every 5 minutes by default.

Known limitations

• The integration provides up to three upcoming departures per stop. If fewer departures are available, the remaining sensors show as unavailable.
• There is no estimated data for subways, only theoretical.

Troubleshooting

Can’t set up the integration

Symptom: “Invalid authentication”

When trying to set up the integration, the form shows the message “Invalid authentication”.

Description

This means the username or password you entered is incorrect.

Resolution

To resolve this issue, try the following steps:

1. Make sure you are using your data.grandlyon.com credentials.
2. Log in to the Grand Lyon data portal directly to verify your credentials work.
3. If you forgot your password, reset it on the Grand Lyon data portal.

Transit stop shows no data

Make sure the line identifier and stop ID are correct. You can verify these on the Grand Lyon open data platform.

Vélo’v station shows no data

Make sure the station ID is correct. You can verify it on the Grand Lyon open data platform.

Removing the integration

This integration follows standard integration removal.

To remove an integration instance from Home Assistant

1. Go to Settings > Devices & services and select the integration card.
2. From the list of devices, select the integration instance you want to remove.
3. Next to the entry, select the three dots menu. Then, select Delete.