Hey there! I'm a bit clueless and hope you may be able to help me. It concerns one of my nodes, node-red-contrib-smarthome-powerswitch. It's something pretty simple. Until now, the output's topic was always command and the payload either boolean true or false. So in the HTML file, I added: RED.nod…

Hi, Should be: $('#node-input-outputPayloadOff').val('false'); //or $('#node-input-outputPayloadOff').typedInput('value', 'false'); EDIT: It's a string

[image] danube: RED.nodes.registerType('powerswitch',{ category: 'Smart Home', color: '#C0DEED', defaults: { ... outputPayloadOnType: {value: "bool"}, outputPayloadOn: {value: true}, outputPayloadOffType: {value: "bool"}, outputPayloadOff: {val…

@GogoVega with "updating" I mean updating from a previous node version (1.0.10) to a newer one (1.1.0). Where the new version contains configuration parameters outputPayloadOn and outputPayloadOff which simply did not exist in the previous version but have been introduced in the new version. Both o…

If you add a new node, is Off Payload still true?

I should have mentioned that already, cause that seems to be a point... If I add it as a new node from the palette, outputPayloadOff indeed is false. Hence, this seems to affect only existing (and so, updated) nodes.

If outputPayloadOn is a new property, you don't have to do anything, the default value will be used. But you can check if node.outputPayloadOn exists then act accordingly I believe your value is true because you tested in dev, so you added this value to your node

[image] GogoVega: If outputPayloadOn is a new property, you don't have to do anything, the default value will be used. The thing is, this seems not to be true! The new parameters have both been given a default value. outputPayloadOn: {value: true}, outputPayloadOff: {value: false} Now t…

[image] GogoVega: If outputPayloadOn is a new property, you don't have to do anything, the default value will be used Not quite Default values are only applied for newly created nodes introduced into the flow - not for nodes that are already deployed. Defaults are applied when a node is dra…

If there are new properties, the default values (of these properties) will be used but a deployment (and therefore a modification of the node) is necessary. You can test it by exporting your node: look before then after modifying it.

No. Defaults are only used when a new node has not had its configuration written yet. Here is an example. Drag in a delay node you can see the default is 5 seconds. Import the below. Its a delay node where it doesn't have (lets pretend a timeout set) - I removed it from the JSON [{"id":"e041bf…

Strange, need to check why :thinking: So check if node.outputPayloadOn exists then set value

Node config parameter not following default value

Developing Nodes

marcus-j-davies 4 December 2023 09:13 16

This has transitioned to a Feature Request for further discussion.

FR: Populate default value to new node property even if the node already exists - Core Development / Feature Requests - Node-RED Forum (nodered.org)

Topic		Replies	Views
FR: Populate default value to new node property even if the node already exists Feature Requests editor	12	270	4 December 2023
Issue: new node properties don't show up after upgrade General	8	392	11 August 2022
Node-Red don´t set node properties default values on load Developing Nodes	8	1249	21 February 2021
Upgrading Nodes specifically my own Developing Nodes	21	2588	25 June 2021
Access discontinued parameters Developing Nodes	16	327	20 January 2024

Node config parameter not following default value

Related topics