Skip to content

feat: bus status usermod#3631

Closed
casesolved-co-uk wants to merge 1 commit intowled:mainfrom
casesolved-co-uk:busstatus
Closed

feat: bus status usermod#3631
casesolved-co-uk wants to merge 1 commit intowled:mainfrom
casesolved-co-uk:busstatus

Conversation

@casesolved-co-uk
Copy link
Copy Markdown

@casesolved-co-uk casesolved-co-uk commented Jan 1, 2024

Works roughly similar to the STATUSLED functionality.

Now implemented as an effect usermod, description in the README

@blazoncek
Copy link
Copy Markdown
Contributor

The changes to core functionality are unacceptable just to support usermod unless done wisely with the possibility to be used in other usermods or in core. I do not see such usability here.

@casesolved-co-uk
Copy link
Copy Markdown
Author

The changes to core functionality are unacceptable just to support usermod unless done wisely with the possibility to be used in other usermods or in core. I do not see such usability here.

Could you be more specific and make some suggestions please?

The changes to core functionality are fully backward compatible.

@blazoncek
Copy link
Copy Markdown
Contributor

If you want a status to be displayed on a segment, why bother with all this?

Just make a custom effect function, that can be applied to any segment. You can append your custom effect to regular effects using strip.addEffect() in your setup().

Do not complicate things when they don't need to be complicated. 😉

@blazoncek
Copy link
Copy Markdown
Contributor

Similar to #3574

@blazoncek blazoncek added enhancement usermod usermod related labels Jan 2, 2024
@casesolved-co-uk
Copy link
Copy Markdown
Author

casesolved-co-uk commented Jan 3, 2024

If you want a status to be displayed on a segment, why bother with all this?

Just make a custom effect function, that can be applied to any segment. You can append your custom effect to regular effects using strip.addEffect() in your setup().

Thanks for the tips. How do you suggest I make the segment:

  • Always on, freeze doesn't appear to work when changing another segment
  • Static, for example having the breathe effect on an adjacent segment also makes the status fade even though not selected

@casesolved-co-uk casesolved-co-uk force-pushed the busstatus branch 2 times, most recently from a3136c2 to e553585 Compare January 3, 2024 05:50
@casesolved-co-uk casesolved-co-uk marked this pull request as draft January 3, 2024 05:54
@blazoncek
Copy link
Copy Markdown
Contributor

Just a regular segment with regular (custom) effect applied. But I'm not sure I understand what you want.
And BTW never force push your changes. Do normal commits and normal pushes.

@casesolved-co-uk
Copy link
Copy Markdown
Author

casesolved-co-uk commented Jan 3, 2024

Just a regular segment with regular (custom) effect applied.

This is not true.

  • If you try putting the Breathe and Solid effects on separate segments (and busses), the Solid effect is still faded in and out
  • Freeze of the Solid segment causes it to fade to black

version v0.14.1-b2
Should I start a new bug issue?

@blazoncek
Copy link
Copy Markdown
Contributor

This is not true.

How so? Perhaps I am the only one who knows how WLED works as I wrote the whole damn thing regarding segments, transitions and effect blending. 😁

* If you try putting the Breathe and Solid effects on separate segments (and busses), the Solid effect is still faded in and out

Faded in what way? Are we talking about fading aka transitions or displaying a WLED status (whatever that means to you) on a part of the strip (aka segment)?
If you are talking about transitions (when powering WLED on or off) then yes all segments are transitioned (faded) in and out. When WLED is in off state nothing is displayed on strips except if using STATUSLED (aka setStatusPixel()).
If you are talking about displaying separate content of segments then each and every segment can display separate effect.

* Freeze of the Solid segment causes it to fade to black

Freeze does not do that. It only stops updating segment with effect data.

version v0.14.1-b2 Should I start a new bug issue?

IDK but it looks to me that maybe we are not talking about the same thing.
It will be very difficult to convince me to approve current implementation as I think the "status usermod" could be done without changing WLED core functions.

@casesolved-co-uk
Copy link
Copy Markdown
Author

Faded in what way? Are we talking about fading aka transitions or displaying a WLED status (whatever that means to you) on a part of the strip (aka segment)?

I've posted a video showing the problems. The implementation of this usermod has now been changed to just be an effect as you requested. The issues I'm seeing are part of the core functionality because I used the official release build for the video; it did not include this usermod.

@casesolved-co-uk casesolved-co-uk marked this pull request as ready for review January 3, 2024 22:18
@blazoncek
Copy link
Copy Markdown
Contributor

Hardware (power) issue, not WLED functionality.

@casesolved-co-uk casesolved-co-uk changed the title feat: bus status usermod and related changes to the WLED framework feat: bus status usermod Jan 4, 2024
@softhack007 softhack007 added the rebase needed This PR needs to be re-based to the current development branch label Aug 15, 2024
@softhack007
Copy link
Copy Markdown
Member

softhack007 commented Apr 14, 2026

closing - this PR had no activity since >20 month, its not compatible any more with WLED 16.0.0-beta, and the purpose / added value is not clear to me.

Plus the PR is full of force-pushed commits, and a lot of information seems to be missing/lost from the review history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement rebase needed This PR needs to be re-based to the current development branch usermod usermod related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants