# Node editing not responsive

**URL:** <https://discourse.nodered.org/t/node-editing-not-responsive/87201>\
**Category:** General\
**Tags:** editor, home-assistant\
**Created:** [12 April 2024 15:52 UTC](https://discourse.nodered.org/t/node-editing-not-responsive/87201 "2024-04-12T15:52:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![CowboyBootsSP](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cowboybootssp/32/90127_2.png) [@CowboyBootsSP](https://discourse.nodered.org/u/CowboyBootsSP)\
**Post date:** [12 April 2024 15:52 UTC](https://discourse.nodered.org/t/node-editing-not-responsive/87201/1 "2024-04-12T15:52:14Z")

</div>

I use Node Red installed as an addon on my home assistant. Now, it's quite often that I double-click on a node to edit it or press Enter but nothing happens. I looked for errors at all sort of logs, but nothing is found. Both, node red and home assistant are up to date to the latest version.  
Sometimes, when I restart the addon, I can edit some simple nodes before it stops responding. I already tried to clear the browser cache and cookies without success.  
Apparently all flows are working as it should be.  
Can you help me to understand what is happening?

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [12 April 2024 16:05 UTC](https://discourse.nodered.org/t/node-editing-not-responsive/87201/2 "2024-04-12T16:05:21Z")

</div>

> [@CowboyBootsSP](#):
>
> Now, it's quite often that I double-click on a node to edit it or press Enter but nothing happens

This is usually due to a misbehaving node.

Open the devtools on your browser the first time it happens - look in the console - there will be an error.

You should let us know which node is causing this so we can fix it or report it to the author.

To get fix node-red editor, a simple browser refresh is all that is required (no need to restart the server)

---

<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:** [12 April 2024 16:11 UTC](https://discourse.nodered.org/t/node-editing-not-responsive/87201/3 "2024-04-12T16:11:38Z")

</div>

If not that, then check the system monitor on the machine running node and the machine running the browser and see if something is hogging the processor.

---

<div class="post-metadata">

**Author:** ![CowboyBootsSP](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cowboybootssp/32/90127_2.png) [@CowboyBootsSP](https://discourse.nodered.org/u/CowboyBootsSP)\
**Post date:** [12 April 2024 18:46 UTC](https://discourse.nodered.org/t/node-editing-not-responsive/87201/4 "2024-04-12T18:46:12Z")

</div>

Thank you very much, Steve!  
I could partially solve the mystery by disabling all flows and restarting one by one until I get The One that is in trouble. Now I must to check one node by one until I figure the problem.

---

<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:** [26 April 2024 18:47 UTC](https://discourse.nodered.org/t/node-editing-not-responsive/87201/5 "2024-04-26T18:47:04Z")

</div>

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