Another trigger

[Callahan78]

I am pretty new to Node Red and I am getting nowhere even though I have tried many times.
I have reproduced the example program and it works.
Now I want to customize it for my needs and replace the web socket trigger with an "ioBroker in" (trigger on state change). Unfortunately the triggering does not work. Could someone tell me what is still missing here?

[ybizeul]

Sorry for the delayed answer.

Best practice is to use the new sd-input and sd-output node-red nodes from node-red-contrib-streamdeck-ws so the flow can manage internal IDs of the different button when they load, and cache it for further use.

If you don't use those nodes, you will have to be careful injecting the right parameters to the websocket message when returning. Those parameters, in particular the context id come from the websocket, which explains you don't have it hen using another trigger.

One way to fix this is to catch all the buttons loading when StreamDeck initializes and cache in a flow variable all the context and settings/id sent alongside the event. Again, that's when the StreamDeck initializes.

Later on, when you need to change a button state, you fetch in that cache what is the context for this button and make sure you add it to the message sent to the StreamDeck.

This is a bit complicated, that's why I created the node-red-contrib-streamdeck-ws module that you can use like this :

Basically you send all messages coming from StreamDeck to sd-input and then use sd-output to sent new states to StreamDeck :

[Callahan78]

Thank you very much for the further hints. I will now see how far I can get with it.

Maybe I'll shortly explain my goal:

Simple example: control a lamp.

Goal 1:
Switching the lamp via stream deck. Here I would probably start with sd-input and then have to change the object state (on/off) in ioBroker.

Goal 2:
I want the stream deck to display the status of the lamp (on/off image in the stream deck). When the status of the lamp changes (whether by stream deck or by other trigger), the right picture should be displayed in stream deck. This is the need I described in my input post.

A later variant of goal 2 is not to change an image in the stream deck, but display a concrete value from an ioBroker object (e.g. a temperature).

If I had a working template for all this, I could create a lot of cool actions for it :-)

[ybizeul]

I don't use ioBroker, but I guess HomeAssistant module is similar. That's basically the example above in my answer, then :

change: 2 rules is like this :

And sd-output SttreamDeck is :

[Callahan78]

I have now installed node-red-contrib-streamdeck-ws. But to be honest, haven't quite understood how to use that to achieve my goal.
I can't quite interpret your examples either. So I think I need to get more basics in node red to get further here.

[ybizeul]

It is a little bit convoluted indeed. the sd-input node "does" nothing in itself, it's just getting request and caches them in the follow for further use by sd-output. Not sure it makes sense !

[Callahan78]

It surely makes sense, but I don't quite understand it yet ;-)
If I understood it correctly, sd-input/sd-output is only for analysis of the StreamDeck and not for later use in the production script. (?)

[ybizeul]

No they are for production use. Bottomline is : you put a sd-input right after the the websocket node, and use sd-output to update your StreamDeck.