# Nodered keeps restarting due to Philips Hue scenes not found

**URL:** <https://discourse.nodered.org/t/nodered-keeps-restarting-due-to-philips-hue-scenes-not-found/76652>\
**Category:** General\
**Tags:** docker\
**Created:** [17 March 2023 07:52 UTC](https://discourse.nodered.org/t/nodered-keeps-restarting-due-to-philips-hue-scenes-not-found/76652 "2023-03-17T07:52:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![JGoor](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jgoor/32/61433_2.png) [@JGoor](https://discourse.nodered.org/u/JGoor)\
**Post date:** [17 March 2023 07:52 UTC](https://discourse.nodered.org/t/nodered-keeps-restarting-due-to-philips-hue-scenes-not-found/76652/1 "2023-03-17T07:52:22Z")

</div>

The log output (Docker instance):

```auto
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.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [17 March 2023 08:31 UTC](https://discourse.nodered.org/t/nodered-keeps-restarting-due-to-philips-hue-scenes-not-found/76652/2 "2023-03-17T08:31:43Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![JGoor](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jgoor/32/61433_2.png) [@JGoor](https://discourse.nodered.org/u/JGoor)\
**Post date:** [17 March 2023 13:12 UTC](https://discourse.nodered.org/t/nodered-keeps-restarting-due-to-philips-hue-scenes-not-found/76652/3 "2023-03-17T13:12:22Z")

</div>

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:

```auto
    environment:
      - NODE_RED_ENABLE_SAFE_MODE="true"

```

Regards,  
John

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [16 May 2023 13:13 UTC](https://discourse.nodered.org/t/nodered-keeps-restarting-due-to-philips-hue-scenes-not-found/76652/4 "2023-05-16T13:13:03Z")

</div>

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