Connection to home assistant shows disconnected since 2023.1.2

[magiva]

Problem/Motivation

No connection to home assistant for the sensor nodes etc

(Why the issue was filed)

Expected behavior

connection to server

(What you expected to happen)

Actual behavior

home assistant nodes show as disconnected

(What actually happened)

Steps to reproduce

viewable in the nodered dashboard as disconnected under each home assistant node

(How can someone else make/see it happen) connected with 2023.1.1, connection fails with updates since then including 2023.1.4

Proposed changes

(If you have a proposed change, workaround or fix, describe the rationale behind it) rollback to 2023.1.1 was the only fix. i rolled back to 2023.1.2 - that didnt work

[magiva]

Current version: 14.0.1 Dashboard: 3.3.1 node-red-contrib-home-assistant-websocket: 0.48.0

no new updates to apply

[canedje]

I did have troubles see other issues. So I decided to remove nodered addon and nodered directory to start from scratch. I was able to startup a new Nodered addon. But not able to get nodered server connected to HA anymore. Nodered addon is now totally useless:

[magiva]

whats mostly concerning is that i, like many and most other people, run their homes with this.
The lack of attention these tickets get is really concerning and very disapointing.

[canedje]

Yes indeed I do think exactly the same. This is already going om for a month without any reaction from anyone. A lot of issues are connected to this. Without NodeRed HA is nothing for me

[magiva]

[12:54:49] INFO: Starting NGinx... 16 Jan 12:54:49 - [info] [mqtt-broker:hass-mqtt] Connected to broker: mqtt://localhost:1883 16 Jan 12:54:54 - [info] [server:Home Assistant] Connecting to http://supervisor/core 16 Jan 12:54:54 - [info] [server:Home Assistant] Connected to http://supervisor/core 16 Jan 12:54:54 - [info] [server:Home Assistant] Connection closed to http://supervisor/core 16 Jan 12:54:54 - [info] [server:Home Assistant] Connection closed to http://supervisor/core 16 Jan 12:54:54 - [debug] [server:Home Assistant] HA State: running 16 Jan 12:54:54 - [debug] [server:Home Assistant] Integration: notloaded

i see after changing log_level to debug, Integration is not loaded

Welcome to Node-RED

16 Jan 15:53:22 - [info] Node-RED version: v3.0.2 16 Jan 15:53:22 - [info] Node.js version: v18.12.1 16 Jan 15:53:22 - [info] Linux 5.15.80 x64 LE 16 Jan 15:53:22 - [info] Loading palette nodes 16 Jan 15:53:25 - [info] Dashboard version 3.3.1 started at /endpoint/ui 16 Jan 15:53:26 - [info] Settings file : /etc/node-red/config.js 16 Jan 15:53:26 - [info] Context store : 'default' [module=memory] 16 Jan 15:53:26 - [info] User directory : /config/node-red/ 16 Jan 15:53:26 - [warn] Projects disabled : editorTheme.projects.enabled=false 16 Jan 15:53:26 - [info] Flows file : /config/node-red/flows.json 16 Jan 15:53:26 - [info] Server now running at http://127.0.0.1:46836/ 16 Jan 15:53:26 - [info] Starting flows [15:53:26] INFO: Starting NGinx... 16 Jan 15:53:26 - [info] Started flows 16 Jan 15:53:26 - [info] [mqtt-broker:hass-mqtt] Connected to broker: mqtt://localhost:1883 16 Jan 15:53:31 - [info] [server:Home Assistant SAM] Connecting to http://supervisor/core 16 Jan 15:53:31 - [info] [server:Home Assistant SAM] Connected to http://supervisor/core 16 Jan 15:53:31 - [info] [server:Home Assistant SAM] Connection closed to http://supervisor/core 16 Jan 15:53:31 - [info] [server:Home Assistant SAM] Connection closed to http://supervisor/core 16 Jan 15:53:36 - [info] [server:Home Assistant SAM] Connecting to http://supervisor/core 16 Jan 15:53:36 - [info] [server:Home Assistant SAM] Connected to http://supervisor/core 16 Jan 15:53:36 - [info] [server:Home Assistant SAM] Connection closed to http://supervisor/core 16 Jan 15:53:37 - [info] [server:Home Assistant SAM] Connection closed to http://supervisor/core 16 Jan 15:53:37 - [info] [debug:json stock] 16 Jan 15:53:37 - [info] [debug:HA msg] 86.6400 16 Jan 15:53:37 - [error] [ha-sensor:stock_gib] NoConnectionError: No connection to Home Assistant

[magiva]

is anyone going to acknowledge this ticket ?

[magiva]

so to move this forward.... i created a new home-assistant server connection as a manual connection. to do this i had to click the user icon (bottom left) and create a permanent token, copy and use that

this worked to a point. it connected and most things were back up and working. except the integration only sees some, not all entities !!!!

so some of the entities i had as triggers now are not found. Its a rediculously bad piece of code that frustrates me alot. maybe you have more luck.

the other way round is to create automations to post mqtt and have mqtt listeners in nodered.

[canedje]

I do run a seperate docker under Unraid with NR. And did as backup in HA the same you mentioned. Make a new server straight to de HA IP with a token My only problem is dat NR flows are slower now. Especially when Zwave is used

So I do have 2 options now to run NR. But I realy hope the problem will be fixed

[magiva]

just create a new ha server entry and don't tick the box to use ha integration

let me know if you need more info

On Mon, 16 Jan 2023, 20:55 canedje, @.***> wrote:

I do run a seperate docker under Unraid with NR. And did as backup in HA the same you mentioned. Make a new server straight to de HA IP with a token My only problem is dat NR flows are slower now. Especially when Zwave is used

— Reply to this email directly, view it on GitHub https://github.com/hassio-addons/addon-node-red/issues/1543#issuecomment-1384491900, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZMQZJZATQ5WLMRHEZRVR3WSWRTJANCNFSM6AAAAAAT2HVPZM . You are receiving this because you authored the thread.Message ID: @.***>

[martinsheldon]

whats mostly concerning is that i, like many and most other people, run their homes with this. The lack of attention these tickets get is really concerning and very disapointing.

I totally agree with you on this. I really appreciate the effort the team are putting in to developing HA but with several people experiencing this issue we should expect an update or at least know if they are aware and working on it. After all Node Red is the 6th most popular addon accoring to their own analytics page with 34 000 installs.

As a temporary workaround I've moved my NR to Docker in Unraid and that has been working fine for over a week. However, this is not how I prefer to do it as a long term solution.

[roybosch]

a temporary workaround I've moved my NR to Docker in Unraid and that has been working fine for over a w

I too agree with this.

I found out that not all users experience the same issues. A friend of mine uses a RPI4 and didn't experience any problems with NodeRed since last update. I'm using an Odroid N2+. What hardware do you use?

I figured that maybe my Home Assistant would have become a little corrupted, because also the developer tools/status tab has very high loading times. I reinstalled Home Assistant and restored a backup to find out that none of it mattered. It didn't resolve any of it.

[magiva]

mine is both a pi and vmware ha os. its more that not one person has been assigned any of the tickets.

On Fri, 20 Jan 2023, 12:05 Roy, @.***> wrote:

a temporary workaround I've moved my NR to Docker in Unraid and that has been working fine for over a w

I too agree with this.

I found out that not all users experience the same issues. A friend of mine uses a RPI4 and didn't experience any problems with NodeRed since last update. I'm using an Odroid N2+. What hardware do you use?

I figured that maybe my Home Assistant would have become a little corrupted, because also the developer tools/status tab has very high loading times. I reinstalled Home Assistant and restored a backup to find out that none of it mattered. It didn't resolve any of it.

— Reply to this email directly, view it on GitHub https://github.com/hassio-addons/addon-node-red/issues/1543#issuecomment-1398229528, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZMQZLK4I4BZO57MGZ4DMTWTJWPXANCNFSM6AAAAAAT2HVPZM . You are receiving this because you authored the thread.Message ID: @.***>

[martinsheldon]

a temporary workaround I've moved my NR to Docker in Unraid and that has been working fine for over a w

I too agree with this.

I found out that not all users experience the same issues. A friend of mine uses a RPI4 and didn't experience any problems with NodeRed since last update. I'm using an Odroid N2+. What hardware do you use?

I figured that maybe my Home Assistant would have become a little corrupted, because also the developer tools/status tab has very high loading times. I reinstalled Home Assistant and restored a backup to find out that none of it mattered. It didn't resolve any of it.

I'm using an old Dell Laptop to run Unraid but I've testet with two laptops and both Unraid and Proxmox with exactly the same behaviour.

States tab in Dev tools is also super slow for me. I mentioned this in the WTH month in October and I believe it was Frenck that commented this indeed was something they was interested in improving so I think its a general issue when you have lots of entities.

[roybosch]

States tab in Dev tools is also super slow for me. I mentioned this in the WTH month in October and I believe it was Frenck that commented this indeed was something they was interested in improving so I think its a general issue when you have lots of entities.

I guess so. But I didn't have this problem before, and I didn't add entities since the last update. Even so the performance dropped drastically.

[canedje]

I agree with above message. It suddenly appeared without changes. Communication with HA is slower in general

[natedzl]

I've been having a similar experience and have been struggling to get to the root cause. Biggest issue is the delay now to zwave network from NR. I've rolled back to 2023.1.1 and rolled back NR and ZWave JS UI add-ons to around the same time and it's slightly better but nowhere near where it was. I'm still showing a number of disconnects and it will eventually reconnect but not for very long.

This is very disappointing that no one is acknowledging these issues.

Running on HA Blue (Odroid N2+)

HomeAssistant - 2023.1.1 Supervisor - 2022.12.1 Operating System - 9.4 ZWave JS UI - 1.4.2 Node-Red - 14.0.1

23 Jan 03:49:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core 23 Jan 03:49:26 - [info] [server:Home Assistant] Connected to http://supervisor/core 23 Jan 05:43:18 - [error] [api-call-service:Nate Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Colleen Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Noah Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Valerie Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Katelynn Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Nate Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Colleen Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Noah Home] Call-service error. 23 Jan 05:43:19 - [error] [api-call-service:Valerie Home] Call-service error. 23 Jan 05:43:20 - [error] [api-call-service:Katelynn Home] Call-service error. 23 Jan 05:43:20 - [error] [api-call-service:Nate Home] Call-service error. 23 Jan 05:43:20 - [error] [api-call-service:Colleen Home] Call-service error. 23 Jan 05:43:20 - [error] [api-call-service:Noah Home] Call-service error. 23 Jan 05:43:20 - [error] [api-call-service:Valerie Home] Call-service error. 23 Jan 05:43:20 - [error] [api-call-service:Katelynn Home] Call-service error. 23 Jan 05:43:20 - [error] [api-call-service:Nate Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Colleen Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Noah Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Valerie Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Katelynn Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Nate Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Colleen Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Noah Home] Call-service error. 23 Jan 05:43:21 - [error] [api-call-service:Valerie Home] Call-service error. 23 Jan 05:43:22 - [error] [api-call-service:Katelynn Home] Call-service error. 23 Jan 05:43:22 - [error] [api-call-service:Kids Home] Call-service error. 23 Jan 05:43:22 - [error] [api-call-service:Kids Home] Call-service error. 23 Jan 05:43:22 - [error] [api-call-service:Kids Home] Call-service error. 23 Jan 05:43:22 - [info] [server:Home Assistant] Connection closed to http://supervisor/core 23 Jan 05:43:22 - [info] [server:Home Assistant] Connection closed to http://supervisor/core 23 Jan 05:43:23 - [error] [api-call-service:Turn Off Basement Porch Lights] Call-Service attempted without connection to server. 23 Jan 05:43:23 - [error] [api-call-service:Turn Off - Back Yard Sconces] Call-Service attempted without connection to server. 23 Jan 05:43:23 - [error] [api-call-service:Turn Off Basement Porch Lights] Call-Service attempted without connection to server. 23 Jan 05:43:23 - [error] [api-call-service:Turn Off - Back Yard Sconces] Call-Service attempted without connection to server. 23 Jan 05:43:23 - [error] [api-call-service:Turn Off Basement Porch Lights] Call-Service attempted without connection to server. 23 Jan 05:43:23 - [error] [api-call-service:Turn Off - Back Yard Sconces] Call-Service attempted without connection to server. 23 Jan 05:43:23 - [error] [api-call-service:Turn Off Basement Porch Lights] Call-Service attempted without connection to server. 23 Jan 05:43:23 - [error] [api-call-service:Turn Off - Back Yard Sconces] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Nate Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Colleen Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Noah Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Valerie Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Katelynn Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Nate Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Colleen Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Noah Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Valerie Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Katelynn Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Nate Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Colleen Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Noah Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Valerie Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Katelynn Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Nate Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Colleen Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Noah Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Valerie Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Katelynn Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Nate Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Colleen Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Noah Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Valerie Home] Call-Service attempted without connection to server. 23 Jan 05:43:25 - [error] [api-call-service:Katelynn Home] Call-Service attempted without connection to server. 23 Jan 05:43:28 - [info] [server:Home Assistant] Connecting to http://supervisor/core 23 Jan 05:43:29 - [info] [server:Home Assistant] Connected to http://supervisor/core

[roybosch]

Unfortunately the latest supervisor update doesn't fix anything. I'm still having NodeRed connect and disconnect every second.

[magiva]

@frenck will anyone respond to this ? is it abandoned ?

[canedje]

Yes very frustrating that there is no reaction at all for more than a month. We don’t know the reason is also an answer. At least showing they take it seriously

[canedje]

It looks like that the last operating system 9.5 did the trick. My NodeRed is operating normal again :-)

[roybosch]

No luck for me unfortunately.

[natedzl]

No luck here either - 9.5 didn't change anything for me.

[frenck]

duplicate of #1498