-
-
Notifications
You must be signed in to change notification settings - Fork 396
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
Differentiate between LED-Device Enable/Disable and Switch On/Off #960
Differentiate between LED-Device Enable/Disable and Switch On/Off #960
Conversation
Hello @Lord-Grey 👋 I'm your friendly neighborhood bot and would like to say thank you for So that you and other users can test your changes more quickly, If you make changes to your PR, i create a new link to your workflow artifacts. Best regards, |
Here is your new link to your workflow artifacts. |
Here is your new link to your workflow artifacts. |
Any news when that will be merged into master? |
Here is your new link to your workflow artifacts. |
a4148f7
to
a48684c
Compare
Here is your new link to your workflow artifacts. |
1 similar comment
Here is your new link to your workflow artifacts. |
a48684c
to
d341cf1
Compare
Here is your new link to your workflow artifacts. |
Here is your new link to your workflow artifacts. |
03cd67f
to
50e9084
Compare
@Lord-Grey Is the PR done so far? |
Here is your new link to your workflow artifacts. |
Yes, Let us merge the PR now. |
Here is your new link to your workflow artifacts. |
Summary
Differentiate between LED-Device Enable/Disable and Switch On/Off allows to
switch off LED-Devices output when there is no signal e.g. given no source is available any longer.
In case input is available again, LED-Devices are switched on.
In both cases, the LED-Device shows enabled allowing to differentiate from error state or a suspend/resume scenario.
Currently, switch on/off is implemented, if no source is available (addressing #828).
What kind of change does this PR introduce? (check at least one)
If changing the UI of web configuration, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing setups:
The PR fulfills these requirements:
Fixes: #xxx[,#xxx]
, where "xxx" is the issue number)If adding a new feature, the PR's description includes:
PLEASE DON'T FORGET TO ADD YOUR CHANGES TO CHANGELOG.MD
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:
Fixes: #828