home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
70.22k stars 29.23k forks source link

Thermobeacon signal_strength entity very chatty #121562

Open Mariusthvdb opened 3 weeks ago

Mariusthvdb commented 3 weeks ago

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:

Scherm­afbeelding 2024-07-08 om 15 44 58

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] commented 3 weeks ago

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)