Nodered keeps restarting due to Philips Hue scenes not found

General
1

The log output (Docker instance):

nodered  | 17 Mar 08:45:46 - [red] Uncaught Exception:
nodered  | 17 Mar 08:45:46 - [error] Error: Philips Hue: 3, resource, /scenes/DpwCyRUaE1M0Pza, not available
nodered  |     at /data/node_modules/huejay/lib/Transport.js:88:17
nodered  |     at processTicksAndRejections (node:internal/process/task_queues:96:5)

The result is I cannot update the Flow as NodeRed is continuously restarting.

2

Welcome to the forum @JGoor

Assuming you are not using a Docker install then you can start node-red in safe mode, where it loads the editor but does not start the flows, using the command
node-red --safe
then you can fix the flow and when you deploy it will start it running. You will need to stop node-red first, how to do that depends on how you installed and run it. Possibly the command
node-red-stop
will stop it.

If you are running Docker then the technique for starting in safe mode is different.

3

Hi Colin - Thanks for pointing out the safe mode. Was not aware of that.

The solution was putting the following in the 'docker-compose.yaml'- file:

    environment:
      - NODE_RED_ENABLE_SAFE_MODE="true"

Regards,
John

2 Likes
4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.