Releases: hasl-sensor/integration
v3.2.0b2
What's Changed
- bring back Route Planner 3.1 sensor
- bump trafiklab-sl dependency to v1.0.2
- Updated readme for the beta, referencing correct departure card
⚠️ Breaking change
RP3 sensor's attributes now bundled under route
key. This is done to prevent history recorder from storing too much data
Full Changelog: v3.2.0b1...v3.2.0b2
v3.2.0b1
What's Changed
sl_find_location
,sl_find_trip_id
andsl_find_trip_pos
work again.- The results are now returned back using normal service call and not custom event which allows using results in automations
- added missing SV translation for error messages in configuration flow
- bump trafiklab-sl dependency to v1.0.1
⚠️ Breaking change
RP3 sensor is temporary disabled and will be brought back in next release
Full Changelog: v3.2.0b0...v3.2.0b1
v3.2.0b0
What's Changed
- New Departures and Deviations based on new SL Traffic API by @NecroKote in #71
- updated code for Departure and Status sensors that follow recent HASS changes
- Spelling fixes and API URL bump by @systemcrash in #69
- Menu-based integration selector for new integrations
- legacy integrations are not available for now. Should still work if configured previously or via
configuration.yaml
- legacy integrations are not available for now. Should still work if configured previously or via
- New configuration step that allows searching for stops while configuring Departure Integration.
- based on SL Stop Lookup API and requires
SL Platsuppslag
API key to work
- based on SL Stop Lookup API and requires
New Contributors
- @systemcrash made their first contribution in #70
Full Changelog: 3.1.1...v3.2.0b0
v3.1.1
v3.1.0
What's Changed
This is major relase adding Resrobot functionallity BUT with some known upgrade issues due to some bad decisions earlier in development. During some cases the automatic upgrade of sensors might fail and to restore a broken sensor it must be fully removed and then recreated manually. Sorry.
BREAKING CHANGES
- During some cases the automatic upgrade of sensors might fail, to restore a broken sensor it must be fully removed and then recreated manually. Sorry.
- Service find_location renamed to
sl_find_location
- Service find_trip_id renamed to
sl_find_trip_id
- Service find_trip_pos renamed to
sl_find_trip_pos
ADDED
- API Communication for Resrobot 2.1
- Departure sensor using Resrobot API
- Arrival sensor using Resrobot API
- Route sensor using Resrobot API
- Lookup services for resrobot locations
Full Changelog: 3.0.6...3.1
v3.1.0b2
What's changed
Fixes
- Fixes hasl-sensor/integration#43 Warning on deprecated 'async_get_registry' being used
- Removed localized titles in en.json and sv.json due to hassfest validation failing
v3.1.0b1
Project will change name to Swedish Public Transit Sensor (HASL)
because resrobot supports the whole country however for Stockholm region it is still recomended to use SL-specific apis since they contain alot of extra data.
Breaking Changes
- Service find_location renamed to
sl_find_location
- Service find_trip_id renamed to
sl_find_trip_id
- Service find_trip_pos renamed to
sl_find_trip_pos
Added
- API Communication for Resrobot 2.1
- Departure sensor using Resrobot API
- Arrival sensor using Resrobot API
- Route sensor using Resrobot API
- Lookup service for resrobot locations
Changed
- Updated translation for names ad descriptions and strings where applicable
v3.0.6
What's Changed
Added
- Errors are now logged to error and not just to debug so you know whats wrong when it fails
- If sensor data is empty, force refresh even if intervall is not up yet
Fixes
- Added missing translation from GUI for new wizard
- Fixes hasl-sensor/integration#38) broken logging
Full Changelog: 3.0.5...3.0.6
v3.0.5
What's Changed
Fixes
- Fixes hasl-sensor/integration#36 introduced in 3.0.3
- Fixes hasl-sensor/integration#35 anoying log message due to stupidity
Changes
- Sensor will now show unavailable until sensor data is initiated
- Configuration now stored in data and not options inside of configuration object
- Implemented separate configuration schema versioning (restarting with schema version 2. Everyting earlier is to be treated as version 1)
- Now configures integration in one step when adding new integration
- Harmonizing version settings between slapi and core as theese will never differ anymore
Full Changelog: 3.0.4...3.0.5
v3.0.4
What's Changed
- Fixes hasl-sensor/integration#33 due to dependency updates in Home Assistant
Full Changelog: 3.0.3...3.0.4