Split reading components to separate functional parts being overlay and bulb

[bravecobra]

If I understood it correctly during stream, currently there is only one local chat reading component that would then trigger both the overlay color changing and bulb changing part. Both are different components who just happen to have the same input, being the command in the chat.

Adding a chat reading component in Azure would separate the whole bulb part from the overlay part. Both would read the twitch chat as input, thus separating the functional concerns. You could trigger both local and online services without depending on your local service to be running. In the Azure reading component you could build in a safe guard to trigger only when streaming.

So you would want 2 chat readers, one running on Azure and another running locally. Those would spit out events that you can hook into. On the local reader you can hook in the overlay change by subscribing to the chat command event. On the online reader you can hook in the bot-sending by subscribing to the same chat event.
That way the overlays and the light bulb are completely separated and won't influence each other.

Another option would be to read the input from same online event and trigger on that, instead of having a local reader at all.