v0.1.6 - Smart Unavailable Detection
π οΈ Critical Bug Fixes
This release fixes two major issues that were causing false positives and inaccurate device tracking.
1. π― Smart Unavailable Detection
Problem: Devices were marked as unavailable if even ONE sensor was offline, leading to false alarms.
Solution: A device is now only marked as unavailable if ALL its entities are unavailable.
Example:
- Before v0.1.6: iPad has 10 sensors β 9 unavailable, 1 available β β iPad shown as UNAVAILABLE (false positive!)
- After v0.1.6: iPad has 10 sensors β 9 unavailable, 1 available β β iPad NOT unavailable (accurate!)
This dramatically improves accuracy and prevents false alarms for devices that are actually functioning.
2. π« Self-Sensor Filtering
Problem: Cardio4HA's own sensors were being tracked, causing nonsensical entries like "Cardio4HA - 9.0%" in low battery devices.
Solution: The integration now automatically excludes its own sensors from all tracking categories (unavailable, battery, signal).
What Changed?
Fixed:
- Device unavailable detection now requires ALL entities to be unavailable (not just one)
- Cardio4HA's own sensors are excluded from tracking
- Eliminated false positive unavailable device alerts
- Removed circular self-tracking references
Technical Details:
- Implemented two-pass entity counting algorithm
- Added
device_entity_countsstructure to track total vs unavailable entities per device - Added platform-based filtering to exclude integration's own sensors
- Standalone entities (without device_id) continue to be tracked individually
Upgrade Notes:
After upgrading to v0.1.6:
- Restart Home Assistant
- Wait 60 seconds for the first scan
- You should see significantly fewer unavailable devices (more accurate!)
- No "Cardio4HA" entries in battery/signal lists
This is a recommended upgrade for all users experiencing false unavailable device alerts.
Full Changelog: v0.1.5...v0.1.6