Version 2.3.0

• Add configurable number of time entities

Version 2.2.1

• Fixed Info Traffic Sensors

Version 2.2.0

Changelog:

• Fixed missing stops
• Replaced the API to get traffic information, the new API should be more complete
• Replaced the pre-processed data files by a class fetching them at runtime, this will ensure that the lines/stops listings are up to date, the first configuration might take a few seconds
• Added a new calendar sensor which indicates the planned problems on a line

Version 2.1.3

• Fixed missing stops

Version 2.1.2

• Fixed line filtering
• Added new details attribute

Version 2.1.1

Upgrade idfm-api and fix API errors

Version 2.1.0

• Add new attributes for time sensor:

  At stop: if the train is currently at a stop
  Platform: the platform where the train will arrive
  Status: if the train is on time/late/cancelled ...

Based on a contribution on idfm-api by @Egglestron: droso-hass/idfm-api#4

Version 2.0.2

• Fix for reported schedules in the past (PR#11 by @Egglestron)

Version 2.0.1

• Fix unavailable sensor bug

Version 2.0.0

⚠️ THIS RELEASE CONTAINS BREAKING CHANGES, you will need to delete your current instances of the integration and re-create them after updating

With this new release, we are introducing a brand new version of the idfm-api package, based on the official API from the PRIM platform, thus the data retreival should be more reliable.

Changelog:

• Bump idfm-api version from v0.2.5 to v1.0.4
• Switch to official APIs of PRIM
• Fix for the timeout errors
• Addition of a fourth sensor for the next schedules
• Default refresh interval set to 3 min (and disabled between 1h30 and 5h30 for tram, train and metro) to save bandwidth