You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 settingconst.KEY_STATE: False
inHyperHDRPriorityLight
as you do inHyperHDRLight
.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
The text was updated successfully, but these errors were encountered: