This release also takes care of mitigating the recently discovered lodash vulnerability that is considered high severity. Not all Node-RED nodes have patched and updated to handle this vulnerability, so the add-on does this for you on a higher level. We keep this in place till we are sure all is OK.
More information is provided by Snyk (whom we use to protect and actively scan our add-ons):
@Morten_DK Sounds like you already had a /config/node-red folder.
The add-on only creates the user configuration if the folder is absent (in order to prevent overwriting user data).
Try removing (or renaming) that folder and restart the add-on, it will create the default configuration on startup.
I’m having issues getting Node Red to connect to Home Assistant after reinstalling HA and restoring from a snapshot. I’m able to access nodered via the sidebar, but none of the nodes are able to connect to home assistant. I see API errors across the board, auto-complete doesn’t work, no sign of connection.
I just updated my entire home assistant installation (HassOS, HA Supervisor v170, HA v96.2). I’ve tried messing with settings, reinstalling nodered and starting clean - no previous config files. Still no luck.
Any ideas? Everything worked flawlessly before this.
Update: I was able to get the connection to work by manually inputting my duckdns address and creating a token (unchecking use I have hassio). However auto-complete isn’t working for me yet.
Updating here for completeness sake: My issue ultimately turned out to be with my auth files. Somewhere during my snapshot restoration, the authorization for the proxy HA uses to talk with add-ons stopped working. It affected node red and another add-on. I wanted a clean slate so I deleted all my auth files, onboarding, hassio, etc. I needed to recreate users and credentials and such, but my problem has disappeared.
There might be an easier way, but this way works if you’re having add-on connectivity issues with hassio!
[12:54:43] INFO: Starting NGinx…
nginx: [alert] detected a LuaJIT version which is not OpenResty’s; many optimizations will be disabled and performance will be compromised (see GitHub - openresty/luajit2: OpenResty's Branch of LuaJIT 2 for OpenResty’s LuaJIT or, even better, consider using the OpenResty releases from OpenResty - Download)
28 Jul 12:54:47 - [info] [server:Home Assistant] WebSocket Connected to http://hassio/homeassistant
Does that error mean anything or is it just ignoring it?
Repeating: this can be safely ignored and cannot be fixed at this point.
I know this because I initially caused it by contributing to the Alpine Linux project.
If you are running a high traffic application or website, it might be worth to invest time in it, for a private app, you won’t notice the performance difference.
If you feel like discussing that, feel free to do so in a separate topic.
i’m getting consistent errors from the hass.io logs as follows:
19-07-29 15:31:59 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:04 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:04 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:04 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:09 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:09 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:09 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:14 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:14 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:14 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:19 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:19 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:19 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:24 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:24 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:24 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:29 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:29 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:29 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:34 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:34 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:34 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:39 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:39 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:39 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:44 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:44 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:44 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:49 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:49 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:49 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 15:32:54 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 15:32:54 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 15:32:54 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request running
19-07-29 15:32:56 INFO (MainThread) [hassio.homeassistant] Detect a running Home Assistant instance
19-07-29 16:47:45 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_vscode for admin
19-07-29 16:47:45 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
I’m running 0.96.5 on ubuntu 18.04.2 LTS with supervisor 170 and node red v4.0.6. I tried uninstalling node red, deleting the docker image, and the node red directory in config and redirected all home assistant nodes to a new websocket, but the error keeps coming back. I believe it is also causing instability in hass.io because I’m seeing random reboots. I don’t have any trusted network settings in my configuration.yaml as of now but I have tried that to no avail. Any help is appreciated.
to add to the logs i posted this also happens when a restart is forced:
19-07-29 17:21:06 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API error: Received message 257:None is not str
19-07-29 17:21:06 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API connection is closed
19-07-29 17:21:11 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 17:21:11 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 17:21:11 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 17:21:14 INFO (MainThread) [hassio.api.security] /supervisor/logs access from a0d7b954_vscode
19-07-29 17:21:16 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 17:21:16 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
19-07-29 17:21:16 ERROR (MainThread) [hassio.api.proxy] Client error on WebSocket API Cannot connect to host 172.30.32.1:8123 ssl:False [Connection refused].
19-07-29 17:21:17 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant Docker!
19-07-29 17:21:17 INFO (SyncWorker_34) [hassio.docker.interface] Start homeassistant/qemux86-64-homeassistant
19-07-29 17:21:20 INFO (MainThread) [hassio.api.security] /supervisor/logs access from a0d7b954_vscode
19-07-29 17:21:21 INFO (MainThread) [hassio.api.proxy] Home Assistant WebSocket API request initialize
19-07-29 17:21:21 INFO (MainThread) [hassio.api.proxy] WebSocket access from a0d7b954_nodered
@sunglass_guy On restarts or upgrades of Home Assistant, this is expected to happen.
Node-RED keeps running in that period, and will try to reconnect as soon as possible. There errors occur on connection failure (which makes sense, since HA is not available) until HA is available again.
Release v4.0.2
Changes
Updates node-red-contrib-theme-midnight-red to v0.2.11 (#258)
This release also takes care of mitigating the recently discovered 
Add Timezone configuration details (
Minor typo (
