Replies: 1 comment 5 replies
-
|
That should work as is, it takes the value when deploying this node. If the value of the global context changes after the node is deployed it will not update the trigger of the node. |
Beta Was this translation helpful? Give feedback.
-
|
I appreciate the response, thank you for confirming. If I try running this by manually specifying the entity, it runs. When I run it using my context, nothing ever activates which is part of the reason I'm unsure if I'm doing this right since I don't have any debug info. State node is same format as original post, just using {{global.basement_leak_sensor}}. Using curly braces in the Input node outputs the correct entity from the context. I've just updated as well to latest ha/node-red/ws-plugin and am running into the same thing.
|
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I was mistaken I was thinking about using environment variables, not mustache templates. |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha, so the node it can't evaluate global context within the mustache templates, but it can with ENVs. Would it evaluate any type of JSONATA with any of the entity filters? Say I have env.LEAK_SENSOR, which format would the state node accept? Whichever I seem to just fail silently as the node state just says 'running'. {{env.NR_NODE_NAME}} |
Beta Was this translation helpful? Give feedback.
-
no
${NR_NODE_NAME} |
Beta Was this translation helpful? Give feedback.
-
|
is it possible to add to this? I'm trying to do something like |
Beta Was this translation helpful? Give feedback.
-
Not sure if this is supported, but it isn't working the way I expected it might. Attached is what I'm hoping to do, take a variable I have defined in global context and fetch the state when changed. Does this get evaluated using any of the entity definition settings?
Using it as {{global.some_entity}} currently, doesn't seem to do anything.
Beta Was this translation helpful? Give feedback.
All reactions