gtfs module is now also looking at next day.

[asirinelli]

If no trip has be found today, the next trip tomorrow is returned.
This should close #7956.

Description:

Related issue (if applicable): fixes #7956

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• New dependencies have been added to the REQUIREMENTS variable (example).
• New dependencies are only imported inside functions that use them (example).
• New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
• New files were added to .coveragerc.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[homeassistant]

Hi @asirinelli,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[renemarc]

Hi @asirinelli,

We both came up with solutions for next-day departures, great minds think alike! 😃 Your approach makes sense, but running that second query is expensive in terms of I/O on a Raspberry Pi's SD card since the original query is already slow to begin with.

I am trying to optimize the GTFS sensor as much as possible, and came up with a series of upgrades that would reduce expensive I/Os like the original query does. Some have PRs ready, others are awaiting in the pipeline for these building blocks to be approved first.

As an alternative, PR #20992 runs an optimized initial query only once, capturing all data from yesterday, today and tomorrow then filters the relevant dates in code. Would you like to give it a try?

[robbiet480]

Closing in favor of #20992