I have no idea what to do:
- I created the long-lived token
- I entered the credentials for Home Assistant (http://ip_address:8123)
I get a persisting “Connecting” message. Not sure what to do. Any guidance?
I have no idea what to do:
I get a persisting “Connecting” message. Not sure what to do. Any guidance?
That is very little info…
Are you using the addon??
if so…did you check the configuration tab??
Installation
The installation of this add-on is pretty straightforward and not different in comparison to installing any other Home Assistant add-on.
Search for the "Node-RED" add-on in the Home Assistant add-on store and install it.
Set a credential_secret, which is used to encrypt sensitive data. This is just a "password", which you should save in a secondary location.
Start the "Node-RED" add-on.
Check the logs of "Node-RED" to see if everything went well.
Click on the "OPEN WEB UI" button to jump into Node-RED.
The add-on works straight out the box! No need to configure a server!
Note: The add-on is pre-configured out of the box! There is no need to add/change/update the server connection settings!
Sorry: I have this installed in containers (not Add-on)
Are you using https possibly?
It’s not an https; tried using https://ip_address:8123 too. Also, access from browser is def http
SOLVED: firewall issue between docker and local machine. Looked into syslog and realized the error
how was this resolved? I have same issue… However my Home Assistant is https enabled and Node Red is NOT (its http) … In NR , While adding server, I’m accessing the HA server as my duckdns FQDN (https://<myFQDN.site>:8123
Both HA and NR are two different docker instances running on same Synology NAS
I have installed node-red-contrib-home-assistant-websocket in NR node.
Appreciate any guidance.
Ok this is resolved
In Node Red , while configuring the Server,
Changed the HA Base URL to local IP, instead of external(duckdns FQDN)
Select the Accept Unauthorized SSL Certificates checkbox .
Diamond thanks bud…
Anyone else…
https://[haIpAddress]:8123
and mark the check box…
Anyone else…
Be sure to add no trailing slash.
Forget vim vs emacs, trailing slashes are the new reason for online heated debates!