Problem with several trains on one connection #16
Comments
|
I#ll try to copy the Attributes next time this will happen. |
|
Can you then please also add a screenshot of the DB Website or Navigator to see the difference? First guess: We're not showing the next departure, but the next arrival. This could be an API issue. Or we need to change the query. |
|
It looks like yesterday was just a one-off bug. The Attribute: - origin: Uelzen
departure: '2024-12-22T12:09:00+01:00'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T13:15:00+01:00'
delay_arrival: '0:00:00'
transfers: 0
duration: '1:06:00'
canceled: false
ontime: true
products: ME 82869
legs:
- origin: Uelzen
departure: '2024-12-22T12:09:00+01:00'
platform: '301'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T13:15:00+01:00'
platform_arrival: 4 D-G
delay_arrival: '0:00:00'
mode: train
name: ME 82869
canceled: false
distance: null
remarks:
- Fahrradmitnahme begrenzt möglich
- Rollstuhlstellplatz
stopovers:
- Uelzen
- Suderburg
- Unterlüß
- Eschede
- Celle
- Großburgwedel
- Isernhagen
- Langenhagen Mitte
- Hannover Hbf
- origin: Uelzen
departure: '2024-12-22T13:15:00+01:00'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T13:58:00+01:00'
delay_arrival: '0:00:00'
transfers: 0
duration: '0:43:00'
canceled: false
ontime: true
products: ICE 1671
legs:
- origin: Uelzen
departure: '2024-12-22T13:15:00+01:00'
platform: '101'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T13:58:00+01:00'
platform_arrival: '4'
delay_arrival: '0:00:00'
mode: train
name: ICE 1671
canceled: false
distance: null
remarks:
- Komfort Check-in verfügbar - wenn möglich bitte einchecken
- Fahrradmitnahme reservierungspflichtig
- Fahrradmitnahme begrenzt möglich
- Bordrestaurant
stopovers:
- Uelzen
- Celle
- Hannover Hbf
- origin: Uelzen
departure: '2024-12-22T14:14:00+01:00'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T14:51:00+01:00'
delay_arrival: '0:00:00'
transfers: 0
duration: '0:37:00'
canceled: false
ontime: true
products: ICE 1205
legs:
- origin: Uelzen
departure: '2024-12-22T14:14:00+01:00'
platform: '101'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T14:51:00+01:00'
platform_arrival: '4'
delay_arrival: '0:00:00'
mode: train
name: ICE 1205
canceled: false
distance: null
remarks:
- Komfort Check-in verfügbar - wenn möglich bitte einchecken
- Fahrradmitnahme reservierungspflichtig
- Fahrradmitnahme begrenzt möglich
- Bordrestaurant
- >-
Kein behindertengerechtes WC in Wagen 22. Mobilitätseingeschränkte
Reisende wenden sich bzgl. eventuell erforderlicher Umbuchungen an
unsere Mobilitätsservice-Zentrale unter 030 65212888.
stopovers:
- Uelzen
- Hannover Hbf |
|
Damn, the problem still exists. The Screenshot The Attribute: - origin: Uelzen
departure: '2024-12-22T18:18:00+01:00'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T19:05:00+01:00'
delay_arrival: '0:00:00'
transfers: 0
duration: '0:47:00'
canceled: true
ontime: true
products: ICE 1687
legs:
- origin: Uelzen
departure: '2024-12-22T18:18:00+01:00'
platform: '101'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T19:05:00+01:00'
platform_arrival: '4'
delay_arrival: '0:00:00'
mode: train
name: ICE 1687
canceled: true
distance: null
remarks:
- Komfort Check-in verfügbar - wenn möglich bitte einchecken
- Fahrradmitnahme reservierungspflichtig
- Fahrradmitnahme begrenzt möglich
- Bordrestaurant
- Fahrt fällt aus
- >-
Für ICE 1687 verkehrt Ersatzfahrt ICE 2911 zwischen Uelzen und
Hannover Hbf
stopovers:
- Uelzen (canceled)
- Celle (canceled)
- Langenhagen Mitte (canceled)
- Hannover Hbf (canceled)
- origin: Uelzen
departure: '2024-12-22T19:15:00+01:00'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T19:58:00+01:00'
delay_arrival: '0:00:00'
transfers: 0
duration: '0:43:00'
canceled: false
ontime: true
products: ICE 1677
legs:
- origin: Uelzen
departure: '2024-12-22T19:15:00+01:00'
platform: '101'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T19:58:00+01:00'
platform_arrival: '4'
delay_arrival: '0:00:00'
mode: train
name: ICE 1677
canceled: false
distance: null
remarks:
- Komfort Check-in verfügbar - wenn möglich bitte einchecken
- Fahrradmitnahme reservierungspflichtig
- Fahrradmitnahme begrenzt möglich
- Bordrestaurant
- >-
Rollstuhlgerechte Einstiegstür in Wagen 22 defekt.
Mobilitätseingeschränkte Reisende wenden sich bzgl. eventuell
erforderlicher Umbuchungen an unsere Mobilitätsservice-Zentrale unter
030 65212888.
stopovers:
- Uelzen
- Celle
- Hannover Hbf
- origin: Uelzen
departure: '2024-12-22T20:09:00+01:00'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T21:15:00+01:00'
delay_arrival: '0:00:00'
transfers: 0
duration: '1:06:00'
canceled: false
ontime: true
products: ME 82885
legs:
- origin: Uelzen
departure: '2024-12-22T20:09:00+01:00'
platform: '301'
delay: '0:00:00'
destination: Hannover Hbf
arrival: '2024-12-22T21:15:00+01:00'
platform_arrival: '3'
delay_arrival: '0:00:00'
mode: train
name: ME 82885
canceled: false
distance: null
remarks:
- Fahrradmitnahme begrenzt möglich
- Rollstuhlstellplatz
stopovers:
- Uelzen
- Suderburg
- Unterlüß
- Eschede
- Celle
- Großburgwedel
- Isernhagen
- Langenhagen Mitte
- Hannover Hbf |
|
Strange. I cannot see anything special about the skipped trains. Also your earlier comment...
... The slower train should still be displayed in the attributes, I think. Let's try and find out, how the skipped ME trains are different from the others. Can you browse the website and look for differences, when this issue happens next time? The replacement ICE might be somehow special, as it's a replacement. Still, it should be shown of course. Out of curiosity: Did you specify the direct-only option? Or a delay? Oh, and a GitHub hint: please format the attributes as code. That will make them much more readable. You can do so, by wrapping them as "fenced code blocks". |
The “Deutsche Bahn” integration, which is currently not working and refers to your integration, does the same. It always shows the next train that is faster to the destination.
I'll keep an eye on it. I have created two entities, one as a direct connection and one without a direct connection. And yes, you're right, I forgot the formatting ;-) |
|
Ah, and another effect. |
|
I just bumped pyhafas to the next version, but haven't "released" it yet. Could you update your installation to the |
|
Update is running |
|
Ok, here is the next "bug". However, the DB Navigator shows a regional train 82813 at 09:09 and an ICE 2943 at 09:16. However, the ICE is a replacement train for the ICE 1577. The original ICE 1577 can be found in the attributes, but as “canceled: true”. You can also see that the ICE is being replaced by another one, this is stated under “remarks: Her are the Attributes: Direct Connection: No Direct Connection: |
|
Let's open a separate issue for the replacement train and stick to the missing trains in this one. |
I also linked #15 (comment). I am a bit afraid that your issues might require a fix in the API, which I don't really understand how it works... Browsing around, maybe this could be related, too: public-transport/hafas-client#287 |
|
I have tried to implement the change mentioned above into the pyhafas library and created a branch to see, if it changes anything: https://github.com/akloeckner/hacs-hafas/tree/fix/rtMode I am a bit hesitant to create a pre-release from it for testing, because it is really hacked together. Can you download the code itself and test it on your end? If not, I might need to jump through the loop and create a pre-release for you. Until then: Please let me know, whenever you see the effect again. If I can react quickly enough, I can then check in my test setup if the missing train is there... |
|
I'll test it. |
|
Ok, the bug still exists. It is 18:56, the next trains are: The Integration shows 20:09 Regional Train 82885 The Attributes: |
if there are 2 different trains for a connection (in my example Uelzen to Hanover, there are ICE and regional express trains), often only the ICE trains are displayed.
Specifically:
Saturday at 14:09 there is a Regionalexpress to Hanover, at 15:15 an ICE.
If I enquire about the next connection at 13:50, only the ICE is displayed, the regional express is not shown.
In the evening there is no ICE, only a regional express. These are then displayed correctly as the next connection.
In the legs, however, I can see the regional express at 14:09. How can I display this as the next connection?
Translated with DeepL.com (free version)
The text was updated successfully, but these errors were encountered: