Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Different Buses but same stops results in wrong results #115

Open
1 task done
Krispkiwi opened this issue Dec 14, 2024 · 7 comments
Open
1 task done

[Bug]: Different Buses but same stops results in wrong results #115

Krispkiwi opened this issue Dec 14, 2024 · 7 comments
Labels
bug Something isn't working

Comments

@Krispkiwi
Copy link

Own Analysis

  • I cannot find my issue in the documentation

A clear and concise description of what the bug is.

If you have different bus route that visit the same stops as part of it and add them both, the second one you add defaults to the timetable of the original one you added instead of what it's supposed to be.

Provide details on the data source(s)

- https://files.mobilitydatabase.org/mdb-983/mdb-983-202412050022/mdb-983-202412050022.zip
- Yes

Config in case of setup using start / stop station

Wakari To City & Helensbrough to City Stop 185 to Bus Hub

Config in case of setup using location based departures

No response

Info on your installed version

Latest release of both Home assistant supervised and GTFS2

Relevant log output

No response

@Krispkiwi Krispkiwi added the bug Something isn't working label Dec 14, 2024
@vingerha
Copy link
Owner

vingerha commented Dec 14, 2024

Need more details, cannot guess routes with this litle info, show results and explain in DETAIL what you see and in DETAIL what you expect

@Krispkiwi
Copy link
Author

So with the GTFS information linked, both the Helensbrough to St Clair and Wakari to Corstophine buses go to stop 185 and go to the bus hub in town before reaching their final destination.

If I add Helensbrough first and say that one has 22 minutes till the next bus reaches stop 185 and Wakari to Corstophine had 50 minutes till the next bus reaches stop 185. Both will show 22 minutes. Essentially if you have two bus routes that cover two of the same stops, the addon will get confused and think they're both the same even though they're not.

@vingerha
Copy link
Owner

vingerha commented Dec 14, 2024

I see no issue except for not knowing if the dept. times are OK themselves
Added first Wakari > 185, then Helensborough > 185
image
image

EDIT: note that this is done on my server in CET timezone so the times will look odd to you, the one thing I see though is thjat they differ which you say they donot

@Krispkiwi
Copy link
Author

I see no issue except for not knowing if the dept. times are OK themselves Added first Wakari > 185, then Helensborough > 185 image image

EDIT: note that this is done on my server in CET timezone so the times will look odd to you, the one thing I see though is thjat they differ which you say they donot

I took a video of it here https://www.youtube.com/watch?v=M3ri0tw8uVw

@vingerha
Copy link
Owner

You do understand that initally you left out details ... I will try to have a look later in the week as I cannot repicate this without TZ settings

@vingerha
Copy link
Owner

I finally got it working in my latest release (had a bug). I added the two routes from 185 to the bus stop and they show clearly different data. So my guess is that your card is wrongly configured

image

@vingerha
Copy link
Owner

Or in other words, show the the data of the entity that is providing the wrong time, no cards, no config, I need the entity data and the value that you use, plus state where it is 'wrong'. Do note that if the GTFS data provides feedback that is incorrect compared to the published online scheule, this usually (! not always !) is an issue with the data-set

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants