I know this isn't a huge deal and I could just use underscores, except that I'm positive I did this literally yesterday and now I've no idea how I accomplished it. I'm trying to create the property "heat index" in the global context object, but I've tried the following to no avail: global.set("[\"…

Global variables should be considered just that, a variable rather than a key to a variable. In that case, a space isn't valid so I'm guessing that's why it hasn't been implemented. Just create a variable name without the space and if you need something with a space, add it to that variable as an o…

But you can't use global 'variables' as variables... You can neither assign them nor retrieve them as you would a variable, you must .get() and .set() all context variables or the changes will not persist between nodes. For example, let's string two function nodes together. The first node is: // S…

Inside a function the deprecated way of accessing was context.global.test1 = true Not global.test1 we have always said the editor is NOT a dashboard

I was just following up on some old flows that broke due to a recent upgrade of NR and the no-space-in-context-keys is the cause for breakage. Context keys with spaces used to work just fine and that got broken. I really don't understand why you need to somehow disallow that. Javascript objects can …

@tve I have never set a flow or global base property with a space so I have no idea if this used to be possible but you are correct that it doesnt work in latest change node... [image] function node... flow.set("key with spaces", "the value") [image] Maybe you should raise this as an issue on…

[image] Steve-Mcl: Maybe you should raise this as an issue on gitthub? I initially wasn't sure whether I was hallucinating about the "it used to work part" so I looked in the forum and bumped into this post... I don't want to add yet another github issue if it falls into the "we're not gonna …

They were always marked as invalid (red border) inside the change node. The latest release now properly surfaces config errors up when the dialog is closed.

Marking up the context name as a string seems to work with no errors, although it isn't displayed in the context sidebar. For example "test context works" [context] [{"id":"6bdf9081.09c6b","type":"inject","z":"b3b413d1.05b1b","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"…

Interesting find! Trying to read the "test context works" state in a function node fails: [{"id":"f20fd17d.b0cdd","type":"inject","z":"630bc809.3cefa8","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payload…

More findings: it seems that the context goes out of its way to reject keys with spaces 'cause -, =, ||, even Δ all work fine: [{"id":"717ae0f1.22128","type":"inject","z":"630bc809.3cefa8","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload…

How to set context variables containing spaces?

General

Colin 14 December 2022 14:24 21

Would it not be better to change the friendly names so they don't contain special characters? Otherwise, if the device fails, you will have to change all your flows when you fit a new device, rather than just configuring the original friendly name in Zigbee2MQTT.

Topic		Replies	Views
Saving in global context parses key, breaking on "." shown in JSON General context	36	273	23 April 2026
Global context variables do not display in the Context Sidebar General	113	11409	6 June 2020
NR 4.0.9 globalcontext problem/question General	3	121	13 May 2025
Changing global variable inside the function node General	58	12348	13 March 2019
Global Context being updated when no global.set executed General function-node	18	681	31 January 2023

How to set context variables containing spaces?

Related topics