gtfs2: [Bug]: Etity getting unavailable periodicaly with error in log
Own Analysis
- I cannot find my issue in the documentation
A clear and concise description of what the bug is.
It was working perfect before. But since few weeks, I have an issue of unaivilbility of the sensor for the stops.
I have smetimes data but most of the time it's unavailable
I set refresh to one minute or 3 minute to have fresh data from RT
Provide details on the data source(s)
Datasource is Ilevia from Lille
https://transport.data.gouv.fr/datasets/localisation-des-arrets-ilevia-bus-metro-et-tram-gtfs-pictogrammes-du-reseau-ilevia-2
With Real time data
Config in case of setup using start / stop station
Route tested are 50 and L5
Stops HL001 or HL002
Config in case of setup using location based departures
Info on your installed version
I tryed to go back to version 0.4
Relevant log output
Enregistreur: custom_components.gtfs2.coordinator
Source: custom_components/gtfs2/coordinator.py:157
intégration: GTFS 2 (General Transit Feed Specification) (documentation, problèmes)
S'est produit pour la première fois: 25 janvier 2025 à 23:18:07 (339 occurrences)
Dernier enregistrement: 09:49:42
Error getting gtfs realtime data, for origin: HLO002: Hautes Loges (7) with error: 'NoneType' object is not iterable
Error getting gtfs realtime data, for origin: HLO001: Hautes Loges (36) with error: 'NoneType' object is not iterable
Error getting gtfs realtime data, for origin: HLO002: Hautes Loges (7) with error: Error parsing message with type 'transit_realtime.FeedMessage'
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 22 (13 by maintainers)
And I understand the confusion when one is starting of from a route… which is a transport-line and which is then ignored in favor of all lines serving the start/end chosen. The thing is that for a setup one needs to have a start and end that are served by (at least) one transport-line and this is only (easily) feasible by using a ‘route’. In most cases this is fine but yes…even for me it was a bit confusing as well as my route-start and route-end only have 1 bus-line so I did not bump into this for about 2 years…and forgot