--- title: "db-infoscreen" description: "db-infoscreen is a Marketplace integration for Home Assistant. It has 491 installs sharing analytics, needs the vendor's cloud and was last updated October 27, 2026." canonical: "https://vulpo.app/integrations/marketplace/faserf-ha-db-infoscreen" url: "https://vulpo.app/integrations/marketplace/faserf-ha-db-infoscreen.md" last-updated: "2026-10-22" version: "1.4" --- # db-infoscreen > db-infoscreen is a Marketplace integration for Home Assistant. It has 491 installs sharing analytics, needs the vendor's cloud and was last updated October 27, 2026. db-infoscreen is a departure board integration that shows train departures for a chosen station in Home Assistant. It gathers data from several sources, mainly Deutsche Bahn IRIS-TTS, through a backend that can be the public service or a self-hosted one, and it covers stations in Germany and Europe. It adds sensors, binary sensors and a departures calendar, covering delay, cancellation, connection status, a leave-now alarm, station punctuality and a trip watchdog. Actions can watch a specific train, track a connecting train at a transfer station, refresh departures, set a temporary time offset and pause updates. Filters cover platforms, via stations, directions, train types and cancelled trains, and display options include a simplified text view and arrival or departure mode. Setup runs in the UI, and a backend add-on can be found automatically on the network. Automatic summary of the README and code of FaserF/ha-db\_infoscreen. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=FaserF&repository=ha-db_infoscreen&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=FaserF&repository=ha-db_infoscreen&category=integration) ## Supports - **Uses the vendor's cloud**: Needs an internet connection and an account with the vendor. - **Found by itself**: Home Assistant spots it on the network and offers to add it. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Select Server - **Server Type** - **Server URL/IP (e.g. http://192.168.1.50:8092 or Home Assistant Add-on URL http://127.0.0.1:8092)** ### Find your Station - **Station Name** - **Data Source (Standard used for trains)** ### Select Station - **Station** - **← Back (Change Search / Data Source)** ### Configure Departure Board - **Number of Upcoming Departures to show** - **Update Interval (minutes)** - **Walk Time to Station (minutes)** - **Show Advanced Options (Filter Settings / Special Handling)** - **Pause periodic updates (Stop data fetching)** ### Advanced Configuration - **Hide Low Delays (under 5 mins)** - **Remove trains that are already gone** - **Filter out duplicate entries** - **Show Detailed Information** - **Include departures from the last 60 minutes** - **Keep full route details (intermediate stops)** - **Keep departure even if this is the end station** - **Data Source (Backend)** - **Time Offset (HH:MM)** - **Display Mode (Arrival vs Departure)** - **Filter by Platforms (comma separated, e.g. 1, 2, 5-7)** - **Filter by Via Stations (comma separated)** - **Via Station Search Logic (AND = all must match, OR = at least one)** - **Filter by Final Destination** - **Exclude Final Destinations** ### Configure Custom Station - **Data Source (Required)** - **Number of Upcoming Departures** - **Update Interval (minutes)** - **Filter by Platforms** - **Filter by Via Stations** - **Via Station Search Logic** ### Reconfigure Departure Board - **Station Name / ID** - **Server Type** - **Server URL/IP** - **Data Source** ### After setup - **Station Name / ID** - **Data Source** - **Number of Upcoming Departures** - **Via Stations (comma separated)** - **Direction** - **Platforms (comma separated)** - **Number of Upcoming Departures** - **Update Interval (minutes)** - **Cache TTL (seconds)** - **Offset (HH:MM)** - **Walk Time to Station (minutes)** - **Pause periodic updates (Stop data fetching)** - **Calendar Event Duration (minutes)** - **Calendar: Only include favorite trains** - **Calendar: Only include delayed trains** - **Server Type** - **Server URL** - **Platforms** - **Via Stations** - **Via Station Search Logic** - **Direction** - **Excluded Directions** - **Ignored Train Types** - **Exclude Cancelled Trains** - **Multiple Favorite Trains (comma separated e.g. 'ICE 1, RE 2')** - **Detailed Information** - **Enable Simplified Text View** - **Template for Simplified Text View** - **Display Mode** - **Hide Low Delay** - **Show Occupancy Information** - **Deduplicate Departures** - **Keep Route Details** - **Keep Endstation** - **Drop Late Trains** - **Include Past 60 Minutes** - **Data Source** - **Custom Deduplication Key (e.g. ｛line｝ - Leave empty for default: ｛journeyID｝｛journeyId｝｛id｝｛key｝｛trainNumber｝)** - **Maximum JSON Size (Bytes)** Texts from the code of [FaserF/ha-db\_infoscreen](https://github.com/FaserF/ha-db_infoscreen). ## Entities - **Binary sensors**: Delay, Cancellation, API Connection, Update Status, Station Accessibility, Connection Status - **Calendars**: Departures - **Sensors**: Departures, Leave Now Alarm, Station Punctuality, Trip Watchdog ## Actions - **Watch Train**: Registers a background task to monitor a specific train departure from a station. Fields: Train ID, Notify Service, Delay Threshold, Notify on Platform Change, Notify on Cancellation - **Track Connection**: Monitors a connecting train at a transfer station. Fields: Current Train ID, Change Station, Next Train ID - **Refresh Departures**: Triggers a manual refresh of train departures for all configured stations. - **Set Offset**: Dynamically overrides the default time offset for departures temporarily. Fields: Offset, Station - **Set Paused State**: Enables or disables periodic data fetching for a specific station or all stations. Fields: Paused, Station ## Troubleshooting - **Repair notices**: Notices it can show in Settings, Repairs: Station data is stale, API error for station, API error for station (Via route configured), Station may no longer be supported, Connection error ## From the README > A comprehensive departure board integration for Home Assistant. From the README of [FaserF/ha-db\_infoscreen](https://github.com/FaserF/ha-db_infoscreen#readme), [GNU AGPL v3.0](https://spdx.org/licenses/AGPL-3.0.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Productivity and information](https://vulpo.app/integrations/category/productivity-and-information.md), Calendars and to-dos - Number: 491 installs sharing analytics; 96 GitHub stars - Connection: Needs the vendor's cloud - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v2026.10.0, last updated October 27, 2026 - Domain: `db_infoscreen` - Source: - Issues: - Screenshot: https://vulpo.app/integrations-img/35ea8e13bbd81b25.webp (from FaserF/ha-db\_infoscreen's README) In Vulpo: Calendar card, Chart card, Apple Watch Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-22. Source: https://vulpo.app/integrations/marketplace/faserf-ha-db-infoscreen --- - HTML version of this page: https://vulpo.app/integrations/marketplace/faserf-ha-db-infoscreen - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml