#Node-RED suddenly not communicating with HA - no errors in logs.

1 messages · Page 1 of 1 (latest)

frozen flicker
tardy nest
frozen flicker
#

same issue as a lot of others it seems. accessing directly through the browser at port 1880 works, but not through ingress

#

i've got no issues like others mentioned, and do not have the entity_id/schema problem you linked to AFAICT

rotund solstice
#

@frozen flicker Did you update your websocket nodes under Manage Palette? I think my issue started after doing so as I never learn, lol. The other issues that I listed in the other thread are side effects of the broader issue that most people refer to as inject and debug nodes no longer working, and no statuses showing under nodes as it is the most obvious sign of the issue. In most cases this happens when you import 3rd party flows that create an erroneous "Home Assistant" configuration node server (name??). All you need to do in that case is point all the new nodes to the correct server and delete the incorrect one. In the snapshot I pasted here, you can see I only have one with 1256 nodes associated to it. When I have a duplicate, the number of nodes is tiny in comparison so that tells you which one is the bad one. I then renamed the correct one so that it is obvious in the node menus which one to pick.