core: Unreliable sensor data (data usage) since firmware 7.50 - filter/block that data

The problem

See

• https://github.com/home-assistant/core/issues/83280 for starting point
• https://github.com/home-assistant/core/issues/83280#issuecomment-1399597517 for follow-up issue and
• https://community.home-assistant.io/t/block-writing-problematic-data-to-the-database-using-sql-trigger-on-ha-database/525021 for a short summary on this issue

Affected entites (possibly renamed):

• sensor.fritzbox_gigabytes_received
• sensor.fritzbox_gigabytes_sent

What version of Home Assistant Core has the issue?

core-2022.12.9

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

AVM FRITZ!Box Tools

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

1. Unfortunately there was no response from integration maintainers (yet) on ideas how to fix this on the integration side @ https://github.com/home-assistant/core/issues/83280#issuecomment-1399597517

2. The other issue has been silently locked and limited to collaborators https://github.com/home-assistant/core/issues/83280#event-8358044112 (which is fine as no development progress was made there) so as promised this is the follow-up issue on that one.

3. One very specific and highly advanced option to “solve” (work around) this issue is noted at https://community.home-assistant.io/t/block-writing-problematic-data-to-the-database-using-sql-trigger-on-ha-database/525021 - currently not more than just an idea.

Hierarchy of fixing:

1. Manufacturer: they wont as stated in https://github.com/home-assistant/core/issues/83280#issuecomment-1400000182
2. Integration: that’s why this issue has been created
3. Individually: Block write attempts using SQL TRIGGER

As 1 is out and everything after 2 is quite complicated and risky, in my opinion the integration is the perfect place to solve this - for all affected users (which are going to increase with continued rollout of the 7.50 release firmware).