Julian Schill

I tried to fix the problem, but I was very confused about the construction of the deliver_publish function. After some debugging and guesswork I found a working solution (at least...

Use delayed gcode for that. https://www.klipper3d.org/Config_Reference.html?#delayed_gcode

Set autostart to true for the first effect and start the second effect with the delayed_gcode like this: ``` [delayed_gcode startup_effect] initial_duration: 3 gcode: SET_LED_EFFECT EFFECT=first_effect STOP=1 SET_LED_EFFECT EFFECT=second_effect ```

At the moment probably not. You could try out multiplying with a [Stepper ](https://github.com/julianschill/klipper-led_effect/blob/master/docs/LED_Effect.md#stepper) Effect. But I don't think you can achieve the desired behaviour with that. I will keep...

The default on moonraker is "master". So I don't think it needs to be defined.

Try this: https://github.com/Drachenkaetzchen/Voron-Documentation/blob/neopixel/community/howto/drachenkatze/neopixel_guide.md#adding-a-100-ohm-resistor-to-combat-signal-integrity-issues Other than that I suspect a broken wire somewhere. But also LED-Effect creates a lot of traffic. It could be, that it is too much. Try reducing...

My guess would be a problem with the signal integrity. What happens when you switch off the motors?

@burntcoinpurse try updating. In the newest version the effects should mix together. @quicksilverstar Can this be closed?

```[led_effect light] leds: neopixel:chamber_light layers: static 1 1 top (1,1,1) ````

Exactly this is working for me. Which LEDs and which color order are you using?