Skip to content

v0.1.5 - Device-Level Tracking

Choose a tag to compare

@nenadjokic nenadjokic released this 08 Feb 08:03
· 18 commits to main since this release

🎯 Major Improvement: Device-Level Tracking

This release introduces device-level tracking instead of sensor-level tracking - a significant UX improvement!

What Changed?

Previously, if you had a device like "iPad" with 10+ sensors, you would see all 10 sensors listed separately in unavailable/battery/signal lists. This created massive clutter.

Now: Each device appears only once, regardless of how many sensors it has! 🎉

Example:

Before v0.1.5:

  • ❌ iPad sensor 1 - unavailable
  • ❌ iPad sensor 2 - unavailable
  • ❌ iPad sensor 3 - unavailable
  • ❌ iPad sensor 4 - unavailable
  • ❌ ... (10+ entries for one device!)

After v0.1.5:

  • ✅ iPad - unavailable

Benefits:

  • Cleaner lists - No more sensor clutter
  • Easier monitoring - See device status at a glance
  • Accurate counts - Sensor counts now reflect actual device count
  • Better UX - More intuitive and user-friendly

What's Affected:

This improvement applies to all monitoring categories:

  • 🔴 Unavailable Devices
  • 🔋 Low Battery Devices
  • 📡 Weak Signal Devices

Technical Details:

  • Added device deduplication using device_id tracking
  • Prioritizes device name over sensor name
  • Standalone entities (without parent devices) still tracked individually
  • No breaking changes - just better organization!

Full Changelog: v0.1.4...v0.1.5