This is a bit of a weird one. I've had 2.0.0-alpha.9 up and running for a long time controlled by HomeAssistant automations (using Kodi and time triggers) and it's been working flawlessly.
Now after moving I ran into issues, without changing any software, where calls from HA automations only work about 50% of the time. I've updated to 2.0.13 and latest HA but the same issue remains.
The problem seems to be that priority handling is very inconsistent and the HA source randomly getting removed for no apparent reason. For example I have an automation that turns screen capture on when starting playback in Kodi and then turns on an effect on stop. This is what happens when starting playback:
2022-09-20T20:16:50.582Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:359:updatePriorities()) Removed source priority 128
2022-09-20T20:16:50.582Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:422:updatePriorities()) Set visible priority to 250
2022-09-20T20:16:50.583Z [SMOOTHING|First LED Hardware instance] (DEBUG) (LinearColorSmoothing.cpp:683:selectConfig()) [0] - type: Linear, pause: false, settlingTime: 100ms, interval: 25ms (40Hz), delay: 0 frames
2022-09-20T20:16:50.792Z [EFFECTENGINE|First LED Hardware instance] (INFO) Effect [Sea waves] finished
Source priority 128 is set in HomeAssistant (in this case Sea waves was running before starting playback).
On stop (when it works as intended):
2022-09-20T20:14:12.362Z [EFFECTENGINE|First LED Hardware instance] (INFO) Run effect "Sea waves" on channel 128
2022-09-20T20:14:12.362Z [EFFECTENGINE|First LED Hardware instance] (DEBUG) (EffectEngine.cpp:206:runEffectScript()) Start the effect: name [Sea waves]
2022-09-20T20:14:12.362Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:182:registerInput()) Reuse input 'Home Assistant@::ffff:192.168.1.4/EFFECT' (Sea waves) with priority 128
2022-09-20T20:14:12.583Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:422:updatePriorities()) Set visible priority to 128
2022-09-20T20:14:12.584Z [SMOOTHING|First LED Hardware instance] (DEBUG) (LinearColorSmoothing.cpp:683:selectConfig()) [6] - type: Linear, pause: false, settlingTime: 200ms, interval: 40ms (25Hz), delay: 0 frames
Here the effect is restarted again on stop and everything works as expected. But now about 50% of the time instead I get:
2022-09-20T20:12:58.536Z [EFFECTENGINE|First LED Hardware instance] (INFO) Run effect "Sea waves" on channel 128
2022-09-20T20:12:58.536Z [EFFECTENGINE|First LED Hardware instance] (DEBUG) (EffectEngine.cpp:206:runEffectScript()) Start the effect: name [Sea waves]
2022-09-20T20:12:58.536Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:182:registerInput()) Reuse input 'Home Assistant@::ffff:192.168.1.4/EFFECT' (Sea waves) with priority 128
2022-09-20T20:12:58.582Z [MUXER|First LED Hardware instance] (DEBUG) (PriorityMuxer.cpp:359:updatePriorities()) Removed source priority 128
Here the source is immediately removed again and I have no idea why. It seems completely random.