klipper-led_effect VS print_area_bed_mesh

Hello group. I have a question about neopixels. On my Marlin setup I defined Neopixel and Neopixel2. All LEDs ran off of the same pin. I was looking at this example. https://github.com/julianschill/klipper-led_effect/blob/master/docs/LED_Effect.md On this it shows 3 separate pins. So now I am confused. Can someone please explain to me how this works. I am just a beginner at this.

Neopixel Led’s: https://github.com/julianschill/klipper-led_effect

However, it is possible using klipper_led-effect

I'd suggest playing around with that until you feel like you are comfortable with it, and then if you want to start looking into animations and such you can check out klipper-led_effect. Just be warned (IMO) it's kind of confusing to configure.

These macros

LED Effects GitHUB

Yeah as a matter of fact klipper-led_effect literally just added this option yesterday.

Ok cool. What I'm trying to do is to add a Neopixel ring to the underside of my build plate (don't worry, I've already sorted out thermal insulation so they don't burn) and have it change colour automatically based off certain parameters. I want it white and breathing slowly when it turns on, changing from blue to red while it's heating and between 30⁰ and 60⁰, then breathing red while it prints. Finally it would turn green upon the print completing, and then go in reverse order from red to blue and back to white as the bed cools and lands below 30⁰. I've been researching this shit all day and have started to build a led_progress.cfg as instructed by this page, however, according to this page I can have all kinds of control over the lights.

A macro that only probes the bed area that you are printing in aka dynamic bed mesh probing! https://github.com/Turge08/print_area_bed_mesh

Well i just wanted to use this bed mesh plugin https://github.com/Turge08/print_area_bed_mesh

print_area_bed_mesh GitHUB

Unparsed config option 'origin: https://github.com/Turge08/print_area_bed_mesh.git' detected in section [update_manager print_area_bed_mesh]. This may be an option no longer available or could be the result of a module that failed to load. In the future this will result in a startup error.

Gives this a try, it wont fix your problem but auto adjust your probed area to your print area. https://github.com/Turge08/print_area_bed_mesh

If you want to get fancy with it, check out this little gem: print_area_bed_mesh

By print_size_mesh, do you mean this macro? https://github.com/Turge08/print_area_bed_mesh

My main reason to start using it was because of a macro (not this one, but it's a better one) that only generates a mesh for the area you will be printing in. It can also reuse meshes if the new mesh is the same size or smaller than the last. Of course you can just generate one mesh and run with it for awhile, but I like having as fresh a mesh as I can and this saves time.