Unexpected/unknown effect in HyperHDR from HA

[firstone]

Version of the custom_component

0.0.7

Describe the bug

Everything works but in HyperHDR I get a source that says Home Assistant Effect with priority of 128, which is above capture card. I don't know where it comes from. There is nothing in HA logs related to that.

Debug log

2025-02-03 14:00:08.700 DEBUG (MainThread) [hyperhdr.client] Send to server (192.168.13.10:19444): b'{"command": "componentstate", "componentstate": {"component": "ALL", "state": true}}\n'
2025-02-03 14:00:08.701 DEBUG (MainThread) [hyperhdr.client] Send to server (192.168.13.10:19444): b'{"command": "componentstate", "componentstate": {"component": "LEDDEVICE", "state": true}}\n'
2025-02-03 14:00:08.701 DEBUG (MainThread) [hyperhdr.client] Send to server (192.168.13.10:19444): b'{"command": "clear", "priority": 128}\n'
2025-02-03 14:00:08.701 DEBUG (MainThread) [hyperhdr.client] Send to server (192.168.13.10:19444): b'{"command": "effect", "effect": {"name": "Rainbow swirl fast"}, "origin": "Home Assistant", "priority": 128}\n'
2025-02-03 14:00:08.701 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"componentstate","success":true,"tan":0}\n'
2025-02-03 14:00:08.701 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"componentstate","success":true,"tan":0}\n'
2025-02-03 14:00:08.701 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"clear","success":true,"tan":0}\n'
2025-02-03 14:00:08.742 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"effect","success":true,"tan":0}\n'
2025-02-03 14:00:08.742 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"priorities-update","data":{"priorities":[{"active":true,"componentId":"EFFECT","origin":"Home Assistant@::ffff:192.168.13.2","owner":"Rainbow swirl fast","priority":128,"visible":true},{"active":false,"componentId":"VIDEOGRABBER","origin":"System","owner":"USB3.0 Capture: USB3.0 Capture (video0)","priority":240,"visible":false},{"active":true,"componentId":"EFFECT","origin":"System","owner":"Rainbow swirl fast","priority":254,"visible":false}],"priorities_autoselect":true}}\n'
2025-02-03 14:00:08.861 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"components-update","data":{"enabled":true,"name":"LEDDEVICE"}}\n'
2025-02-03 14:01:52.725 DEBUG (MainThread) [hyperhdr.client] Send to server (192.168.13.10:19444): b'{"command": "componentstate", "componentstate": {"component": "LEDDEVICE", "state": false}}\n'
2025-02-03 14:01:52.726 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"componentstate","success":true,"tan":0}\n'
2025-02-03 14:01:52.875 DEBUG (MainThread) [hyperhdr.client] Read from server (192.168.13.10:19444): b'{"command":"components-update","data":{"enabled":false,"name":"LEDDEVICE"}}\n'

EDIT: It seems to be created simply by sending On command when USB capture card is idle / screen is off. The problem is that it stays there with higher priority and simply overrides everything until I go into HyperHDR screen and delete it.

[t3rral33t]

Cant you change the priority of your USB grabber to be lower than 128?

[firstone]

It was just totally unexpected and, frankly, seems wrong.

I would expect On command to be just that. There's separate "Set Effect" that sets effect. Would be consistent with other color lights.

I've also discovered I can remove this override by sending "Set Effect USB Capture", so between chanting priority and that, I'm ok.

Close if you want to stay with this behavior.

Thank you for awesome work regardless.