My Rail Commute for Home Assistant (Marketplace integration)

Installs: 73 sharing analytics
GitHub stars: 17
Connection: Uses the vendor's cloud
Upkeep: Updated in the last 6 months
Version: V1.1.9, October 18, 2026
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: my_rail_commute
Source: github.com/adamf83/my-rail-commute
Issues: Report an issue

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

About

My Rail Commute tracks UK rail commutes using National Rail real-time data from the Darwin API. It adds sensors and a binary sensor for each configured commute, covering upcoming trains between two stations, an overall status that moves from normal through minor, major and severe delays to critical when a train is cancelled, and disruption alerts. Multi-leg journeys with interchanges get per-leg sensors and a status for each connection, and an all departures mode follows an origin station with no fixed destination. Favourite departure times can each get their own sensor, and trains can be limited to chosen operators. Delay thresholds are adjustable, and an optional Delay Repay feature tracks claims against operator-specific schemes. Daily statistics include rolling 7-day and 30-day on-time percentages. It needs the vendor's cloud and an API key, and is set up in the UI.

Automatic summary of the README and code of adamf83/my-rail-commute. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

Uses the vendor's cloud Needs an internet connection and an account with the vendor.
From the Marketplace Installed through the Marketplace, formerly HACS.
Actively maintained Its author released or pushed a change in the last six months.

Provides

Sensors

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

My Rail Commute - API Authentication

API Key

Configure Route

Origin Station
Show All Departures (no destination filter)
Destination Station (CRS Code) — leave blank if 'All Departures' is enabled

Add a Connecting Leg

Add a connecting leg
Change At Station (CRS Code)

Trains to Watch

Commute Name
Favourite trains (departure times, comma separated)Optional. Daily departure times from your origin station to keep an eye on, e.g. '07:42, 08:15'. Each gets its own sensor, which stays visible after the train has left. Multi-leg journeys use the first leg only.
Train operators to showOptional. Choose the operators whose trains you want; trains from any others are hidden. Leave empty to show every operator. Applies to every leg of a multi-leg journey.
Number of Services to Track
Time Window (minutes)
Minimum Connection Time (minutes)
Only Show Catchable Services (hide trains you can't make the connection for)

Disruption Alerts

Severe Disruption Threshold (minutes)
Major Delays Threshold (minutes)
Minor Delays Threshold (minutes)
Departed Train Grace Period (minutes)
Enable Night-Time Updates

Delay Repay

Track Delay Repay claims

Delay Repay

Delay Repay thresholds (minutes, comma separated)Delay lengths that qualify for compensation. The usual scheme is 15, 30, 60 and 120. Used for every operator without an override.
Operator overrides (one per line: Operator = 15,30,60 | claim link)Optional. Operators whose scheme differs, e.g. 'Southern = 30,60,120'. Add a claim link after a '|' if you want one stored with the journey. Lines starting with # are ignored.
Days to claim before a journey expires
Arrival Board API key (optional)Needed to confirm the actual arrival time of late trains. This is a separate Rail Data Marketplace product from the departure board: subscribe to 'Live Arrival Board' (free) and paste its key. Without it, journeys stay marked as estimated.
Service Details API key (optional)Lets the integration read a train's actual arrival from its service details. Also a separate Rail Data Marketplace product ('Service Details'). Only asked for once; other commutes reuse it.

Return Journey

Set up return journey

After setup

Favourite trains (departure times, comma separated)Optional. Daily departure times from your origin station to keep an eye on, e.g. '07:42, 08:15'. Each gets its own sensor, which stays visible after the train has left. Multi-leg journeys use the first leg only.
Train operators to showOptional. Choose the operators you want; trains from any others are hidden from this commute's sensors. Leave all unticked to show every operator. Applies to every leg of a multi-leg journey. Operators seen on the live board are added to the list automatically.
Number of Services to Track
Time Window (minutes)
Minimum Connection Time (minutes)
Only Show Catchable Services (hide trains you can't make the connection for)
Severe Disruption Threshold (minutes)
Major Delays Threshold (minutes)
Minor Delays Threshold (minutes)
Departed Train Grace Period (minutes)
Enable Night-Time Updates
Track Delay Repay claims
Delay Repay thresholds (minutes, comma separated)Delay lengths that qualify for compensation. The usual scheme is 15, 30, 60 and 120. Used for every operator without an override.
Operator overrides (one per line: Operator = 15,30,60 | claim link)Optional. Operators whose scheme differs, e.g. 'Southern = 30,60,120'. Add a claim link after a '|' if you want one stored with the journey. Lines starting with # are ignored.
Days to claim before a journey expires
Arrival Board API key (optional)Needed to confirm the actual arrival time of late trains. This is a separate Rail Data Marketplace product from the departure board: subscribe to 'Live Arrival Board' (free) and paste its key. Without it, journeys stay marked as estimated.
Service Details API key (optional)Lets the integration read a train's actual arrival from its service details. Also a separate Rail Data Marketplace product ('Service Details'). Only asked for once; other commutes reuse it.

Texts from the code of adamf83/my-rail-commute.

From the README

A custom Home Assistant integration that tracks regular commutes using National Rail real-time data from the Darwin API. Monitor train services, get disruption alerts, and automate your commuting routine.
Real-time Train Tracking: Monitor upcoming train services between any two UK rail stations
Smart Update Intervals: Automatically adjusts polling frequency based on time of day (peak/off-peak/night)
Disruption Detection: Binary sensor that alerts on cancellations or significant delays
Rich Sensor Data: Comprehensive attributes including platforms, delays, calling points, and more
Multi-Route Support: Configure multiple commutes (e.g., morning and evening journeys)
Multi-Leg Journeys: Track commutes with one or more interchanges, with per-leg sensors and per-connection status (Connection OK, Tight Connection, Delayed Connection, Missed Connection)
All Departures Mode: Optionally track all departures from an origin station with no fixed destination
Historical Performance Tracking: Persistent daily statistics with rolling 7-day and 30-day on-time percentages and average delays
UI Configuration: Easy setup through Home Assistant's config flow interface
HACS Compatible: Simple installation via Home Assistant Community Store
Custom Lovelace Card: Beautiful, dedicated dashboard card for displaying train information

From the README of adamf83/my-rail-commute, MIT License. Shortened.