GTFS Realtime for Home Assistant (Marketplace integration)

Installs: 105 sharing analytics
GitHub stars: 37
Connection: Uses the vendor's cloud
Upkeep: Updated in the last 6 months
Version: 0.4.10, October 24, 2026
Category: Vehicles and transport, Public transport
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: gtfs_realtime
Source: github.com/bcpearce/homeassistant-gtfs-realtime
Issues: Report an issue

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

Screenshots From the README of bcpearce/homeassistant-gtfs-realtime.

About

GTFS Realtime is an integration that adds public transit arrivals and service alerts to Home Assistant. It reads realtime and static GTFS feeds from a transit provider, and the static schedule data is merged in to supply details such as destination headsigns and route IDs. Sensors for a chosen stop report the first, second, third and later arrivals in order of shortest time, and a binary sensor and a button for clearing schedule data are also provided. Some providers are preconfigured, an API key can be sent as a request header, and route icons can be loaded from a custom URL. A Generate Arrival Board action builds a tile dashboard for a stop, and experimental vehicle position data can appear on map cards. It is added through the Home Assistant interface and relies on the provider's cloud feeds.

Automatic summary of the README and code of bcpearce/homeassistant-gtfs-realtime. 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.

Select a GTFS Provider

GTFS Provider

Select Route and Stop IDs to create sensor and binary sensor entities.

Arrival Limit
GTFS Provider Name
Route IDRoute ID for a GTFS entity to receive service alerts.
Stop IDStop ID for a GTFS entity to receive arrival data and service alerts

Select GTFS Realtime and Static Feed URLs.

Authorization header (if required)Must be in the form '[Authorization Type]: [authorization string]'. For example, this could be 'X-Api-Key: [the api key]' or 'Authorization: apikey [the api key]'. Not all auth types are supported.
GTFS Static Feeds (file or URL)GTFS static feed zip file. Include the URL(s) for static schedule data. Note this is required to merge trip and stop info with realtime data.
Route Icons format URLURL to a route-icons provider containing an svg image file for a given route. The string can contain up to 3 str.format() compatible formatters for [route_id], [route_color], and [route_text_color] respectively. If your provider gives these colors as HTML hex, you may need to add an html-escaped '#' preceeding the input.
Feed URLFeed URLs for realtime GTFS Data