Continuous MQTT & Lower Startup Brightness#44
Merged
DutchDevelop merged 1 commit intoDutchDevelop:mainfrom Apr 1, 2024
Merged
Conversation
aerodomigue
pushed a commit
to aerodomigue/BLLEDController
that referenced
this pull request
Jul 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With people reporting flickering lights on start, I suspect 1 or two likely causes:
underpowered PS or large draws from whatever LED strip is being used.
In order to reduce occurrences, I reduces the default brightness to 20%. <- you may want to test they yourself to see if you want to change before commiting a new release. 20% is still plenty bright for me.
I also change the start up sequence LED to be 100,100,100,100,100 (instead of all 255) in case of the same problem
Errors casued due to MQTT timeout.
Changed the maintenance mode / test color / RGB cycle logic so it doesn't skip the MQTT loop. Errors appear if the BLLED client doesn't keep up with the MQTT subscription by mqttClient.loop();
The printer eventually drops the MQTT connection after ~20 seconds on no acknowledgement from the BLLED.
Reworked logic now still accepts any new MQTT messages, but doesn't process the content for state changes, unless in replicate state mode.