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

GTFS indicates 0 if no more departure today #7956

Closed
Kernald opened this issue Jun 8, 2017 · 9 comments
Closed

GTFS indicates 0 if no more departure today #7956

Kernald opened this issue Jun 8, 2017 · 9 comments

Comments

@Kernald
Copy link
Contributor

Kernald commented Jun 8, 2017

Home Assistant release (hass --version):
0.46 (Docker image)

Python release (python3 --version):
I don't know, the one bundled in the Docker image

Component/platform:
sensor.gtfs

Description of problem:
When the next departure at a given stop is scheduled for tomorrow, the GTFS sensor indicates 0. At midnight, it switches correctly to the delay until the next departure.

Expected:
If no more departures found today, the sensor should look at the next day(s).

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@Kernald
Copy link
Contributor Author

Kernald commented Aug 12, 2017

This issue is still relevant.

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@Kernald
Copy link
Contributor Author

Kernald commented Dec 11, 2017

The issue is still relevant.

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@brianredbeard
Copy link

Curious if this has been fixed.

@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@brianredbeard
Copy link

brianredbeard commented Oct 26, 2018 via email

@cgarwood
Copy link
Member

This is a year and a half old at this point. I'm going to close it. Please create a new issue if there is still an issue as of 0.84.

asirinelli added a commit to asirinelli/home-assistant that referenced this issue Jan 26, 2019
If no trip has be found today, the next trip tomorrow is returned.
This should close home-assistant#7956.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants