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
WLED/Led_effect implementation #142
Comments
There is currently no management of WLED in Klippain. But as everything is customization, I would say it's possible to do it: my recommendation would be to override the |
thank you for the reply! :) So, a quick way to do this would be to add this to add this in override:
and change this in variables:
it will then use preset value for caselight on my WLED instead of RGB value? am i on the right path? |
this is where I am so far. I hope I am on the right track, but I am having a hard time figuring out how to get my WLED_ON macro to pull the number from my chamber variable and use it for preset. I'm really bad with variables, especially since this original one is a bit tricky since it accommodates a lot of different setups i tried to copy how it was done for caselight, but change "color" to "preset" in override and just use the single number set in my variable config file instead of an rgb string
in variables I did this:
|
Hey how is it going? Did you managed to make it work? I just had a look at your macros and it looks ok to me. At least it's how I would do it myself :) |
Hi! Unfortunately, it is not reading the variable I am using for preset. Not sure if I need " or ' or {} around the single number? |
UndefinedError: dict object has no element Undefined |
have you completed it or do you have still issues? |
i'm stuck. was never able to figure out how to feed the variable properly |
can you put here the whole picture? all gcode and config you use for the implementation? not only snippets |
to summarize -- the goal is to, for example, have STATUS_LEDS COLOR="PRINTING" send the command WLED_ON preset=1, STATUS_LEDS COLOR="BUSY" sends command WLED_ON preset=2, etc. It should pick up the preset number from variables.cfg since i set a variable_status_leds_colors for WLED ('chamber'). For testing, all of my led colors are set to 1. the documentation for using wled is located here https://moonraker.readthedocs.io/en/latest/configuration/#wled If i test wled by sending manual commands or setting a startup preset, it works properly, so i definitely have a connection to it. thank you! attached are my variables.cfg and overrides.cfg files. quoted are my relevant variables.cfg and overrides.cfg changes (excluding motor overrides) for quick reference:
|
I changed the title of this issue to track WLED but also Led_effect integration since it's highly linked and there is still currently no good implementation of this into Klippain... |
I don't have anything for WLED integration, but I am working on BARF and I think I have it configured for the most part. Would you want to create another branch for me to send the PR to to help look over it? |
imho the pr needs major work done |
This is now merged on develop to be released soon :) |
Hi,
Just wondering if you have any ideas how an end user could implement WLED? All of the current lighting calls are baked into the non-modifiable macros and use a specific format. That makes it a bit hard to use overrides (from what I understand) since we wouldn't really need to specify rgb values or use the current format.
WLED allows us to use complex animations and offload the processing to a very inexpensive esp32. All of the setup is done on the esp32 gui.
To use it in klipper, we simply add WLED to moonraker via IP or serial, and call the specific preset that we want (which was created through the WLED interface on the esp32).
For example:
WLED_ON string=chamber preset=1
This would load any complex animations or effects we set up for preset 1 without any extra configuring on the klipper side.
Here is the documentation:
https://moonraker.readthedocs.io/en/latest/configuration/#wled
The text was updated successfully, but these errors were encountered: