Gladys Assistant 5.1.2: spot the chatty devices đŸ—Łïž

Hello everyone :waving_hand:

Gladys Assistant 5.1.2 is available! A version focused on a recurring topic: database size. You can now see at a glance which devices are filling up the history, and how much space each feature takes up :bar_chart:

:mag: « Devices Â» Page: Identify Chatty Devices

Some devices send their status every few seconds (e.g., a plug that continuously reports its power). If history is enabled, they can alone represent most of your database, without you needing it.

The Devices page now highlights them:

  • A banner indicates how many devices are « very chatty Â» and what share of the last 24 hours’ history they represent.
  • A button allows you to show only these devices, which have a « Very Chatty Â» badge. Hovering over the badge shows the number of recorded states and the features involved.
  • A device is flagged when one of its features records at least 1,440 states in 24 hours, i.e., on average at least one state per minute.

  • A new sort option « Sort by Most Chatty Â» ranks all your devices by the number of states recorded in the last 24 hours.

:floppy_disk: The Size of Each Feature’s History

On a device’s page, next to the « Keep state history? Â» switch, Gladys now displays the number of states stored for each feature and an estimate of the space occupied.

You can immediately see which feature is worth being historized and which takes up a lot of space for little benefit. When you disable the history of a feature, its states are deleted from the database, and the number is updated.

This is available on the device pages of integrations (Zigbee2mqtt, MQTT, external integrations
).

:up_arrow: Gladys Updates: Clearer Errors

When Gladys update failed to download the new Docker image, the error message remained vague. Gladys now displays the real cause:

  • Out of disk space: The message clearly states this and explains how to free up space (e.g., with docker image prune -a, which removes images not used by any container).
  • Download too slow: It is stopped after 15 minutes, without making any changes to your installation.
  • Other error: The error returned by Docker is displayed as is, to allow diagnosis (and to share it with us on the forum if needed :wink:).

:lock: Security

  • The location history of a user, and the API that reports them as present in a house, are now restricted to the user themselves or an administrator.

:hammer_and_wrench: Project Side

  • The repository now has a MAINTAINERS.md file and a CODEOWNERS, and the release workflows are separated.
  • Third-party GitHub actions used by the CI are pinned to a specific version, and the permissions of the jobs are reduced to the bare minimum.

:up_arrow: Update

The update is done as usual from Settings → System, or automatically if you have enabled automatic updates.

:page_facing_up: Full details of the changes: Release v5.1.2 · GladysAssistant/Gladys · GitHub

Feel free to tell us what you find on your installation: which devices are the chattiest for you? :smile:

And thank you all for continuing to report what you encounter :rocket:

Great! Less flashy improvements than previous releases, but a lot of groundwork!!! :+1:

Thank you so much!

However, I realize that I set the detection threshold for „chatty devices“ a bit low: 1440 states per day is just one state per minute, which is still quite normal. I will raise the threshold to one state every 10 seconds (i.e., 8640 per day), which seems more coherent.

Here it is: Raise the verbose device threshold and restyle the banner button by Pierre-Gilles · Pull Request #3140 · GladysAssistant/Gladys · GitHub

It’s fixed in Gladys Assistant v5.1.3, the threshold is now 8640 per day!

This is a good opportunity to see that I have 2 outlets that are quite chatty, I’ll need to reduce the volume on the Zigbee2mqtt side :smiley:

The culprit was easily found in Zigbee2mqtt, thanks Claude :smiley:

I increased the minimum reporting intervals to 60 seconds everywhere, which avoids sending values every 5-10 seconds for nothing

@pierre-gilles Interesting! Question: If you uncheck « keep history Â» for a state in a device, does this indeed delete the history of that state from the database?

Yes, the data is deleted!

I had the same problem with a socket :slight_smile:
Thanks