Skip to content
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

stg_cur not in message - lights_report not in message #26

Open
rajgoyal00 opened this issue Feb 4, 2024 · 3 comments
Open

stg_cur not in message - lights_report not in message #26

rajgoyal00 opened this issue Feb 4, 2024 · 3 comments

Comments

@rajgoyal00
Copy link

Receiving the above error in logs. The RGB cycle keeps on cycling LEDs

@CreasaBE
Copy link

CreasaBE commented Feb 7, 2024

same as the issue I logged beginning of Jan: #19

@DutchDevelop
Copy link
Owner

@rajgoyal00 i dont see any logs attached.

@wile1411
Copy link
Contributor

I don't see any error logs either
Noting thatthe RGB cycle doesn't really listen to the MQTT messages as it just cycles the colors regardless.

Some work on the code was recently completed by a community member
Check the latest BLLC_19.3.24.bin version from official site https://www.dutchdevelop.com/bl-led-controller/

The 'not in message' errors weren't related to the BLLED function, but seems to be added to know what was happening in the processing of the MQTT messages. They were specifically referencing the gcode instructions that the printer spits out during the setup process (eg bed leveling). They were recently filtered out to make the logs cleaner as the only message type requires was 'push_status'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants