Intergration stopped after midnight

[Ed1954]

The problem

Can't see any connections

What version of Home Assistant Core has the issue?

2024-12-3

What version of DeutscheBahn Integration has the issue?

3.03

What type of installation are you running?

Home Assistant Supervised

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Dieser Fehler stammt von einer benutzerdefinierten Integration

Logger: custom_components.deutschebahn.sensor
Quelle: custom_components/deutschebahn/sensor.py:154
Integration: Deutsche Bahn (Dokumentation, Probleme)
Erstmals aufgetreten: 10:50:11 (194 Vorkommnisse)
Zuletzt protokolliert: 11:38:15

Requested 4 connections, but only 1 are available.

Additional information

No response

[TheNexusCore]

Same here, HA Core 2024.12.3 and integration version 3.03.
Type is HaOS.

Log:

Logger: custom_components.deutschebahn.sensor
Quelle: custom_components/deutschebahn/sensor.py:154
Integration: Deutsche Bahn (Dokumentation, Probleme)
Erstmals aufgetreten: 03:04:31 (1254 Vorkommnisse)
Zuletzt protokolliert: 11:43:37

Requested 3 connections, but only 1 are available.

[namorwoy]

Same, HA Core 2024.12.3 and integration version 3.03.

[emptymalei]

Same here.

[realwuffi]

I believe it has to do with change of the new schedule since yesterday.
This made the schiene library break, because

The page http://mobile.bahn.de/bin/mobil/query.exe/dox is no longer available (301 - moved permanently)
and https://reiseauskunft.bahn.de/bin/query.exe/dn does say that it can no longer be used.

If I have time the next couple of days I could have a look at the schiene library and may be able to support fixing that

[FaserF]

Thanks for all the input, for now I have disabled update fetching with 3.0.4 until we have found a solution.
More details: https://github.com/FaserF/ha-deutschebahn?tab=readme-ov-file#breaking-warning

[hostand]

Thanks for all the input, for now I have disabled update fetching with 3.0.4 until we have found a solution. More details: https://github.com/FaserF/ha-deutschebahn?tab=readme-ov-file#breaking-warning

Hi @FaserF !

I have my own rest sensor based on this URL from DeutschBahn: https://iris.noncd.db.de/iris-tts/timetable/plan/station_id/ymd/H replace station_id (evaNumber) for desired station and ymd for year(2 digits) month day and H for hour. This URL is used by the system that show those old 'blue screens' in the stations.

e.g. Berlin HBF https://iris.noncd.db.de/iris-tts/timetable/plan/8089185/241216/21

I use also another URL when I need full information for db data both departures and arrivals (just change departures for arrivals) on
https://www.bahnhof.de/api/boards/departures?evaNumbers=8089021&evaNumbers=8011160&evaNumbers=8098160&filterTransports=HIGH_SPEED_TRAIN&filterTransports=INTERCITY_TRAIN&filterTransports=INTER_REGIONAL_TRAIN&filterTransports=REGIONAL_TRAIN&filterTransports=CITY_TRAIN&filterTransports=UNKNOWN&duration=60&stationCategory=1&locale=de&sortBy=TIME_SCHEDULE

[bcutter]

What a downer. Well, web-scraping is never a reliable option. If I remind correctly this was the reason for HA to remove DB integration from Core.

If I understand correctly, v3.0.4 mainly acts as messenger so users see (why) it is broken. Disabling sensor updates probably doesn't make any difference, does it.

Fingers crossed it can somehow be fixed shortly.

Switching the integration is not an option for me. This one is great and I heavily customized things, relying on attributes this integration provides and much more.

[kaystrobach]

Maybe this helps:

https://developers.deutschebahn.com/db-api-marketplace/apis/product/timetables

[CHirch]

Using DB Timetables API seems like the best solution to me. On the downside users whould have to create an API key for themselfes.
However many changes are necessary to keep the integration running.