Skip to content

0.23.18, Bug Fixes For Damaged or Erroneous Data

Pre-release
Pre-release

Choose a tag to compare

View all tags
@TheThinkingHome TheThinkingHome released this 29 Sep 23:08
· 83 commits to main since this release
0.23.18
aa38a3c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Fixed

  • Device Sentinel starts even with damaged saved data. It checks each saved value as it loads and saves, and repairs anything impossible, such as a date billions of years away. Before, one bad value could stop it starting.
  • Your Daily Brief and reports arrive even when one report fails. Device Sentinel writes each reportand logs any that fails.
  • Batteries that count to 200 show the right percentage. Some Zigbee devices report 178 to mean 89%. Device Sentinel spots them after two days of readings over 110, keeps their history, and checks again after each battery change or firmware update.
  • Reports show a very long silence as "more than 180 days", or whatever length of history you keep, instead of a figure Device Sentinel can't measure.
  • The rhythm comparison report tells you what happened. It says when the system clock was reset, and it keeps the name of a device you remove.

What You Will See

A device that showed a battery over 100% shows its real percentage.

Assets 2
Loading