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

Platform Capture not enabled after sleep #12

Closed
jangrewe opened this issue Dec 19, 2020 · 2 comments
Closed

Platform Capture not enabled after sleep #12

jangrewe opened this issue Dec 19, 2020 · 2 comments

Comments

@jangrewe
Copy link

jangrewe commented Dec 19, 2020

Hi, thank you for this plugin!

I'm running Hyperion.NG 2.0.0-alpha9 on a Vero 4K+, controlling an WLED instance.
If have ticked the boxes to enable/disable Hyperion, enabled Ambilight for everything except screensaver (because that's what Kodi does on the Vero 4K+, there is no shutdown), and picked "Platform Capture" as the "Component" - so that it's basically always on unless the screensaver is activated (which could be because Kodi is going to sleep).

When sending the Vero 4K+ to sleep, the "Platform Capture" source gets removed from the "Remote Control" -> "Source Selection" table and the LEDs go off, but the the "Capturing Hardware" -> "Instance Capture" -> "Enable platform capture" checkbox is still ticked.
When waking the Vero 4K+ from sleep, the "Platform Capture" source does not get added to "Remote Control" -> "Source Selection" again, and the LEDs stay off.

I can bring the LEDs back by disabling "Capturing Hardware" -> "Instance Capture" -> "Enable platform capture" , saving, enabling "Capturing Hardware" -> "Instance Capture" -> "Enable platform capture", saving again - but that's a bit annoying ;-)

This is the debug log:

2020-12-19 04:50:38.669 T:3398426848  NOTICE: [script.service.hyperion-control] Settings updated!
2020-12-19 04:50:38.670 T:3398426848  NOTICE: [script.service.hyperion-control] Hyperion ip:           127.0.0.1
2020-12-19 04:50:38.670 T:3398426848  NOTICE: [script.service.hyperion-control] Hyperion port:         8090
2020-12-19 04:50:38.670 T:3398426848  NOTICE: [script.service.hyperion-control] Enable H on start:     True
2020-12-19 04:50:38.670 T:3398426848  NOTICE: [script.service.hyperion-control] Disable H on stop:     True
2020-12-19 04:50:38.670 T:3398426848  NOTICE: [script.service.hyperion-control] VideoMode enabled:     False
2020-12-19 04:50:38.671 T:3398426848  NOTICE: [script.service.hyperion-control] Hyperion target comp:  GRABBER
2020-12-19 04:50:38.671 T:3398426848  NOTICE: [script.service.hyperion-control] Screensaver enabled:   False
2020-12-19 04:50:38.671 T:3398426848  NOTICE: [script.service.hyperion-control] Video enabled:         True
2020-12-19 04:50:38.671 T:3398426848  NOTICE: [script.service.hyperion-control] Audio enabled:         True
2020-12-19 04:50:38.671 T:3398426848  NOTICE: [script.service.hyperion-control] Pause enabled:         True
2020-12-19 04:50:38.672 T:3398426848  NOTICE: [script.service.hyperion-control] Menu enabled:          True
2020-12-19 04:50:38.672 T:3398426848  NOTICE: [script.service.hyperion-control] Debug enabled:         True
2020-12-19 04:50:38.672 T:3398426848  NOTICE: [script.service.hyperion-control] ChangelogOnUpdate:     True
2020-12-19 04:50:38.672 T:3398426848  NOTICE: [script.service.hyperion-control] tasks:                 0
@jangrewe
Copy link
Author

I also tested with the updated utils.py (COMP_GRABBER), but then it doesn't work at all.

@jangrewe
Copy link
Author

Another thing that may be unintentional: Disabling the plugin itself also disables the instance in Hyperion. I guess that's a bit overreaching? ;-)

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

2 participants