Automation throwing errors # 254 and #255 with WLED - what are they?

1

So I have a change happening on previously smooth automations.
They are relatively consistent, and I don’t know what they are.

They happen when calling presets with WLED instances, but is new this last week or so?
The WLED instances are normal, stock setups on ESP32 chips.
And the catch? the error does not stop the action-- the action actually fires.
This is happening on more than one automation, and sometimes it is “Error 255”
I ~think~ the action is taking some extra time to fire, but I am not sure.

Here are some traces:

image
image242×587 4.2 KB

image
image
image
image722×107 6.2 KB

I dig the logs in HA, I find nothing.
ANy ideas? What ARE errors 254 and 255?

Data - I run HAOS on LXC under proxmox.
image

2

The recent update requires all wled boards to run at least ver 14.0. Are the boards up to date?

3

great question- I had to check.
They are not up to date, but they are all at least 14.1

4

Is there a list somewhere of what error codes are?
They aren’t just random numbers, right?

6

I just want to note that pretty much every automation or script I have that involves a wled preset returns an error 250 or 254. It actually launches the preset (most of the time), but it does prevent that script from finishing.

7

Hmmmm! I wish I knew what it meant.

And do you know about “continue on error”?
You can yaml it in.
I still put my WLED changes at the end if I can :slight_smile:
image

2 Likes
8

Did anyone make any progress on this? I’m experiencing the same behavior and “continue_on_error” doesn’t see to work

9

I’ve found that the building blocks option of “run these actions in parallel” addresses the issue since it no longer relies on confirmation from WLED that the command was executed prior to moving forward with the next action. However, every command I trigger (even changing the brightness or color of any one of my 12 WLED devices) results in an “error: XXX - failed to ____________”.

1 Like