V1.7
Pre-release
Pre-release
π Additional Features & Architectural Changes
ποΈ Config Subentry Architecture
- Subentry Pattern Implementation: Transititioned the internal architecture to use a
ConfigSubentrypattern (#209, #353). This allows for granular management of individual devices (Trackers) and the Service itself within a single parent Config Entry. - Subentry Flows: Added specific config flows for managing subentries, including device selection and options handling (#212, #353).
- Self-Healing & Deduplication: Implemented logic to prevent duplicate subentries and automatically heal/link orphaned devices to the correct service anchor (#419, #432).
βοΈ Discovery & Automation
- Cloud Discovery: Added support for cloud discovery triggers. The integration can now automatically detect when new trackers are added to the Google account and prompt to register them in Home Assistant (#244, #271).
- Discovery Runtime: Implemented the underlying runtime to handle discovery signals and metadata (#245).
ποΈ UI & Entities
- Stop Sound Button: Added a dedicated "Stop Sound" button entity (and service) to explicitly stop ringing devices (#49).
- Nova Auth Sensor: Added a specific binary sensor to surface the immediate authentication status of the Nova API (#149, #156).
- Contributor Mode: Added and localized specific options for "Contributor Mode" to assist with advanced debugging (#663).
- Activity Health Tracking: Implemented activity-based health tracking specifically for FCM (Firebase) clients to detect stalled connections (#708).
β‘ Performance & Quality of Life
- Lazy Loading: Significantly improved startup time and event-loop stability by lazy-loading heavy dependencies:
- Recorder history fallback (#706)
- Protobuf decoders (#705)
http_eceencryption modules (#705)- Chromedriver dependencies (#599)
- Strict Typing & Linting: Enforced strict
mypytyping across the codebase (Coordinators, API helpers) and added Semgrep SAST workflows for higher code quality (#265, #624, #215).
π Specific Bug Fixes
- History & Timestamps:
- Fixed Recorder history to respect the
last_seentimestamp from the device rather than the Home Assistant state-change timestamp. This ensures historical maps reflect the actual time the device was at a location, not when HA received the update (#163, #165, #167). - Fixed
datetimehandling to strictly use UTC and ISO strings, resolving future deprecation warnings (#160, #184).
- Fixed Recorder history to respect the
- Map View Rendering:
- Data Accuracy:
- Notifications:
- Fixed GCM sender fallback logic when receiving HTML responses instead of JSON (#172).
HUGE thanks to @jleinenbach for this release!