Releases: pnbruckner/ha-composite-tracker
Add Italian translations & update Dutch translations
What's Changed
- Add Italian translations for composite component by @sibest19 in #101
- Update Dutch translations by @Mariusthvdb in #103
New Contributors
- @sibest19 made their first contribution in #101
- @Mariusthvdb made their first contribution in #103
Full Changelog: 4.0.0...4.1.0
Support Home Assistant 2024.11 or newer
What's Changed
- Support Home Assistant 2024.11 or newer by @pnbruckner in #100
- Drop support for Home Assistant versions before 2024.11.0.
- Limit the
device_tracker'ssource_typeattribute to supported values only. - Add option to show unknown speed sensor value as 0.0. This can help when, e.g., the speed sensor is used as an input to the Statistics integration.
Breaking Changes
- Since
binary_sensoris not officially supported as a value of thedevice_tracker'ssource_typeattribute, it will now be reported asrouterinstead.
Full Changelog: 3.6.0...4.0.0
Improve handling of speed and corresponding driving state
What's Changed
- Improve handling of speed and corresponding driving state by @pnbruckner in #99
-
Maintain driving state even when not updating speed sensor
Bug fix: When updates come too close together, speed sensor is not updated. However, if speed was previously above set driving speed threshold, still need to keep device_tracker state as driving, which was previously not the case. -
Add time to hold driving state after speed falls below configured driving speed
New config option: Can help avoid undesired state changes when, e.g., slowing to go around a corner or when stopping at an intersection. -
Add max time between speed sensor updates
New config option: If set, will clear speed sensor state when exceeded.
-
Full Changelog: 3.5.0...3.6.0
Support Home Assistant 2024.8.3 or newer
What's Changed
- Support Home Assistant 2024.8.3 or newer by @pnbruckner in #91
- Drop support for HA versions before 2024.8.3
- Move file I/O to executor
- Don't force sensor updates
Full Changelog: 3.4.5...3.5.0
Use UTC datetimes internally
What's Changed
- Python datetime object comparisons and math don't work as expected when the objects are aware and have the same tzinfo attribute. Basically, the fold attribute is ignored in this case, which can lead to wrong results. Avoid this problem by using aware times in UTC internally. Only use local time zone for user visible attributes.
Full Changelog: 3.4.4...3.4.5
Add missing PACKAGE_MERGE_HINT to config.py
Fix new error w/ HA 2024.8
What's Changed
- Apparently, it's no longer allowed to call
async_get_hassindirectly viaCONFIG_SCHEMA, so move YAML config processing toconfig.py. - Also, a couple other minor fixes/improvements.
Full Changelog: 3.4.2...3.4.3
Restore before checking input entities at startup
Originally input entities were checked at startup before possibly restoring state of the composite entity. This could cause an input entity with data older than the most recent data the composite used before shutdown to temporarily cause the composite to use that old data and abort the restore process. However, the restore process should happen first, so that input data older than the restored state can be properly reject. This release reverses those processes so that restoring happens first.
Import cached_property from functools instead of backports
What's Changed
- Import cached_property from functools instead of backports by @pnbruckner in #73
Full Changelog: 3.4.0...3.4.1
Accept various formats for last_seen/last_timestamp attribute
Enhance "last seen" attribute processing to allow a datetime string format. Basically, these attributes (last_seen or last_timestamp) can be any one of the following:
- a naive Python datetime object which is assumed to be in HA's configured time zone
- an aware Python datetime object in any time zone
- anything homeassistant.util.dt.utc_from_timestamp will accept (after being converted to a float)
- anything homeassistant.util.dt.parse_datetime will accept