Skip to content

Releases

Train Commute Companion 0.9.0

Choose a tag to compare

@rhnfzl rhnfzl released this 22 Nov 02:57
e5ce474

Train Commute Companion 0.9.0

  • Set a work arrival time and station walk in Telegram setup. Home Assistant previews an arrival-target train using your boarding buffer, required changes, and direct-train preference.
  • Home Assistant uses the confidence and time of activity reports when deciding whether you missed a train.
  • Filter private Today alert history by profile, category, and date.
  • Use /trip reverse NAME to check the opposite direction of a saved route.
  • MCP status gives structured journey details and timetable freshness. Named agents can check any station pair through the same request limit as the other quick-trip tools.

Home Assistant installs the matching train-commute-companion==0.9.0 core. If you use a shared Docker schedule, update the integration and Docker companion to the same release.

v0.8.0

Choose a tag to compare

@rhnfzl rhnfzl released this 21 Nov 23:31
17acc27

What's Changed

  • Manage commute profiles from the Home Assistant integration page by @rhnfzl in #35
  • Offer Dutch commute alerts and publish the setup guide by @rhnfzl in #36
  • Link to the verified public setup guide from the README by @rhnfzl in #37
  • Share one Docker-owned schedule with Home Assistant and MCP agents by @rhnfzl in #38

Full Changelog: v0.6.0...v0.8.0

Train Commute Companion 0.7.0

Choose a tag to compare

@rhnfzl rhnfzl released this 21 Nov 23:35
8510de0
  • Manage individual commutes from the Train Commute Companion integration page in Home Assistant. You can add, edit or remove a commute there. Profiles still use the portable YAML file.
  • Choose Dutch for a profile’s train alerts, reminders and status text. English remains the default.
  • Choose a setup for Home Assistant, Docker and Telegram, or Docker and ntfy. Setup guide

Home Assistant installs the matching 0.7.0 core package with this integration version. Home Assistant setup and upgrades

v0.6.0

Choose a tag to compare

@rhnfzl rhnfzl released this 21 Nov 21:22
da70d03

What's Changed

  • Suggest extra station time for forecast weather by @rhnfzl in #22
  • Let commuters configure how far ahead to check timetables by @rhnfzl in #23
  • Plan one-off and recurring train journeys by @rhnfzl in #24
  • Run personal branch checks locally before the batch PR by @rhnfzl in #25
  • Batch 2 verified changes by @rhnfzl in #26
  • Batch 2 verified changes by @rhnfzl in #27
  • Add recurring schedules and a Home Assistant alert blueprint by @rhnfzl in #28
  • Add local commute statistics and recaps, opt-in sent-alert history, and a token-protected calendar subscription. by @rhnfzl in #29
  • Add quick trip checks, guided Home Assistant profiles, and morning and evening commute checks. by @rhnfzl in #30
  • Remind travellers who are still home or at work when it is time to leave. by @rhnfzl in #31
  • Batch 2 verified changes by @rhnfzl in #32
  • Build a Home Assistant dashboard card for a chosen commute by @rhnfzl in #33
  • Check replacement trains before sending advice, adjust an opt-in wake alert, and share private return estimates by @rhnfzl in #34

Full Changelog: v0.5.0...v0.6.0

0.5.0: easier setup and commute alerts

Choose a tag to compare

@rhnfzl rhnfzl released this 21 Nov 13:44
3ec4d15

Set up saved commutes in Home Assistant or Docker, then receive train, weather and departure advice with your own NS API key.

This release adds guided station selection, Dutch setup forms, private Telegram claim links, reusable private health tokens, configurable delay thresholds and check-in timing, and leave-by advice. Cached station forecasts and optional KNMI warnings add weather context. Saved Home Assistant entity IDs remain unchanged.

Validation: 2,612 core/app tests on the locked runtime and Python 3.12 dependency floors; 482 Home Assistant tests; both type checks; Ruff; Hassfest; HACS; Docker builds; and independent Codex reviews. Windows storage CI passes.

The published 0.5.0 PyPI wheel and source archive have verified hashes and contents. The versioned Docker image supports amd64 and arm64. Live phone delivery, rendered Home Assistant UI and authenticated KNMI retrieval remain unverified.

Setup: Home Assistant, Docker, weather.

0.4.1: clear Telegram button feedback

Choose a tag to compare

@rhnfzl rhnfzl released this 21 Nov 11:03
a358c6f

Telegram buttons now acknowledge the selected action and report its result.

  • Clear completed choices while preserving usable controls on shared messages.
  • Keep failed or refused actions available for retry.
  • Prevent rapid taps from restoring used buttons.
  • Remove recovery controls for the previous step revision.
  • Remember the confirmed delivery-test button after restart.
  • Keep the original controls when the result reply cannot be delivered.

Validation: independent Codex review, passing PR checks, 2,409 core/app tests on locked and minimum dependencies, and 381 Home Assistant tests.

v0.4.0

Choose a tag to compare

@rhnfzl rhnfzl released this 21 Nov 00:23
73a6baf

Easier setup

  • Station names in profiles. Write home_station: Utrecht Centraal instead of UT. An exact code always wins, so existing profiles behave the same. A name that fits more than one station is refused with the matching codes; use the code then. Saving a profile through the Home Assistant editor stores codes.
  • Ready-made Docker image. ghcr.io/rhnfzl/train-commute-companion for linux/amd64 and linux/arm64 (a Raspberry Pi works). The Docker quick start now needs only the compose file, the example profile and a .env; no clone or build. Building from source stays documented.
  • NS API key guide. docs/ns-api-key.md shows how to get a key, with screenshots.
  • README images now show on PyPI and HACS.

Upgrade notes

  • Home Assistant: update through HACS and restart; the matching core installs automatically. Back up first, as always.
  • The CLI station cache now stores names. An older version ignores the new file, and this version ignores the old list-only file; each simply fetches the station list again.
  • Known limit: with a profile that uses station names, a restart while NS is unreachable sends one "profile change refused" notice until NS answers. Profiles that use codes are not affected.

v0.3.0: Window mode, minimum stay and other boarding stations

Choose a tag to compare

@rhnfzl rhnfzl released this 20 Nov 02:16
0a719a2

Window mode. Each direction can be a fixed train, as before, or any train in a time window. Choose how the train is picked: the earliest train with loud missed-train messages (default), the earliest with silent ones, or only when you leave. A minimum stay (for example 8 hours at work) starts the way home at the later of the window start and your arrival plus the stay. Settings can differ per day, weekend days included.

Other boarding station. With location on and no train followed, the companion notices when your phone is near another station. A station you listed or remembered is followed by itself. A new station asks Yes / Other train / No, then whether to remember it. No answer does nothing. Remembered stations live in the companion's state, never in your profile file. New profile keys: other_stations per direction, and under location: other_station_radius_m (default 500), other_station_dwell_min (default 0) and ask_to_remember_station (default true).

New Home Assistant services answer_prompt and forget_station, companion-app action buttons, Docker app buttons and /stations / /forget. All new settings are in the Home Assistant profile editor. The README has new diagrams.

Profiles stay valid, and fixed-train profiles behave as on 0.2.6. Upgrade the integration and its pinned core together and back up the component, profile, state and integration settings first. State saved by 0.3.0 cannot be read by 0.2.6; downgrading requires the pre-upgrade state backup.

Validation: full project CI passes. Local runs pass 2,361 core/app tests and 379 Home Assistant tests, including a fix-by-fix replay of a real evening that boarded at another station.

v0.2.6: Stay quiet about trains you never boarded

Choose a tag to compare

@rhnfzl rhnfzl released this 18 Nov 23:22
bae14d5

A train the companion never saw you board now ends quietly instead of with a loud "I stopped following" message, and the direction stays open: the companion follows again when you reach the boarding station, leave your origin or pick a train.

New optional profile key alerts.quiet_repeat_misses (default off): when on, the 2nd and later missed trains from your origin in the same direction are silent. Off keeps every missed-train message loud.

NS disruption notices now count only when a section covers a stretch of your journey (two stops in a row, or a single named station on the leg); when the train's stops are unknown, any shared station still counts. "minder stoptreinen" is treated as Sprinter-only. Platform-change escalation now uses the same exact expected-departure boundary as the core.

Upgrade the integration and its pinned core together and back up the component, profile, state and integration settings first. State saved by 0.2.6 cannot be read by 0.2.5; downgrading requires the pre-upgrade state backup.

Validation: full project CI passes. Local runs pass 2,198 core/app tests and 361 Home Assistant tests. The 2026-11-18 evening replays without a loud message after the last real miss.

v0.2.5: Decide missed trains from several phone signals

Choose a tag to compare

@rhnfzl rhnfzl released this 17 Nov 23:37
46d57af

A single late phone position near the boarding station no longer counts as a missed train. The companion now combines signals: a leave after departure, a fix at 8 m/s or more, or a fresh Automotive activity means riding; origin Wi-Fi at departure, a fresh Stationary/Walking activity with the phone still in the zone, or the Home Assistant vouch at departure + 12 min proves a miss. Without proof only the silent "has left" hedge is sent and the train stays followed.

New optional profile keys location.wifi and location.activity_entity (source ha). Messages name stations from the NS catalogue instead of raw numeric identifiers.

Upgrade the integration and its pinned core together and back up the component, profile, state and integration settings first. State saved by 0.2.5 cannot be read by 0.2.4; downgrading requires the pre-upgrade state backup.

Validation: full project CI passes. Local runs pass 2,182 core/app tests (also on the Python 3.12 published floors) and 358 Home Assistant tests. The 2026-11-17 evening replays without a false miss.