# Run update configuration node via shell command

**URL:** <https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996>\
**Category:** General\
**Created:** [3 September 2023 10:41 UTC](https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996 "2023-09-03T10:41:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![khfischbach](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/khfischbach/32/16627_2.png) [@khfischbach](https://discourse.nodered.org/u/khfischbach)\
**Post date:** [3 September 2023 10:41 UTC](https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996/1 "2023-09-03T10:41:11Z")

</div>

Hi,  
is there a way to update a configuration node via a shell command?  
Reason:  
I have some configuation nodes like FRITZ!Box which sometimes lose connection and they need to get restarted/update manually before working again.

Therefore I would like to restart/update the configuration node from outside node red.

Thanks

---

<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:** [4 September 2023 09:49 UTC](https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996/2 "2023-09-04T09:49:01Z")

</div>

I am not aware of how you can do that other than restarting node-red.

Have you submitted bug reports against the nodes?

---

<div class="post-metadata">

**Author:** ![khfischbach](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/khfischbach/32/16627_2.png) [@khfischbach](https://discourse.nodered.org/u/khfischbach)\
**Post date:** [6 September 2023 06:29 UTC](https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996/3 "2023-09-06T06:29:28Z")

</div>

no, not so far. I was looking for some way to restart node red e.g. from a browser but failed so far with this approach.  
Since I am working with a CCU3 the browser access to the node red console to run a restart only works through the ccu3 GUI (as far as I know) - but since I am in this situation on my Mobile this is not the way I would like to go.  
I am still testing some things.  
Thanks for help!

---

<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:** [6 September 2023 06:47 UTC](https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996/4 "2023-09-06T06:47:53Z")

</div>

Do you mean that node red is running in the ccu3?

Is that [CCU3 Rain & Remote Window Control - Teal Products](https://tealproducts.com/product/rain-remote-window-control-ccu3)

---

<div class="post-metadata">

**Author:** ![khfischbach](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/khfischbach/32/16627_2.png) [@khfischbach](https://discourse.nodered.org/u/khfischbach)\
**Post date:** [13 September 2023 07:27 UTC](https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996/5 "2023-09-13T07:27:07Z")

</div>

yes, node red is running as plugin inside a homematic CCU3.

Thanks for the link. I will look into it in more detail later.

Anyhow: **The issue can be closed**. I found out I always have to do a full deployment insted only to deploy the changed flows. This is listed as a hint in some nodes I use. That was the reason why sometimes it worked and sometime lost connection.

---

<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:** [27 September 2023 07:28 UTC](https://discourse.nodered.org/t/run-update-configuration-node-via-shell-command/80996/6 "2023-09-27T07:28:01Z")

</div>

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