Thermobeacon signal_strength entity very chatty

[Mariusthvdb]

The problem

Trying to find the most frequent state_chages in the system because of this problem in the Frontend (it was suggested it rewrites all of the local storage on state_changes...) Ive found at least the signal_strength entities of this integration and the likes of it like Govee to be very chatty.

Multiple updates per second is no rarity and this is a calm sensor:

Ive tried to disable local polling in the system settings of the integration, but that renders no effect at all.

Seems the integration is too chatty, and maybe this needs some throttling

Ive mainly focussed on the signal_strength, but the other entities of these integrations are also updated very frequently.

What version of Home Assistant Core has the issue?

2024.7.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Thermobeacon Govee

Link to integration documentation on our website

https://www.home-assistant.io/integrations/thermobeacon

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Tbh, I dont understand why this would in fact be an issue myself, or, rephrase, be worse than eg the temp and humidity sensors entities.

If I look at those graphs, they even have more datapoints. I dont record the single_strength entities, opposed to the temp and humidity entities. Maybe that is what causes the graphs of those to be more fluent, than the blocked live history graphs of the signal_strength?

[home-assistant[bot]]

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (thermobeacon) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of thermobeacon can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign thermobeacon Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

thermobeacon documentation thermobeacon source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

keep

[bdraco]

I'm oversimplifying this a bit....

The device decides how often it will send updates (with passive scans).

The bluetooth stack decides how often it sends RSSI updates. It looks like bluez has the threshold hard coded to 8 and there doesn't appear to be a way to change it https://github.com/bluez/bluez/blob/bd7d49d54aa3aa490ebdd67b3dd2317d29213d45/src/device.c#L78

It looks like the only requests about this on the mailing list was ~10 years ago and the request was to do more frequent RSSI updates https://www.spinics.net/lists/linux-bluetooth/msg53347.html

[Mariusthvdb]

so what you are saying this is not in any way configurable or throttleable (is that even a word...?)

thing is we like to mod the color of those entities, just like we have for eg battery level, and for that we need to evaluate the state in a template...... guess you understand why we dont need it to change multiple times per second.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.