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

FeatureRequest: Shutdown Delay for wled controller #1740

Open
LeLunZ opened this issue May 15, 2024 · 6 comments
Open

FeatureRequest: Shutdown Delay for wled controller #1740

LeLunZ opened this issue May 15, 2024 · 6 comments

Comments

@LeLunZ
Copy link

LeLunZ commented May 15, 2024

Feature request

Currently, when using Hyperion with WLED controller type, there's no built-in mechanism to delay the termination of the realtime connection. This causes issues when switching between sources on a TV or when switching between HDR/Dolby Vision and normal content, leading to unintended shutdown of LEDs connected via WLED.

What problem does this feature solve?

This delay would provide a buffer period for detecting and handling temporary signal interruptions without prematurely shutting down the LEDs and not having a relay disconnect and reconnect within a second.

What does the proposed API look like?

/

How should this be implemented in your opinion?

Introduce a new setting in Hyperion that allows users to specify a delay before the termination of the realtime connection with WLED. This delay would provide a buffer period for detecting and handling temporary signal interruptions without prematurely shutting down the LEDs.

Are you willing to work on this yourself?

Not sure, haven't really worked with c++.

@Thinner77
Copy link
Contributor

Thinner77 commented May 16, 2024

Hi,

i'm guessing you're using USB Capture with signal-detection enabled. Try to increase "Signal Counter Threshold", default is 200 frames, for FPS=25 it means 8 seconds. You have to change settings-level in WebUI to "Expert" to see this setting.

wbr

@LeLunZ
Copy link
Author

LeLunZ commented May 16, 2024

No i am actually not using Signal detection. And that’s the reason why it’s instantly turning off the LEDs.

I have one of these USB Capture Cards that really stop sending the signal. Like they should xD (In Live view I see the default Hyperion Logo)

@Lord-Grey
Copy link
Collaborator

Lord-Grey commented May 17, 2024

As a workaround you might want to create a background effect or background effect (color e.g. black) that would kick in when there is no source.
That will avoid that the LEDs are turned off.

@LeLunZ
Copy link
Author

LeLunZ commented May 17, 2024

thx . Do you mean under LED-instances -> Effects -> Background Effect/Color?
But in that case if I then really turn of the TV, they are still "on". Just no color.

It would be nice if such a background effect would be possible to set for a specific duration. Such as the Boot Effect/Color.
Or is there currently a specific effect that can be configured to run only for x amount of time?

@Lord-Grey
Copy link
Collaborator

It depends how you turn off your TV.
Have you tried running hyperiond with CEC?
If you power off the TV you can put Hyperion in suspend mode which will switch off the processing incl. LEDs.

Alternatively, you could put Hyperion into Suspend mode manually or API.

@LeLunZ
Copy link
Author

LeLunZ commented May 26, 2024

👍 CEC is a cool suggestion. I will try to look into that in the next few days.

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

3 participants