You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the last few weeks, I'm regularly seeing an issue, typically after deploying changes, where Home Assistant nodes get stuck in a "connecting" status. Inject nodes remain disabled in this state.
Expected behavior
Successful connection, I guess?
Actual behavior
In the browser console, I see attempts being made every second to GET wss://[my_domain]/api/hassio_ingress/[...]/comms, always with a HTTP 101 response with a body that contains a list of JSON objects like {"subscribe":"homeassistant/labels/#"}.
After trying various other things, I've found that I'm often able to resolve the issue by restarting all flows.
Edit: Nevermind - restarting flows seems to be generally unhelpful. What I've otherwise tried is to restart Node RED, which rarely works, and restart Home Assistant, which works most if not all of the time.
Steps to reproduce
For me at least - this is seemingly quite random and happens after deploying changes.
Proposed changes
-
The text was updated successfully, but these errors were encountered:
Problem/Motivation
For the last few weeks, I'm regularly seeing an issue, typically after deploying changes, where Home Assistant nodes get stuck in a "connecting" status. Inject nodes remain disabled in this state.
Expected behavior
Successful connection, I guess?
Actual behavior
In the browser console, I see attempts being made every second to GET
wss://[my_domain]/api/hassio_ingress/[...]/comms
, always with a HTTP 101 response with a body that contains a list of JSON objects like{"subscribe":"homeassistant/labels/#"}
.After trying various other things, I've found that
I'm often able to resolve the issue by restarting all flows.Edit: Nevermind - restarting flows seems to be generally unhelpful. What I've otherwise tried is to restart Node RED, which rarely works, and restart Home Assistant, which works most if not all of the time.
Steps to reproduce
For me at least - this is seemingly quite random and happens after deploying changes.
Proposed changes
-
The text was updated successfully, but these errors were encountered: