Transport NSW Mk II for Home Assistant (Marketplace integration)

Installs: 69 sharing analytics
GitHub stars: 25
Connection: Uses the vendor's cloud
Upkeep: Updated in the last 6 months
Version: 3.1.2, September 18, 2026
Category: Vehicles and transport, Public transport
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: ha_transportnsw
Source: github.com/andystewart999/ha_transportnsw
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 andystewart999/ha_transportnsw.

About

Transport NSW Mk II is an integration that provides real-time Transport NSW journey information in Home Assistant. Each journey is its own subentry, with an origin and one or more destinations given as stop IDs or location names, and the origin can also be a device tracker. Journeys can be filtered by transport type for the first and last legs, by number of changes, by minimum time until departure, and by line name text. A journey can create up to three trips, and updates can be limited to set time periods to reduce API usage. The default sensor shows minutes until departure, and further sensors and an alerts sensor can be selected. It needs a Transport NSW API key and the vendor's cloud, and it is set up in the UI.

Automatic summary of the README and code of andystewart999/ha_transportnsw. 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
Presence

Setting it up

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

Connect

Your Transport NSW API key

After setup

Sensor update interval (s)The sensor update interval in seconds. 0 means the update interval will be calculated based on the API calls used per update and how many API calls remain from the daily limit.
Available daily API allocation (%)
Device tracker location update at each pollIf the journey origin is a device tracker (e.g. a mobile phone), attempt to request a location update at each poll. Note that this could impact the battery life of the device being polled.

Texts from the code of andystewart999/ha_transportnsw.