Releases: hasl-sensor/integration
Releases · hasl-sensor/integration
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
v3.0.3
v3.0.2
Added
- Added first and last leg details as attributes for route sensor
- Added possibility to use longitude,latitude pairs as locations in route sensor
- Starting address/location is detailed in attributes for route sensor
- Swedish translation for GUI
- Added stoplists to results for RP3 for route planner
- Added prognosisType for each leg and stoplist in haslworker for route planner
Fixes
- Fixed broken counter for number of transfers in route sensor
- Fixes #26: version number fixed in hacs.json
- Fixes #29: filtering in departure sensor updated
- Fixed broken prognosisType for route sensor (thanks @clearminds)
- Fixed broken stoplist for route sensor (thanks @clearminds)
Changes
- Combining location id and longitude,latitude pars as locations in route sensor
- Route sensor total time does include estimated walking time however walking is not shown as first or last leg in route sensor
Contributors
clearminds