[Feature Request]: Migration path from ha-deutschebahn

[Kanecaine]

The request

First of all, thanks for starting this new integration. As you advertise it as the superior of ha-deutschebahn, it would be very nice to have a migration path / detailed upgrade info. As i have understood for now, this new integration behaves slightly different: instead of defining 2 stations you can only specify 1 station and see all arrivals and departures.

So when i am interested in one specific connection between 2 stations, i assume that i have to do it myself by evaluating all the entity attributes and filter out only relevant connections (e.g. where my destination station is part of the route). Maybe you can provide an example of how to do this with a template sensor or something approbiate.

Many thanks in advance.

Is your feature request related to a problem?

Additional information

No response

[FaserF]

That is a real good feature request. Right now the API just provides entering one station to track, no start/destination.
Unfortunatly nearly all new APIs (including Deutsche Bahn API, HAFAS and so on) only provide data for a station. The "old" DB (schiene) API was the only one which provided this functionality.

I think that this maybe can be implemented, but needs to be added to the backend api provider first (https://dbf.finalrewind.org/ / https://github.com/derf/db-fakedisplay/tree/main)

[FaserF]

I will start providing some informations here: https://github.com/FaserF/ha-db_infoscreen?tab=readme-ov-file#migrating-from-ha-deutschebahn

[bcutter]

Coming here via FaserF/ha-deutschebahn#59 (comment) from https://github.com/FaserF/ha-db_infoscreen?tab=readme-ov-file#migrating-from-ha-deutschebahn.

So happy to read this. Installed the 3.0.5 update of the old integration and of course the new one, but did not restart HA yet. I have so intensively used GUI customization and information in automations etc., that before productively using the new integration I need to know exactly which attribute of which sensor in the new integration matches the ones from the old one.

Seeing we don't even (yet) have a track (from station A to station B) as sensor sounds like it's a quite long way to go still.

Anyway, as said: reaaaaaally great to see development progress here. I did not expect a complete new integration. Awesome!

[Kanecaine]

Ok, I'll make a start. With the new integration, I have a sensor for Berlin Central Station and would now like to know which connections there are to Leipzig. With the following template, I get the same output as with the previous integration (try it out first in the template editor):

{%- set target = "Leipzig Hbf" -%}
{%- set number = 0 -%}
{%- set connections = state_attr('sensor.berlin_hbf_departures', 'next_departures') | selectattr('destination', 'equalto', target) | list -%}
{% if connections is not none and connections | length > number %}
  {% set connection = connections[number] %}
  {% set product = connection.train %}
  {% set departure = connection.scheduledDeparture %}
  {% set delay = connection.delayDeparture | int %}
  {{ product }} um {{ departure }}{% if delay > 0 %} +{{ delay }}{% endif %}
{% else %}
  --
{% endif %}

You first enter the destination station in “target”. The variable “number” determines which connection we are interested in. “0” corresponds to the current one, ‘1’ to the next one, etc. The rest of the template can initially be used unchanged and should give you the following output:

IC 495 um 22:28 +1

I have created a new template sensor with this template. The sensor provides information about the current connection from Berlin to Leipzig, the time, which train type and, if applicable, its delay. I use a second sensor to query the next connection by using the same template with “number: 1”. If there is none, “--” is output instead. This works for my dashboard for the time being in order to have the same functionality as before.

[MarkusHaag]

Thank you very much for this new integration.

I like that it is now possible to see track and which train. Regarding selection of target. Could option „nur Fahrten über“ in dbf.finalrewind be used? With that option we could get only data of relevant trains.

[M-See]

Awesome that you port it now, really looking forward to it. Maybe one addition to the Readme -- dbf_data doensn´t show all options/stations directly and e.g. "Godorf Bahnhof, Köln" was not working -- while copying it from the URL as "godorf bahnhof, köln" resulted in a properly configured sensor. Might be worth to add that to the readme.

Thanks for developing that!

[FaserF]

Awesome that you port it now, really looking forward to it. Maybe one addition to the Readme -- dbf_data doensn´t show all options/stations directly and e.g. "Godorf Bahnhof, Köln" was not working -- while copying it from the URL as "godorf bahnhof, köln" resulted in a properly configured sensor. Might be worth to add that to the readme.

Thanks for developing that!

I have now fixed this, should be working with the upcoming release 2025.01.2 - in both ways, lowercase, uppercase and with spaces

Thank you very much for this new integration.

I like that it is now possible to see track and which train. Regarding selection of target. Could option „nur Fahrten über“ in dbf.finalrewind be used? With that option we could get only data of relevant trains.

This feature will also be available with release 2025.01.2

[MarkusHaag]

Thank you for this Great new Version. I will Jump tomorrow into Template Sensors. The data and selection should suit my needs.

I would only propose to have the „via“ Information in Sensor Name as well. E.g. I Need to change Train in Cologne, but it is not allowed to have Station cologne twice. I would need it for selection between way to work and way Home.