General Transit Feed Specification (GTFS) Integration does not work

[anthonyCarigny]

The problem

General Transit Feed Specification (GTFS) seems that does not work.
Sensor configured in configuration.yaml as presented below.
GTFS data file downloaded from here: https://eu.ftp.opendatasoft.com/sncf/gtfs/transilien-gtfs.zip
After restart, DB has been created and I see no errors in the log but sensor state is continuously "unknown" and in info attribute I only see this "No more departures".
Other attributes (e.g origin_station_stop_id, destination_station_stop_name etc.) seems to be set correctly. The only missing (yet the most important) info is next departure time.
Nothing helps. Tried to recreate DB, downloaded different gtfs file, added " to conf file etc.
no success.

What version of Home Assistant Core has the issue?

2022.3.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

gtfs

Link to integration documentation on our website

https://www.home-assistant.io/integrations/gtfs/

Diagnostics information

No response

Example YAML snippet

sensor:
  - platform: gtfs
    origin: "IDFM:478505"
    destination: "IDFM:71572"
    data: transilien.zip
    name: transilien_juvisy_bfm
    include_tomorrow: true

Anything in the logs that might be useful for us?

No response

Additional information

I am duplicating the following issue because it has been closed due to inactivity : #31999

[probot-home-assistant]

gtfs documentation
gtfs source
_{^{(message by IssueLinks)}}

[Shorttravis]

Agreed, I get the same result even though the stop information loads correctly when I click on the sensor in the dashboard.

[github-actions]

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 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[mfolnovic]

Still not working (commenting this just to remove stale label).

[github-actions]

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 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[vingerha]

IMHO this is (again) an issue with the dataset and not GTFS

There is a mismatch in formatting the stop-id, you might need to be using "IDFM:monomodalStopPlace:478505" were it not that this stop id does not exists (verify the stops and stop_times tables for juvisy) ... hence logically no result.

Adding... I myself am trying to work with zou region-sud (06) and there too more than a few issues with the dataset...it is just horrible (stops missing on certain lines, no busses on weekends, etc.etc.) and even thei own website shows those errors (it crashes) ....and it is worse with the other operators in the same area.
Adding more, on HACF there are 2 others with similar dataissues and without wanting to generalize, no one seems to care about data quality

[issue-triage-workflows]

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 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.