-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
predbat.plan_html exceed maximum size of 16384 bytes #438
Comments
Have a look at the faq’s, I’ve added details of this issue last week, and how to suppress it
https://springfall2008.github.io/batpred/faq/
Geoffrey
… On 7 Dec 2023, at 13:53, dbrb2 ***@***.***> wrote:
This doesn't seem to cause any real world problems, but seemed worth mentioning - as has been cropping up in the logs a lot:
Logger: homeassistant.components.recorder.db_schema
Source: components/recorder/db_schema.py:582
Integration: Recorder (documentation, issues)
First occurred: 12:07:19 (31 occurrences)
Last logged: 13:50:19
State attributes for predbat.plan_html exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
|
Ah thanks
That didn't quite work for me - I had to specify which logger to filter:
logger:
default: info
filters:
* homeassistant.components.recorder.db_schema:* - "State attributes
for predbat.plan_html exceed maximum size of 16384 bytes. This can cause
database performance issues; Attributes will not be stored"
Seems to work!
On Thu, Dec 7, 2023 at 2:48 PM Geoffrey Coan ***@***.***>
wrote:
… Have a look at the faq’s, I’ve added details of this issue last week, and
how to suppress it
https://springfall2008.github.io/batpred/faq/
Geoffrey
> On 7 Dec 2023, at 13:53, dbrb2 ***@***.***> wrote:
>
>
> This doesn't seem to cause any real world problems, but seemed worth
mentioning - as has been cropping up in the logs a lot:
>
> Logger: homeassistant.components.recorder.db_schema
> Source: components/recorder/db_schema.py:582
> Integration: Recorder (documentation, issues)
> First occurred: 12:07:19 (31 occurrences)
> Last logged: 13:50:19
>
> State attributes for predbat.plan_html exceed maximum size of 16384
bytes. This can cause database performance issues; Attributes will not be
stored
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you are subscribed to this thread.
—
Reply to this email directly, view it on GitHub
<#438 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABFQ46KUFMX72N7XS26CSLYIHJKNAVCNFSM6AAAAABALDFETCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBVGQ3TKOJSHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks @dbrb2 that was my fault, cut and paste error when copying the code from my configuration.yaml across into predbat It was part of a larger filter I had to also remove similar octopus energy warnings, vis: homeassistant.components.recorder.db_schema:
- "State attributes for sensor.octopus_energy_electricity_xxxx_export_current_rate exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored"
- "State attributes for sensor.octopus_energy_electricity_xxxx_current_rate exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored"
- "State attributes for predbat.plan_html exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored"
homeassistant.helpers.entity:
- "Update of sensor.octopus_energy_electricity_xxxx_export_previous_accumulative_cost is taking over 10 seconds"
- "Update of sensor.octopus_energy_electricity_xxxx_previous_accumulative_cost is taking over 10 seconds" and I accidentally deleted the logger line. Corrected in PR #439 |
@springfall2008 think this can be closed now? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This doesn't seem to cause any real world problems, but seemed worth mentioning - as has been cropping up in the logs a lot:
The text was updated successfully, but these errors were encountered: