ha-db_infoscreen

KO | EN

gitlite — search

#python #react #ai #go #golang #machine-learning #deep-learning #windows #cli #vue #pytorch #security #mcp #openai

ha-db_infoscreen

(★ 95)

db-infoscreen Homeassistant fetching (superior of ha-deutschebahn)

ha-db_infoscreen 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<div align="center">
  <img src="docs/images/logo.png" alt="Logo" width="200px">
  <h1>DB-Infoscreen for Home Assistant 🚆</h1>
  <p><strong>A comprehensive departure board integration for Home Assistant.</strong></p>

[![HACS Default](https://img.shields.io/badge/HACS-Default-41BDF5.svg?style=for-the-badge)](https://github.com/hacs/integration)
[![Downloads (Current release)](https://img.shields.io/github/downloads/FaserF/ha-db_infoscreen/latest/db_infoscreen.zip?label=Downloads%20(Current%20release)&style=for-the-badge)](https://github.com/FaserF/ha-db_infoscreen/releases)
  [![GitHub Release](https://img.shields.io/github/v/release/FaserF/ha-db_infoscreen?style=for-the-badge)](https://github.com/FaserF/ha-db_infoscreen/releases)
  [![License](https://img.shields.io/github/license/FaserF/ha-db_infoscreen?style=for-the-badge)](https://raw.githubusercontent.com/FaserF/ha-db_infoscreen/main/LICENSE)
</div>

---

## ❤️ Support This Project

> I maintain this integration in my **free time alongside my regular job** — bug hunting, new features, and testing on real hardware. Test devices cost money, and every donation helps me stay independent and free up more time for open-source work.
>
> Donations are completely voluntary — but the more support I receive, the less I depend on other income sources and the more time I can realistically invest into these GitHub projects. 💪

[![GitHub Sponsors](https://img.shields.io/badge/Sponsor%20on-GitHub-%23EA4AAA?style=for-the-badge&logo=github-sponsors&logoColor=white)](https://github.com/sponsors/FaserF)&nbsp;&nbsp;
[![PayPal](https://img.shields.io/badge/Donate%20via-PayPal-%2300457C?style=for-the-badge&logo=paypal&logoColor=white)](https://paypal.me/FaserF)

</div>

---

The `db-infoscreen` integration provides detailed **departure times** and train information for a given station directly in Home Assistant. Aggregating data from multiple sources (primarily **Deutsche Bahn IRIS-TTS**), it offers a powerful and comprehensive departure board for stations across Germany and Europe.

📚 **[View the Full Documentation](https://faserf.github.io/ha-db_infoscreen/)**

## 🐳 Self-Hosting the DBF Backend

For a reliable and unrestricted setup, it is highly recommended to host your own **DBF (DB-Fahrplan / db-fakedisplay)** backend API.

### Why Self-Host?
* **No Sensor Limits**: Bypasses the default **30-sensor limit** enforced on the public API to protect public infrastructure.
* **No Rate Limits or IP Bans**: Avoids the strict public API rate limits (30 requests/min total, 1 request/station/min).
* **Improved Performance**: Faster updates as queries stay on your local network.

### Hosting Options
* **Home Assistant Add-on**: [DBF Add-on Repository](https://github.com/FaserF/hassio-addons/tree/master/dbf) – simple one-click install for Home Assistant OS.
* **Docker Container**: [derf/db-fakedisplay](https://github.com/derf/db-fakedisplay) – run via Docker on Unraid, Synology, or any container host: `docker run -d -p 8092:8092 derf/db-fakedisplay:latest`.

### Data Sources & Rate Limits
Even when self-hosted, the backend fetches real-time train data directly from official APIs (like Deutsche Bahn IRIS-TTS and local transit HAFAS endpoints). Because these endpoints are designed to scale, a private home instance querying every few minutes will not trigger upstream rate limits or bans.

For detailed setup instructions, see the **[Self-Hosting Documentation](https://faserf.github.io/ha-db_infoscreen/self-hosting/)**.

## ✨ Features

| Feature | Description |
| :--- | :--- |
| 📋 **Departure Board** | View next departures, delays, platforms, and train types. |
| 👥 **Train Occupancy** | View predicted load factor (1st/2nd class) where available. |
| 🌍 **Wide Coverage** | Supports DB and many local transport associations (via HAFAS/EFA). |
| ⚙️ **Highly Configurable** | Filter by direction, train type, specific platforms, and more. |
| 💖 **Favorite Trains** | Filter for specific "Favorite Trains" (Commuter Profile). |
| ⏸️ **Pause Updates** | Stop periodic data fetches to save API queries. Includes `is_paused` attribute and binary sensor for UI logic. |
| 🔍 **Diagnostic Sensors** | Monitor API connection, update status, and station accessibility (elevators). |
| ℹ️ **Detailed Attributes** | Access route info, warnings, platform changes (`changed_platform`), wagon order (`wagon_order`), wagon order summary (`wagon_order_html`), sector info (`platform_sectors`), facilities (`facilities`), real-time route progress (`route_details`), and unique trip ID (`trip_id`). |

---

## 🛠️ Installation

### 1. Using HACS (Recommended)

This integration is available as a default repository in HACS.

1.  Open **HACS**.
2.  Search for `db-infoscreen`.
3.  Click **Download**.
4.  Restart Home Assistant.

[![Open HACS](https://my.home-assistant.io/badges/hacs_repository.svg)](https://my.home-assistant.io/redirect/hacs_repository/?owner=FaserF&repository=ha-db_infoscreen&category=integration)

> [!TIP]
> HACS ensures you stay up-to-date with the latest API changes and bug fixes.

### 2. Manual Installation

1.  Download the latest [Release](https://github.com/FaserF/ha-db_infoscreen/releases/latest).
2.  Extract the ZIP file.
3.  Copy the `db_infoscreen` folder into your `<config>/custom_components/` directory.
4.  Restart Home Assistant.

---

## ⚙️ Configuration

### 🔍 Auto-Discovery (Zeroconf / mDNS & Supervisor)
- **Automatic Detection**: When running the official DBF Add-on (with `host_network: true`), Home Assistant will **automatically discover** the instance via Zeroconf (`_ha-db_infoscreen._tcp.local.`) and display a discovery notification in **Settings ➔ Devices & Services**.
- **Supervisor Integration**: If discovered or added manually on a Home Assistant OS / Supervised system, the integration automatically pre-fills the local Add-on URL (`http://<host>:8092`).

### ✍️ Manual Setup

1.  Go to **Settings** -> **Devices & Services**.
2.  Click **Add Integration**.
3.  Search for **DB Infoscreen**.

[![Add Integration](https://my.home-assistant.io/badges/config_flow_start.svg)](https://my.home-assistant.io/redirect/config_flow_start/?domain=db_infoscreen)

### Configuration Options

**Initial Setup**:
When adding the integration, you will be asked for the most important settings:

**Options Menu (Configure)**:
All other settings are available via the **Configure** button on the integration entry. They are grouped into:

*   **General**: Update Interval, Offset, Count.
*   **Filter**: Directions, Train Types (e.g. ICE), Exclusions.
*   **Display**: Text View, Mode (Departure/Arrival), Detailed Info.
*   **Advanced**: Custom API URL, Deduplication, Route Details.

#### Full Options List

| Option | Default | Description |
| :--- | :--- | :--- |
| `update_interval` | `3` | Fetch interval in minutes. **Minimum: 1 minute**. |
| `hide_low_delay` | `False` | Hide departures with < 5 min delay. |
| `drop_late_trains` | `False` | Hide past departures even if they are delayed. |
| `deduplicate_departures` | `False` | Filter out duplicate entries. |
| `detailed` | `False` | Show extra attributes (messages, ids, keys, wagon order, etc.). |
| `past_60_minutes` | `False` | Show departures from the past 60 minutes. |
| `keep_route` | `False` | Keep full route (stopover) details in attributes. |
| `keep_endstation` | `False` | Keep departure if station is also the endstation. |
| `custom_api_url` | - | Use a private/custom API instance. |
| `offset` | `00:00` | Time offset for search (HH:MM or HH:MM:SS). |
| `admode` | `departure` | Display departure or arrival times. |
| `paused` | `False` | Pause periodic updates (Stop data fetching). |
| `excluded_directions` | - | Exclude departures with specific direction (substring match). |
| `ignored_train_types` | `[]` | List of train types to ignore. |
| `enable_text_view` | `False` | Enable simplified text view for ePaper displays. |
| `text_view_template` | (Default) | Template for the simplified text view (e.g., `{line};{destination};{platform};{time}`). |
| `deduplicate_key` | (Default) | Template for the unique trip identifier used for deduplication. Default: `{journeyID}{journeyId}{id}{key}{trainNumber}`. |

> [!TIP]
> **Deduplication for KVV**
> If you are using Karlsruher Verkehrsverbund (KVV) and see duplicate entries for different platforms, try setting the `deduplicate_key` to `{line}` or `{key}`. The default key may be too specific because the KVV API includes the scheduled time in the trip ID.

> [!WARNING]
> **Limitations & Performance**
> *   **Sensor Limit**: You are limited to **30 sensors** unless using a custom_api_url.
> *   **Update Interval**: Minimum is 1 minute to prevent API bans/throttling.
> *   **Storage**: Enabling `detailed`, `keep_route`, or a high number of `next_departures` can hit Home Assistant's state storage limits. See [Issue #22](https://github.com/FaserF/ha-db_infoscreen/issues/22).
> *   **Data Accuracy**: Depends on the selected `data_source`.

---

## 🛠️ Services

---

## 📡 Data Sources

This integration allows fetching data from various backend sources via [DBF](https://dbf.finalrewind.org/).

<details>
<summary><strong>👇 Click to expand the full list of supported Data Sources</strong></summary>

### Supported Data Sources

#### 🇩🇪 Germany

*   **IRIS-TTS** (Deutsche Bahn) - *Default / Recommended*
*   **AVV – Aachener Verkehrsverbund**
*   **AVV – Augsburger Verkehrs- & Tarifverbund**
*   **BEG – Bayerische Eisenbahngesellschaft**
*   **BSVG – Braunschweiger Verkehrs-GmbH**
*   **BVG – Berliner Verkehrsbetriebe**
*   **DING – Donau-Iller Nahverkehrsverbund**
*   **KVB – Kölner Verkehrs-Betriebe**
*   **KVV – Karlsruher Verkehrsverbund**
*   **MVV – Münchener Verkehrs- und Tarifverbund**
*   **NAHSH – Nahverkehrsverbund Schleswig-Holstein**
*   **NASA – Personennahverkehr in Sachsen-Anhalt**
*   **NVBW – Nahverkehrsgesellschaft Baden-Württemberg**
*   **NVV – Nordhessischer Verkehrsverbund**
*   **NWL – Nahverkehr Westfalen-Lippe**
*   **RMV – Rhein-Main-Verkehrsverbund**
*   **RSAG – Rostocker Straßenbahn**
*   **RVV – Regensburger Verkehrsverbund**
*   **SaarVV – Saarländischer Verkehrsverbund**
*   **VAG – Freiburger Verkehrs AG**
*   **VBB – Verkehrsverbund Berlin-Brandenburg**
*   **VBN – Verkehrsverbund Bremen/Niedersachsen**
*   **VGN – Verkehrsverbund Großraum Nürnberg**
*   **VMT – Verkehrsverbund Mittelthüringen**
*   **VMV – Verkehrsgesellschaft Mecklenburg-Vorpommern**
*   **VOS – Verkehrsgemeinschaft Osnabrück**
*   **VRN – Verkehrsverbund Rhein-Neckar**
*   **VRR – Verkehrsverbund Rhein-Ruhr**
*   **VRR2 – Verkehrsverbund Rhein-Ruhr**
*   **VRR3 – Verkehrsverbund Rhein-Ruhr**
*   **VVO – Verkehrsverbund Oberelbe**
*   **VVS – Verkehrs- und Tarifverbund Stuttgart**
*   **bwegt – bwegt**

#### 🌍 International

*   **BART – Bay Area Rapid Transit**
*   **BLS – BLS AG**
*   **CFL – Société Nationale des Chemins de Fer Luxembourgeois**
*   **CMTA – Capital Metro Austin Public Transport**
*   **DSB – Rejseplanen**
*   **IE – Iarnród Éireann**
*   **LinzAG – Linz AG**
*   **PKP – Polskie Koleje Państwowe**
*   **Resrobot – Resrobot**
*   **Rolph – Rolph**
*   **STV – Steirischer Verkehrsverbund**
*   **TPG – Transports publics genevois**
*   **ZVV – Züricher Verkehrsverbund**
*   **mobiliteit – mobilitéits zentral**
*   **ÖBB – Österreichische Bundesbahnen**

> Note: To use HAFAS for stations also found in IRIS-TTS (e.g. "Frankenforst Kippekausen"), choose the specific backend or set `hafas=1`. See [Issue #8](https://github.com/FaserF/ha-db_infoscreen/issues/8).

</details>

---

## 📦 Migration from ha-deutschebahn

Direct migration is not possible due to API differences. The old integration supported "Start to Destination" routing, which `db-infoscreen` handles differently.

**To replicate "Start -> Destination" behavior:**

1.  **Via Stations**: Use `via_stations` to filter trains going *through* your destination or key stops.

-   **Single Station**: If only one station is entered, filtering is performed **server-side** (at the API) for maximum efficiency.

-   **Multiple Stations**: If multiple stations are entered, the sensor switches to **local filtering** to support complex logic.

-   **Logic (AND/OR)**:
        -   **OR** (Default): Includes trains passing through *at least one* of the specified stations. Ideal for stations with multiple platform names (e.g., "Frankfurt Hbf" vs "Frankfurt Hbf (tief)").
        -   **AND**: Includes only trains passing through *all* specified stations.

2.  **Platforms**: Filter by platform if trains to your destination always use specific tracks.

3.  **Two Sensors**: Create two sensors (one for Start, one for typical changeover stations) to track complex routes.

---

## 📊 Usage & Examples

For a detailed set of examples including platform change alerts, occupancy warnings, and advanced filtering, check out our **[Automation Cookbook](https://faserf.github.io/ha-db_infoscreen/automations/)**.

### Basic Automations

**Notify when the next train is delayed:**

```yaml
automation:
  - alias: "Train Delay Notification"
    trigger:
      - platform: template
        value_template: "{{ state_attr('sensor.station_departures', 'next_departures')[0]['delayArrival'] | int > 10 }}"
    action:
      - service: notify.mobile_app
        data:
          message: >
            The train to {{ state_attr('sensor.station_departures', 'next_departures')[0]['destination'] }}
            is delayed by {{ state_attr('sensor.station_departures', 'next_departures')[0]['delayArrival'] }} min.
```

### Custom Template Sensors

**Display next connection in `HH:MM +Delay` format:**
*(Credit: [kRew94](https://github.com/kRew94) & [kaffeetrinker71](https://github.com/FaserF/ha-db_infoscreen/issues/4#issuecomment-2611684018))*

```yaml
sensor:
  - platform: template
    sensors:
      next_train_formatted:
        friendly_name: "Next Train"
        value_template: >
          {% set conn = state_attr('sensor.uelzen_departures_via_hannover_hbf', 'next_departures') | selectattr('isCancelled', 'equalto', 0) | list | first %}
          {% if conn %}
            {{ conn.train }} at {{ conn.scheduledDeparture }}{% if conn.delayDeparture > 0 %} +{{ conn.delayDeparture }}{% endif %}
          {% else %}
            No connection
          {% endif %}
```
*Result: "ICE 2935 at 07:15 +5"*

<details>
<summary><strong>👇 Advanced: Filter Connections by Destination (Start -> Destination)</strong></summary>

*(Credit: [Kanecaine](https://github.com/Kanecaine))*
This example demonstrates how to filter connections from a station (e.g. Berlin Hbf) to a specific target (e.g. Leipzig Hbf) that must be in the train's route.

```yaml
{%- set my_station = "Berlin Hbf" -%}
{%- set target = "Leipzig Hbf" -%}
{%- set number = 0 -%}
{%- set connections = state_attr('sensor.berlin_hbf_departures', 'next_departures') | default([]) | selectattr('isCancelled', 'equalto', 0) -%}
{%- set valid_connections = namespace(connections=[]) -%}
{%- for connection in connections -%}
  {%- set route = connection.route | default([]) | selectattr('name', 'defined') | map(attribute='name') | list -%}
  {%- if my_station in route and target in route and route.index(target) > route.index(my_station) -%}
    {%- set valid_connections.connections = valid_connections.connections + [connection] -%}
  {%- endif -%}
{%- endfor -%}

{%- if valid_connections.connections | length > number -%}
  {%- set connection = valid_connections.connections[number] -%}
  {%- set product_raw = connection.train | default('Unknown') -%}
  {%- set product = product_raw | regex_replace('^(Bus).*|^([A-Z]{2})\\s?\\d*', '\\1\\2') | replace("S ", "S") -%}
  {%- set departure = connection.scheduledDeparture | default('--') -%}
  {%- set delay = connection.delayDeparture | default(0) | int -%}
  {{ product }} {{ departure }}{% if delay > 0 %} +{{ delay }}{% endif %}
{%- else -%}
  --
{%- endif -%}
```

</details>

### JSON Data Structure

The integration attributes provide data in JSON format. Use this to build your own templates.

<details>
<summary><strong>👇 View JSON Example</strong></summary>

```json
{
  "departures": [
    {
      "scheduledArrival": "08:08",
      "destination": "München-Pasing",
      "train": "S 4",
      "platform": "4",
      "delayArrival": 18,
      "messages": {
        "delay": [
          {"text": "delay of a train ahead", "timestamp": "2025-01-21T07:53:00"}
        ]
      }
    }
  ]
}
```
</details>

### Frontend Cards

For a beautiful dashboard display, check out these custom cards:

*   [**ha-departureCard**](https://github.com/BagelBeef/ha-departureCard/) by BagelBeef.
*   [**ha-public-transport-connection-card**](https://github.com/silviokennecke/ha-public-transport-connection-card) (Work in Progress).

---

## 🐛 Troubleshooting & Support

*   **Reporting Issues**: Please report bugs on [GitHub Issues](https://github.com/FaserF/ha-db_infoscreen/issues).
*   **Debug Logging**: To help diagnose issues, enable debug logging in `configuration.yaml`:

```yaml
    logger:
       logs:
          custom_components.db_infoscreen: debug
    ```

## ❤️ Credits

*   Backend data provided by [**dbf.finalrewind.org**](https://dbf.finalrewind.org/).
*   Huge thanks to [**derf**](https://github.com/derf) for the underlying [db-fakedisplay](https://github.com/derf/db-fakedisplay) project!

ha-db_infoscreen

ha-db_infoscreen 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

ha-db_infoscreen

ha-db_infoscreen 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README