Releases: pnbruckner/ha-composite-tracker
Add UI config flow, remove time zone features & legacy tracker support
Breaking Change
- All time zone related features have been removed. See https://github.com/pnbruckner/ha-entity-tz for an integration that replaces those features, and more.
- Any tracker entry removed from YAML configuration will be removed from the system.
trackers
in YAML configuration must have at least one entry.- The
entity_id
attribute has been changed toentities
.entity_id
did not show up in the attribute list in the UI.
All Changes
- Add UI config flow.
- Add YAML reload service.
- Add translations.
- Allow any entity that has GPS attributes.
- Change
entity_id
attribute toentities
. - YAML config must have at least one tracker entry.
- Remove time zone related features.
- Remove legacy tracker support.
- Remove config entry when tracker removed from YAML.
- Handle frozen EntityDescription.
Fix timezonefinder install errors on ARM targets
timezonefinder>=6 changed its build infrastructure and started using the h3 package, which seems to break on ARM targets. Going back to version 5.2.0 seems to avoid those problems.
Fix startup failure due to timezonefinderL import error
The timezonefinderL package uses another package named importlib-resources. That package recently changed such that a method timezonefinderL uses (open_binary) is no longer available. That causes an import error, which in turn prevents composite from starting (assuming your configuration uses the device_or_utc or device_or_local choice for the time_as option.)
This change fixes that issue by changing the timezonefinder defaults. Specifically, the default package is now timezonefinder v6.2.0 instead of timezonefinderL v4.0.2, and the default class is now TimezoneFinderL instead of TimezoneFinder.
If, however, your configuration specifies the timezonefinderL package, you will need to manually change it to use the timezonefinder package instead. The easiest way to do that is to remove the tz_finder (and tz_finder_class) option(s) from your composite configuration.
See #49 for more details.
Fix timezonefinder doing file I/O in async_setup
Also, catch timezonefinder timezone_at exception.
Fix: Exception in _update when dispatching 'composite_speed-NAME'
A race condition can cause the following error during startup:
Exception in _update when dispatching 'composite_speed-NAME': (None, None)
This release fixes that bug.
Add support for last_timestamp attribute
Some device tracker integrations (e.g., tile) include a last_timestamp attribute that records when the location information was last updated. Use this the same way as the last_seen attribute of other integrations.
Fix bug in log message
This happens when two input entity updates are too close in time, which causes a debug message to be written to the log. However, that statement had a bug, which results in traceback messages in the log, but no other side effect. This release fixes that bug.
Add angle & direction attributes to speed sensor
Better filter out speed value outliers, especially when a pair of location updates comes from different input entities.
Add speed sensor
Convert last_seen attribute to datetime when restored.