Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Priority not cleared when light.priority turned off. #27

Open
KotBayun69 opened this issue Aug 10, 2024 · 0 comments
Open

Priority not cleared when light.priority turned off. #27

KotBayun69 opened this issue Aug 10, 2024 · 0 comments

Comments

@KotBayun69
Copy link

Version of the custom_component

0.0.07

Describe the bug

When enabling an effect in HyperHDR from Home assistant using light.priority entity, the priority 128 doesn’t clears after the light is turned off and the source with this priority remains active. This prevents switching to USB capture source from Home assistant. To be able to switch to USB capture one should manually do this in HyperHDR fronted e.g. remove the source with priority 128 or switch sources to make USB capture source active.

I am not a programmer, but I looked at the code of the custom_component and figured out you not setting const.KEY_STATE: False in HyperHDRPriorityLight as you do in HyperHDRLight.

If I understand correctly from comments in the code, it was done to “save” the previous state of the light. But if I clear the priority using JSON RPI and turn the light again, it still has all previous settings.

For now I’m using a RESTcommand to clear the priority 128, but it would be nice if you consider to fix it in custom_component

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant