Need some help with automation

[Nexetion]

this is my current configuration and I'm trying to figure out how make the button title change when the state changes, as of right now it changes when I press it but there are 4 states to the device I'm controlling open, close, closing, and opening. Appreciate any help!

[ybizeul]

Did you make sure that no Title is configured in StreamDeck itself ?

EDIT :

If the title is changing when you push the button, the issue is probably not my first thought.

Now, the documentation probably needs an update, in early releases back when the original version was published, it was a little bit tricky to maintain proper context especially with messages that weren't originated by a key push, and an update sent back to the SD (this scenario is easier to implement, as you have noticed).

If the action is initiated outside of the SD, you needed to send the correct context alongside with the message so the SD knows what key you're targeting, it works by sending a context that is generated within SD that you had to store somehow in a cache.

That's why I implemented two new nodes : sd-input and sd-output.

Make sure you have a sd-input node after the websocket in node, and a sd-output node before websocket out, they will set the flow persistent state with all the keys sending willAppear messages, and retore proper context before sending messages back. Then you can take events out of any source (like HA) and send it straight to sd-output.

I like to have a "master" block that handles input and output, and link to task specific blocks like so :

Hope this helps.

[Nexetion]

How do I add the input? I can't find it in Node-Red/HA

[ybizeul]

That's a Streadeck-WS node that you will find under network if you're up to date.

[Nexetion]

So i would basically create this the same as how you have it in the streamdeck part of the picture?

[ybizeul]

yes, after websocket in you add a sd-input, then you use sd-output to format the message you wish to send to websocket out.

[Nexetion]

I'm either getting a string is undefined for payload.state for the title or context for temp is unknown. Anything I should screen shot to help you, help me?

[Nexetion]

Yeah I don't understand how to get the state of my garage door with this new SD input and output

[ybizeul]

sd-input goes right after websocket in, and keeps going to where you want to catch SD events.

Specifically for what you're asking, you're not using websocket in though, so it's irrelevant except for the fact it's used to record all your keys in the flow cache, so do it anyway.

What you need is send the message with sd-output pushing into it a message, and reference the title property in the window above. Don't put anything in State

[Nexetion]

[ybizeul]

Remove the . before payload.state

[Nexetion]

2/27/2022, 12:36:26 PM[node: 2nd Pay](http://homeassistant.local:8123/api/hassio_ingress/9rLW5uJysh3Bcxjnv_aIRZYvPrFK3cCOFqm2m7B3jU8/#)
msg.payload : string[321]
"{"action":"org.tynsoe.streamdeck.wsproxy.proxy","context":"69F862433908EC0A923E6E87A8340C86","device":"7A9B7F6073A842147791757CB8A0B46F","event":"keyDown","payload":{"coordinates":{"column":4,"row":2},"isInMultiAction":false,"settings":{"id":"button1","remoteServer":"ws://homeassistant.local:1880/endpoint/streamdeck"}}}"
2/27/2022, 12:36:26 PM[node: 2nd Pay](http://homeassistant.local:8123/api/hassio_ingress/9rLW5uJysh3Bcxjnv_aIRZYvPrFK3cCOFqm2m7B3jU8/#)msg.payload : string[319]
"{"action":"org.tynsoe.streamdeck.wsproxy.proxy","context":"69F862433908EC0A923E6E87A8340C86","device":"7A9B7F6073A842147791757CB8A0B46F","event":"keyUp","payload":{"coordinates":{"column":4,"row":2},"isInMultiAction":false,"settings":{"id":"button1","remoteServer":"ws://homeassistant.local:1880/endpoint/streamdeck"}}}"
2/27/2022, 12:36:26 PM[node: Stream Deck](http://homeassistant.local:8123/api/hassio_ingress/9rLW5uJysh3Bcxjnv_aIRZYvPrFK3cCOFqm2m7B3jU8/#)msg : undefined
undefined

[Nexetion]

now i get undefined for msg.payload.state

[ybizeul]

Did you actually pu something in msg.payload.state ?

[Nexetion]

check comment below

[Nexetion]

2/27/2022, 12:39:43 PM[node: Stream Deck](http://homeassistant.local:8123/api/hassio_ingress/9rLW5uJysh3Bcxjnv_aIRZYvPrFK3cCOFqm2m7B3jU8/#)
msg : undefined
undefined
2/27/2022, 12:39:43 PM[node: 3rd Pay](http://homeassistant.local:8123/api/hassio_ingress/9rLW5uJysh3Bcxjnv_aIRZYvPrFK3cCOFqm2m7B3jU8/#)msg.payload.state : string[6]
"closed"

[Nexetion]

Now the question is how do I make the title changed based on the status instead of a keypush.

[ybizeul]

Just start with a HA event: state node and push new state to the sd-output node.
That event: state node would be right below the current state node you already have and probably go into the same sd-output

[Nexetion]

in the state changed how would I sent the context?

[Nexetion]

I have it like this right now.

[ybizeul]

in the state changed how would I sent the context?

You don't have to, that's the beauty of it :-) As long as they key is "known" from a previous message it'll remember it. A previous message would be the willAppear sent when the key was displayed initially. That's the main purpose of having a sd input node in the flow.

[Nexetion]

Whats in the "Music"?

[ybizeul]

The Music switch just checks the value of msg.payload.payload.settings.id and make sure that's the key with the music ID that has been pushed.

[Nexetion]

So how would I change the state on the key when say the garage is opened from my phone or the app on my phone with the state change node correct?

[ybizeul]

Yes, you use an event: state node on the garage door entity, and that goes to a sd-output node where you put the property of the message that stores the door state in the Title field. You can also use a change or function node between to reformat if needed

[Nexetion]

Is there anyway we could do this on discord or you could send me your flow for this somehow?

[ybizeul]

The flow for what ?

[meehab]

I appreciate I'm digging up an old thread here, but I'm struggling a little with this.

@ybizeul It would be really useful to have the flows for the image posted on 27th Feb showing what's referred to as master block and the task specific blocks. Would really help to be able to explore those and click into the nodes rather than just looking at the image.