WLED: utf-8 error #103723
Comments
|
Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) wled documentation |
|
I am seeing this issue as well, and it does not pass messages through in NodeRed, so it is breaking existing flows. Here are additional logs: ` [140463828711232] 'utf-8' codec can't decode byte 0xa4 in position 871: invalid start byte |
|
Maybe "special characters" on preset names? Logger: homeassistant.components.wled Unexpected error fetching wled data: 'utf-8' codec can't decode byte 0xff in position 9540: invalid start byte |
|
I have the same issue. |
|
Same here, I looked everywhere for any out of place characters, but couldn't find any. The issue still persists, but doesn't seem to cause any noticeable errors in the lights. Although, WLED seems to be doing some unexpected things, but that could also be due to my inexperience with the too. |
|
The bigger issue for me is that in NodeRed flows, the error causes the flow not to pass the message to the next node, so it breaks existing flows.... |
|
Yes, the problem with this, is that it breaks automations. |
|
I didn't test it that far, all my automations do is turn on/off a preset on WLED, and that seems to work okay, but there is certainly no node after that. That's probably why I don't see any immediate issues. I will have to test a bit further as I have been exploring the automation options in Node Red recently. |
|
Do you change preset from PC mode? |
|
I do both. When I create new presets, I typically do that in a browser tab on the PC (Chrome on Windows). Then I also setup my automation in HA using the browser, this is where I come across the errors. Sometimes, when I want to fine tune things, I do go outside to the strips and modify my presets on the phone using the WLED Android app. But that doesn't happen often. Btw. I do have spaces in my preset names, do you expect those to cause any issues? |
|
In my case, it has always failed in PC mode... but reimporting the file it works again... |
|
Interesting. I just tested removing the spaces from the preset names, and executed my automations a few times. This error only happens sporadically, and I am not able to reproduce it all the time. After activating my automations about a dozen times, I got the error once. My setup is that I have various presets defined in WLED, and I have several playlists defined. The HA automations then set a playlist or a preset as active. What do you do exactly to reimport the file? |
|
Same setup, but changing some presets and play list appear error... And others:
|
|
Same problem here. Quite often. I see also the same stack trace. @frenck would you be willing to add the catch in the WLED client? |
|
Problem has been fixed in WLED 0.14.1-b3 (see Aircoookie/WLED#3641 ) |
|
Is there a binary for an ESP8266 available for 0.14.1-b3? I don't have a build environment setup for this, would be helpful to have a binary. Alternatively, I can look into setting this up. |
https://github.com/Aircoookie/WLED/releases/download/v0.14.1-b3/WLED_0.14.1-b3_ESP8266.bin |
|
Got it. Thank you so much. |
|
Same problem here Env: esp8266 3.1.2 (2) Also: I can confirm that the same issue is present in the 0.14.1 stable |
|
Latest 2401141 build seems to have fixed this issue on all my esp8266s. |
|
I had the problem even after the upgrade and i fixed it in a simple but drastic way.
Obv you will lose every preset but at least should work again with HA |
|
Just chiming in to say that I am also experiencing this problem on HA version 2024.1.5 and WLED 0.14.1. I have also tried the workaround from @WAPEETY above and still get the log errors and WLED device going unavailable periodically. Logger: homeassistant.components.wled Error fetching wled data: Invalid response from API: (503, {'error': 3}) Logger: homeassistant.components.wled Unexpected error fetching wled data: 'utf-8' codec can't decode byte 0xa1 in position 863: invalid start byte |
go on the webpage of WLED and try to see what JSON is broken |
|
Thanks @WAPEETY but I don't know how to do that. Can you explain further or suggest a guide? |
|
Hi, I had the same bug, but by looking at the WLED config and presets JSON files, I found this in my presets.json...
Can you spot the glitch? ;-) Might want to take a look at your JSON files for any unusual characters. For me, it fixed the error in Home Assistant after a reboot. |
go to the web page of your device -> press |
|
My problems seem to have improved a lot after trying a couple of things but they have not gone away completely. Firstly I erased and re-flashed all my WLED boards as I only have 5 and I am currently not using any presets. Secondly I shutdown a second experimental HA instance which had auto-discovered these devices (my thinking is that maybe ESP8266 boards struggle to support multiple instances). After completing the above all the devices seem a lot more responsive however I am still seeing occasional errors as below:
Logger: homeassistant.components.wled Error fetching wled data: Invalid response from API: (503, {'error': 3})
Logger: homeassistant.components.wled Unexpected error fetching wled data: 'utf-8' codec can't decode byte 0xb3 in position 861: invalid start byte Most of the devices are 1m-5m from an AP and one is about 10m away. In summary things are looking a lot better however there is still something not quite right. |
|
Hy! I got erased my presets one-by-one, and i find the defected one, so it works again, without removing from HA! |
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
issue-triage-workflows
bot
closed this as not planned
The problem
I seem to be having the same issue as reported here: https://github.com/home-assistant/core/issues/89884
Oddly enough, the automation errors out at the same position as in the previous report "861".
I already tried overwriting and saving the file in N++ making sure I am using UTF-8 encoding. After restarting the WLED device and reloading the integration, the automation runs fine once. The second time I run it, I get this error message. I am attaching the Trace here as well. Any suggestions would be greatly appreciated.
trace automation.wled_veterans_day 2023-11-10T00_08_39.176374+00_00.json
What version of Home Assistant Core has the issue?
2023.11.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
Automation for WLED
Link to integration documentation on our website
No response
Diagnostics information
config_entry-wled-42417ce3988da4a034f0b57863c28688.json.txt
Example YAML snippet
Anything in the logs that might be useful for us?
{ "trace": { "last_step": "action/0", "run_id": "aeaa30d2129b2c3158557cb64c65bfe1", "state": "stopped", "script_execution": "error", "timestamp": { "start": "2023-11-10T00:08:39.176374+00:00", "finish": "2023-11-10T00:08:39.408728+00:00" }, "domain": "automation", "item_id": "1698966889024", "error": "'utf-8' codec can't decode byte 0xeb in position 861: invalid continuation byte", "trigger": null, "trace": { "trigger": [ { "path": "trigger", "timestamp": "2023-11-10T00:08:39.176458+00:00", "changed_variables": { "this": { "entity_id": "automation.wled_veterans_day", "state": "on", "attributes": { "id": "1698966889024", "last_triggered": "2023-11-10T00:08:15.411726+00:00", "mode": "single", "current": 0, "friendly_name": "WLED Veterans Day" }, "last_changed": "2023-11-09T23:33:45.028528+00:00", "last_updated": "2023-11-10T00:08:15.569603+00:00", "context": { "id": "01HEV8XMSKMXHERWXSXE0SW1D3", "parent_id": "01HEV8XMSJ6QY6T6Y16DDSVT3P", "user_id": null } }, "trigger": { "platform": null } } } ], "action/0": [ { "path": "action/0", "timestamp": "2023-11-10T00:08:39.179556+00:00", "changed_variables": { "context": { "id": "01HEV8YC0833J4SND4WSGK6YPM", "parent_id": "01HEV8YC07D33SWA471YYNZ60K", "user_id": null } }, "error": "'utf-8' codec can't decode byte 0xeb in position 861: invalid continuation byte" } ] }, "config": { "id": "1698966889024", "alias": "WLED Veterans Day", "description": "Displays Veterans Day light strip 45 minute after sunset. ", "trigger": [ { "platform": "sun", "event": "sunset", "offset": "00:45:00" } ], "condition": [ { "condition": "time", "after": "input_datetime.veterans_day_start", "before": "input_datetime.veterans_day_end", "weekday": [ "sat", "fri", "thu", "wed", "tue", "mon", "sun" ] } ], "action": [ { "device_id": "412c6ec03477ca9b61e1c2d87955ffcb", "domain": "select", "entity_id": "f6aa8b5af55284853e871baf88c8a3fb", "type": "select_option", "option": "VeteransDay" } ], "mode": "single" }, "blueprint_inputs": null, "context": { "id": "01HEV8YC0833J4SND4WSGK6YPM", "parent_id": "01HEV8YC07D33SWA471YYNZ60K", "user_id": null } }, "logbookEntries": [ { "name": "WLED Veterans Day", "message": "triggered", "source": null, "entity_id": "automation.wled_veterans_day", "context_id": "01HEV8YC0833J4SND4WSGK6YPM", "when": 1699574919.176572, "domain": "automation" }, { "when": 1699574919.427214, "state": "VeteransDay", "entity_id": "select.wled_preset", "icon": "mdi:playlist-play", "context_event_type": "automation_triggered", "context_domain": "automation", "context_name": "WLED Veterans Day", "context_message": "triggered", "context_entity_id": "automation.wled_veterans_day" } ] }Additional information
No response
The text was updated successfully, but these errors were encountered: