-
-
Notifications
You must be signed in to change notification settings - Fork 28.6k
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
Recorder breaks on: UnicodeEncodeError: 'charmap' codec can't encode character '\u0151' #76436
Comments
recorder documentation |
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( |
the display of the text file above that broke the system might have been a coincidence.
and I will post there too, but even so, Home Assistant shouldn't break/run into trouble because of a single character. |
currently 2022.8.4 new experience: total breakdown, processor up to tops, temp mini pc nearing 80C..
device in DB https://devices.zwave-js.io/?jumpTo=0x015f:0x0901:0x3102:0.0 all because of a ZwaveJS device inclusion of an MCO Multilevel sensor for humid/temp/Co2
log running into 740Mb... continuous restarts. total catastrophe. please have a look? this can not be true Recorder choking on core inclusion of devices |
I don't know if it is a coincidence but I had lots of errors with Mariadb from the August beta and beyond. I switched to the built in sql for now and no issues since. If you are using Mariadb, maybe try temporarily using the built in one and see if they stop. |
Yes, I noticed that. |
Did you save the giant log? It would be helpful to get at least a few megs of it to see why its stuck |
heck, no.... sorry.. it was mostly filled with:
in endless lines. Doesnt the above logging give a clue? Seems quite explicit about the unexcepted char mapping ? |
I am interested in why it didn't move on and kept repeating. |
Sure. I understand. Yet I don't dare to repeat the inclusion... it was a horrifying experience I could get out of by mere chance... |
It should have logged once, and moved on. Where can I buy one of the problem devices? |
they are quite expensive devices..... mine is an older version (been measuring nicely for over 5 years now). It's back on the former Hub for now, although Id love to integrate it into HA zwave again. |
I'm afraid I won't be able to help with this one since the device uses EU zwave frequencies so I wouldn't be able to get a good test setup |
I had simillar issues when recently updating, my MySQL recorder configuration was missing So I would certainly check whatever your MariaDB configuration has the extra charset param in there. Recorder docs do have it for mariadb so might be it? |
O that might well be yes. Great suggestion. Thx. I don't use any of that suffixes in the auth string. Nick, would you also believe that to be required? Must confess I haven't touched that in years, so if a change was introduced, I certainly missed that. It would also be good to have some explanation as to the why in that case, because for me that auth string is just a copy and paste. And not anything I truly understand .... using:
but no idea why this is omitting pymysql and if we should do that |
This solved it for me: |
You definitely need a four byte character set in order to store emoji characters |
If you had the wrong String when your tables were created they are in the wrong charset |
Really sorry but I don't have a The adapted db url string, the charmap code, or the recorded db. Or even Is there a way to be sure and start afresh? Feels a bit like guessing right now. |
Or if you want the short version |
Btw is this related? |
Closing this as the recorder no longer throws an issue on the charmap. will open a new issue though on memory usage. The spikes didn’t go away when away from home, and, while back at home, are replaced by continuous increase of memory. |
The problem
system halted/restarted upon below error
This is an error on recorder choking on certain Unicode characters, which are created by various integrations so it seems.
very serious, as it completely breaks the system, which gets in an endless loop of overheating/memory and processor overload and consequent restarts.
What version of Home Assistant Core has the issue?
2022.8.2
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
Recorder
Link to integration documentation on our website
https://www.home-assistant.io/integrations/recorder/
Diagnostics information
No response
Example YAML snippet
endless repeated logging of:
home-assistant.log.1 shows never seen lines like:
Additional information
pardon the edit, but Ive taken out the irrelevent first impressions, as they turned out to be coincidental.
The text was updated successfully, but these errors were encountered: