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

WLED: Fix for next version and add segment parameter #552

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

numanair
Copy link

The upcoming 0.14 version of WLED has some API changes that are incompatible with the current WLED_ON command. Removing the "on" call fixes this.

Additionally, I have added support for applying settings (brightness, intensity, speed) to individual WLED Segments. This enables multiple independent lights on one WLED controller. The parameter ID is zero-indexed, and if it is not provided the setting is applied to all segments on the WLED "strip".

I do wonder if ID is the best name for this parameter, as it is not self explanatory imo. It is just what WLED calls it.

I tried to rebase my commits as I initially left off the sign-off message. I am not sure if I need to do another step there as I don't know git very well.

Add 0-indexed "id" parameter to wled_control for applying settings to different segments.
Add 0-indexed "id" parameter to wled_control for applying settings to different segments.

Signed-off-by: Cole Morris <[email protected]>
Added optional ID parameter to the example macro

Signed-off-by: Cole Morris <[email protected]>
corrected 3 long lines

Signed-off-by: Cole Morris <[email protected]>
@Arksine
Copy link
Owner

Arksine commented Dec 23, 2022

Thanks. One thing we would need to be sure of is that these changes don't break compatibility with previous versions of WLED.

Since this PR includes multiple, unrelated changes to the WLED module its important to break those out into separate commits. One commit for the compatibility fixes, one commit for the addition of the id parameter.

If you are unfamiliar with git my suggestion would be to research its interactive rebase functionality. This can be used to combine/squash multiple commits into a single commit, reorder commits, and reword commit messages. A standard rebase can be used to update the pull request against master without the merge commit. After these changes are it will be necessary to use a force push to update the remote.

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

Successfully merging this pull request may close these issues.

2 participants