Get Full Departures List Action

[Jawar19]

Integration name

rejseplanen

Link to integration documentation on our website

https://www.home-assistant.io/integrations/rejseplanen/

Describe the enhancement

Feature: Get Full Departures List Action

Add a service/action rejseplanen.get_departures that returns a complete list of all upcoming departures for a specified stop, including all available attributes and details. This action would provide the rich departure data needed by custom cards and advanced automations.

This feature request is based loosely on the archived custom card by @Darkfox

Action Response

The action should return a data structure containing:

{
  "departures": [
    {
      "line": "1A",
      "direction": "Nørrebro",
      "type": "BUS",
      "scheduled_time": "2025-12-07T08:15:00+01:00",
      "realtime_time": "2025-12-07T08:18:00+01:00",
      "delay_minutes": 3,
      "track": "2",
      "is_delayed": true,
      "is_cancelled": false,
      "operator": "Movia",
      "stop_id": "8600617",
      "stop_name": "Roskilde St.",
      "final_stop": "Nørrebro Station"
    },
    {
      "line": "2B",
      "direction": "Sydhavn",
      "type": "BUS",
      "scheduled_time": "2025-12-07T08:25:00+01:00",
      "realtime_time": "2025-12-07T08:25:00+01:00",
      "delay_minutes": 0,
      "track": null,
      "is_delayed": false,
      "is_cancelled": false,
      "operator": "Movia",
      "stop_id": "8600617",
      "stop_name": "Roskilde St.",
      "final_stop": "Sydhavn"
    }
  ],
  "stop_id": "8600617",
  "stop_name": "Roskilde St.",
  "fetched_at": "2025-12-07T08:10:30+01:00",
  "total_departures": 15
}

Parameters

• device_id (required): The device ID of the stop to retrieve departures for
• direction_filter (optional): Only return departures to specific destinations (string or list of strings)
• line_filter (optional): Only return specific line numbers (string or list of strings)
• type_filter (optional): Only return specific transport types (BUS, TRAIN, METRO, etc.)
• max_results (optional): Limit the number of results (default: 10, max: 50)

Use cases

The current sensor entities only display the next single departure, limiting the ability to create rich, information-dense transit dashboards. Many users and custom card developers (like rejseplanen-card) need access to multiple upcoming departures with complete attribute information.

Specific use cases:

1. Custom card integration: Developers can use the action response to populate custom Lovelace cards that display multiple departures with detailed information, real-time delays, and visual indicators for cancelled or delayed services.

2. Smart departure alerts: Automations can trigger the action and analyze the full departure list to send intelligent notifications:

   • Alert if all next 3 departures are delayed by >10 minutes
   • Notify only if there's a delay-free option within the next 30 minutes
   • Suggest alternative routes based on delay patterns

3. Dashboard templates: Create template sensors or templates that extract specific information from the departure list:

   • Display the earliest on-time departure
   • Show average delay for the hour
   • List all cancelled departures

4. Cross-stop comparison: Users planning trips can call the action for multiple stops and compare options:

   • Which station has the soonest departure?
   • Which route has the least delays today?

Example automation using the action:

automation:  - alias: "Get next 5 departures and show on dashboard"
    trigger:
      - platform: state
        entity_id: input_button.refresh_departures
    action:
      -  action: rejseplanen.get_departures
          target:
              device_id: !secret my_station_device_id
          data:
              max_results: 5
          response_variable: departure_data
      -  action: input_text.set_value
          target:
              entity_id: input_text.departures_json
          data:
              value: "{{ departure_data.departures | tojson }}"

Example custom card usage:
Custom card developers can use this in their Lovelace YAML:

type: custom:rejseplanen-card
device_id: !secret my_station_device_id
action_name: rejseplanen.get_departures
max_departures: 10
show_delays: true
show_cancellations: true

This approach provides complete flexibility for advanced users and developers while maintaining clean, standards-compliant sensor entities for basic use cases. The action-based design prevents sensor entity bloat while enabling sophisticated transit planning integrations.

Anything else?

No response

[github-actions[bot]]

🏷️ I've automatically added the integration: rejseplanen label to help categorize this feature request.