GTFS integration doesn't handle case where there is only a calendar_dates file with no calendar file

[ggiesen]

The problem

Trying to use the GTFS integration with these two feeds:

• GO Transit
• UP Express

Unfortunately, any sensors set up using these feeds show only Unknown.

Neither of these files include a calendar.txt file, only a calendar_dates.txt file. Per the GTFS specification, this is legal as long as calendar_dates.txt includes all dates of service.

Looking at the SQL query in the source, if I'm reading it correctly, it looks like calendar_dates.txt may not even be used, as it seems to only reference a calendar table.

Given the above GTFS feeds are legal per the specification, the GTFS integration should handle this case.

What version of Home Assistant Core has the issue?

core-2025.6.1

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: WE
    destination: UN
    data: UP-GTFS.zip
    name: "UP Express: Weston towards Union"
    include_tomorrow: true
  - platform: gtfs
    origin: WE
    destination: PA
    data: UP-GTFS.zip
    name: "UP Express: Weston towards Pearson Airport"
    include_tomorrow: true

Anything in the logs that might be useful for us?

Additional information

Nothing of substance in diagnostic logs:

2025-06-18 23:50:50.191 DEBUG (SyncWorker_6) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:51:19.974 DEBUG (SyncWorker_1) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:51:20.501 DEBUG (SyncWorker_6) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:51:49.939 DEBUG (SyncWorker_6) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:51:50.392 DEBUG (SyncWorker_2) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:52:19.925 DEBUG (SyncWorker_3) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:52:20.412 DEBUG (SyncWorker_5) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:52:49.960 DEBUG (SyncWorker_0) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:52:50.421 DEBUG (SyncWorker_1) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:53:20.044 DEBUG (SyncWorker_3) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:53:20.500 DEBUG (SyncWorker_5) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:53:49.852 DEBUG (SyncWorker_1) [homeassistant.components.gtfs.sensor] Timetable: []
2025-06-18 23:53:50.214 DEBUG (SyncWorker_3) [homeassistant.components.gtfs.sensor] Timetable: []

[home-assistant]

gtfs documentation
gtfs source

[ggiesen]

Looks like the sensible thing seems to be to use @vingerha's GTFS2 integration, as it seems to work.

[vingerha]

Mine seems to work indeed :) The core-gtfs is old, not maintained and has gaps... it should be removed. I thought about updating it but many transport providers like (?) to deviate from standards which led to covering many exceptions and imo no longer viable to be a clean core implementation.