# Home Assistant Node status DISABLED

**URL:** <https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858>\
**Category:** General\
**Tags:** home-assistant\
**Created:** [22 June 2024 10:52 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858 "2024-06-22T10:52:44Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [22 June 2024 10:52 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/1 "2024-06-22T10:52:44Z")

</div>

V4 of NR  
Latest V of HA

Getting DISABLED node status - The node is not disabled in settings.  
Any ideas....  
The Entity is ok and working elsewhere.  
Never seen this before, error yes, but not DISABLED....

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/d/0d0c716f17eef1148c365740625a9fcb9ce97501.png)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/2/b24dbd853680385ab54682cdfc64767f9810b76f.png)

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [22 June 2024 10:57 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/2 "2024-06-22T10:57:40Z")

</div>

Hi @dougle03

That is not Node RED.  
I have a few disabled Nodes in V4, and they do not show that status.

I feel this is something more on the HA side, then Node RED?

---

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [22 June 2024 11:00 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/3 "2024-06-22T11:00:55Z")

</div>

I thought that too, but I have another instance of NR on 3.1.11 and tried these nodes there and they work fine. I've tried rolling back the main NR instance to 3.1.11 but still get DISABLED.  
I've never seen this status before on my more than 300 HA nodes currently deployed... No info on what it might mean either..  
It's very odd....

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [22 June 2024 11:04 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/4 "2024-06-22T11:04:40Z")

</div>

The status label, is controllable...  
You can set one in a function node for example.

```auto
node.status({fill:"red",shape:"ring",text:"Oh Boy! Error"});

```

![Screenshot 2024-06-22 at 12.02.10](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/c/cc95188b6dff67d621ab23951d985411ab1f9ab1.png)

It seems as if HA is setting that status - why, not sure many will know outside of HA 😞

The status is not a constant - it can be set to whatever the developer of a Node wants

---

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [22 June 2024 11:07 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/5 "2024-06-22T11:07:29Z")

</div>

Perhaps time for a post on the HA forum or the Git for the dev of the nodes. Thanks

---

<div class="post-metadata">

**Author:** ![dpgh947](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dpgh947/32/83842_2.png) [@dpgh947](https://discourse.nodered.org/u/dpgh947)\
**Post date:** [23 June 2024 13:21 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/6 "2024-06-23T13:21:05Z")

</div>

It's the "expose as" field - you can use this to define a switch in HA that enables/disables the node. When you edit a new node it is now defaulting to the first existing switch defined, rather than "none".

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [23 June 2024 15:42 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/7 "2024-06-23T15:42:42Z")

</div>

FWIW - we have just had another report like this : ["Expose as..." field in State Nodes weirdness in Node-RED v4](https://discourse.nodered.org/t/expose-as-field-in-state-nodes-weirdness-in-node-red-v4/88887)

Not being a HA user (like most here), I feel this is a bug on the HA side.

As everything non HA related is acting correctly.

---

<div class="post-metadata">

**Author:** ![dpgh947](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dpgh947/32/83842_2.png) [@dpgh947](https://discourse.nodered.org/u/dpgh947)\
**Post date:** [23 June 2024 16:39 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/8 "2024-06-23T16:39:47Z")

</div>

I think the problem is that "none" used to be at the top of the pulldown list for that field, now it is at the bottom. So every time you edit a node, it is picking whatever comes first in that list. If you edit an old node that was set to none, it is picking the first entry, so if you don't notice and save it, it goes wrong. If you don't save it, it is actually still set to "none" and so still works. If you have explicitly set it to something other than none, it saves that and comes up correct if you go back in to edit.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [23 June 2024 16:54 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/9 "2024-06-23T16:54:31Z")

</div>

Ok - Now I see it.

@knolleary @Steve-Mcl

This might be something to add to the snagging list?  
if this has moved, it does seem to have an unwanted effect.

![Jun-23-2024 17-53-27](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/2/42f3ffd5214da9e234f6424a0f417d3194acb9b1.gif)

The moment something else is changed on the Node - its going to apply

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [23 June 2024 17:24 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/10 "2024-06-23T17:24:50Z")

</div>

Please raise an issue with details.

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [23 June 2024 19:28 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/11 "2024-06-23T19:28:19Z")

</div>

Ok sorry, old code that does not correctly define the select value.  
I will correct that 😉

---

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [23 June 2024 19:36 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/12 "2024-06-23T19:36:10Z")

</div>

All thanks for tracking this down. thought it was me going crazy.  
Can someone that's more adept at writing bug reports do the honors..?  
Many thanks Pete

---

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [23 June 2024 19:38 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/13 "2024-06-23T19:38:52Z")

</div>

> [@dpgh947](#):
>
> When you edit a new node it is now defaulting to the first existing switch defined, rather than "none".

It's also doing it with existing nodes when opened, the default of None changes to, in my case, 'vacatio'.... Not sure where that is coming from, but it's not right for sure.  
Thanks for spotting this, I'd have never noticed it as I never use the Expose as feature in the HA Nodes.

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [23 June 2024 19:41 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/14 "2024-06-23T19:41:42Z")

</div>

Yup.

Its not HA specific.

After I decided to be.. well.. you know... helpful and stuff 😄 , I was able to replicate it also with Nodes that have config inputs

---

<div class="post-metadata">

**Author:** ![dougle03](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dougle03/32/32979_2.png) [@dougle03](https://discourse.nodered.org/u/dougle03)\
**Post date:** [23 June 2024 19:52 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/15 "2024-06-23T19:52:35Z")

</div>

Brilliant, glad it wasn't just me.. lol  
Now I need to go through every other node to see if it also has the problem. I do a lot of edits a day so it's entirely possible I've 'touched' other nodes and not noticed the behaviour... 😢

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [23 June 2024 20:06 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/16 "2024-06-23T20:06:47Z")

</div>

Should be fixed by:

> <https://github.com/node-red/node-red/pull/4788>
>
> \- \[x\] Bugfix (non-breaking change which fixes an issue)
> \- \[\] New feature (non-…breaking change which adds functionality)
> 
> \## Proposed changes
> 
> Fix the config node select value assignment for "none":
> 
> \- Remove old code in \`updateConfigNodeSelect\` that is supposed to assign the select value.
> \- Fix the value assignment of the select which used the label as value.
> 
> More informations on video \[here\](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/9?u=gogovega).
> 
> \## Checklist
> 
> \- \[x\] I have read the \[contribution guidelines\](https://github.com/node-red/node-red/blob/master/CONTRIBUTING.md)
> \- \[\] For non-bugfix PRs, I have discussed this change on the forum/slack team.
> \- \[x\] I have run \`npm run test\` to verify the unit tests pass
> \- \[\] I have added suitable unit tests to cover the new/changed functionality

Sorry, I don't know how we missed it 😕

---

<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:** [7 July 2024 20:07 UTC](https://discourse.nodered.org/t/home-assistant-node-status-disabled/88858/17 "2024-07-07T20:07:41Z")

</div>

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