Finetuning, reducing error messages

0.1.9

Finetuning

Adding 'alerts' into the sensor

If your gtfs provider ships a 'alerts' url then you can now use this to receive alerts for both origin and destination stops

Improvements on static and real-time

Changes

fix on incorrect sorting in case data for 'today' still provides tomorrow slots
improving chances to find real-time departures, by enabling also an extract via trip_id (instead of route_id)
initial steps for getting real-time 'alerts' (not working yet)

Tuning, Stabilizing and adding option for RealTime sources

POSSIBLE (!) BREAKING CHANGE

The GUI configuration flow has changed a lot, I tried to apply migration procedures but they may not always work. In that case you will have to re-configure your route(s)

Change Log

Adding features:

• added option to add realtime source
• added option to add realtime vehicle tracking source
• improved issue/error handling especially whilst updating datasources
• improved stability wtih missing data and reboots
• improved workflow via GUI

Fixes on missing data

Changes

Increases the chance to setup a new route on a day where there is no traffic, config failed if no traffic 'today'
Fixes bugs where sensor had no route data and system was restarted

Fix bug with tomorrow-dates

Fixes both state value as well as attributes if start/end is tomorrow
Initiate extracting real-time data via trip_id. if the feed does not contain route_id (ex.: TER in France)

Fix bug with missing stop / destination ID's

0.1.6c2

Merge branch 'dev' of https://github.com/vingerha/gtfs2 into dev

Fix bug with realtime while still extracting new source

0.1.6c1

Fix bug with collecting realtime data whilst still extracting

Fix issue when extracting new data with existing sensor

Breaking Change

Attribute 'offset' moved to 'configure/options and (re)set to 0

Fix issue with 'null' values in routes

Fixes concatenation issue when routes contain 'null' values for name / short_name