@truglodite wrote:
I recently started playing with themes. I copied some theme yaml’s to my themes folder, a background image to my www/ folder, and use an automation to select dark/light themes. This mostly seems to be working well, however I keep getting these recorder error logs:
2020-02-09 09:16:51 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (MySQLdb._exceptions.DataError) (1406, "Data too long for column 'event_data' at row 1") [SQL: INSERT INTO events (event_type, event_data, origin, time_fired, created, context_id, context_user_id) VALUES (%s, %s, %s, %s, %s, %s, %s)] [parameters: ('themes_updated', '{"themes": {"Google Dark Theme": {"background": "center / cover no-repeat url(\\"/local/img/dark.jpg\\") fixed", "app-header-background-color": "#171 ... (573927 characters truncated) ... "mcg-title-letter-spacing": ".15em", "mini-media-player-base-color": "white", "mini-media-player-icon-color": "white"}}, "default_theme": "vintage"}', 'LOCAL', datetime.datetime(2020, 2, 9, 17, 16, 32, 990993, tzinfo=<UTC>), datetime.datetime(2020, 2, 9, 17, 16, 51, 279297), 'c1824500e2e44efa947b927b84bc3ffc', None)] (Background on this error at: http://sqlalche.me/e/9h9h) 2020-02-09 09:16:51 ERROR (Recorder) [homeassistant.components.recorder] Error saving event: <Event themes_updated[L]: themes=Google Dark Theme=background=center ...cropped massive error output containing theme info and related errors, as it seemed uneeded...
Looks like the recorder is trying to write theme changes to database, and the data is massive so of course I get an error. In attempts to fix this, my recorder.yaml has:
exclude: domains: - automation entities: - automation.set_ha_theme_for_day_and_night include: domains: - person - binary_sensor - switch - light - input_boolean entities: - blah blah blah... no automation or theme related stuff below (individual sensors mostly)
It still appears the recorder is trying to record things related to theme switching, and I’m not sure how to stop it. I wouldn’t mind like logging just the triggering of the automation (without all the theme data), but that isn’t really needed. I mainly want to stop the massive error logs, and potential resource issues related to this recorder behavior. Any hints on what I’m doing wrong?
Posts: 3
Participants: 2