Node-RED management

Node-RED deploy

Each time you do a modification inside the editor, the modification only exists in the editor and must be deployed to the server.

You have to take care of the Deploy button on top right of the screen.

If it is red, it means that modifications must be synchronized, if you press it, a message should pop up at the top saying “Successfully deployed”. Otherwise, an error message is pop up that should help to troubleshoot the issue.

Restarting Node-RED

Whenever you need to restart Node-RED, you can use the service management CLI command.

Accessing Node-RED flow file

In case you encounter issues with Node-Red configuration, making Node-RED UI unreachable (e.g. infinite loop that consume all node CPU) and you have no backup file:

• You may directly connect on the box using the node-red user (password is the one you use to connect on ThingPark Enterprise All-in-One):

  ssh node-red@$BOX_IP

• Enter the node-red-data folder:

  cd $ROOTACT/node-red-data/

• You can edit flows.json and correct the file.

Uploading a file to the Node-RED data folder

• You may directly scp on the box using the node-red user (password is the one you use to connect on ThingPark Enterprise All-in-One), for example, you can upload a modbus-definition.csv file :

  scp ./modbus-definition.csv node-red@$BOX_IP:$ROOTACT/node-red-data/