Device Health Monitor v1.4.5
Small but useful update — the in-app guide got a major expansion.
What changed in v1.4.5:
The
App Guide & Reference page (accessible from the main page under Help & Support) has been completely rewritten with seven permanent documentation sections:
- Health Ratings — what each rating means and the thresholds behind them
- How Baselines Are Learned — sample collection, the Pending state, the minimum gate, EWMA smoothing, and the 20-sample window
- Protocol Detection & Overrides — how auto-detection works, why devices land on LAN or Hub Mesh, Unknown devices, and how protocol overrides work
- State Attribute Overrides — how the Current State column picks an attribute, when to override it, and how to reset
- Verification (Ping / Refresh) — how verification fires on Poor/Offline devices, Refresh vs Ping priority, and the full Hue Bridge requirement explained:
- Hue bulbs and fixtures can't be pinged/refreshed directly — they go through the Bridge
- You must add your Hue Bridge to monitored devices to enable verification
- One Bridge refresh covers all your Hue devices simultaneously
- If the Bridge isn't added, devices will show
Cannot verify — add Hue Bridge to monitored devices
- Hub Mesh Source Hub Detection — how grouping works and the current C-8 Pro firmware limitation
- Tips for Best Results — including the Hue Bridge tip and notes on Force Scan, State Changed timing, and Low Activity devices
No functional changes — health scoring, scan logic, protocol detection, and all pages work exactly as before. This is purely a documentation improvement to help users understand what they're seeing without needing to dig through the community thread.
3 Likes
Device Health Monitor v1.4.6
Two bug fixes.
Fix 1 — State Attribute Overrides missing devices on fresh hubs
Presence/Life360, locks, water sensors, smoke/CO, contact, and motion devices were being excluded from the Protocol & State Overrides page if they only had one attribute populated. On an established hub this rarely surfaced — but on a fresh install or newly paired device, currentStates hasn't fully populated yet and those devices silently dropped off the list.
- Attribute detection now also scans declared capabilities, so newly paired devices appear correctly before they've reported a value
- Known single-primary-attribute types (presence, locks, water, smoke, contact, motion, valves) now always appear in the override list regardless of what's populated
Fix 2 — Notifications section collapsing when toggling Enable Notifications
Toggling Enable Notifications caused the section to snap closed, requiring you to reopen it every time you changed a setting. The section now stays open through re-renders. Sub-inputs still show and hide correctly when the toggle is flipped.
No functional changes — health scoring, scan logic, protocol detection, and all pages work exactly as before.
2 Likes
