Thanks for the work!
I have v2.0.1 installed on latestest hassio. I can’t start node-red now. There are no error messages from the interface or CLI. When I attempt to start from the UI, the webpage in chrome eventually hangs and has to be killed.
Hi, did you manage to find a solution as I have the same problem. I also looked on the discord server and there did not seem to be any solution there either.
I think there are two things happening, at least on my end: some of the pages are now dying (browsers give option to wait or kill). RE: node-red, I ended up un-installing the add-on, rebooted and re-installed node-red and things are fine. Well, had to re-plumb credentials, but other than that working OK.
Release v2.0.2
Changed
-
Updates node-red to v0.20.3 (#172) -
Updates js-yaml to v3.13.0 (#173)
-
Upgrades add-on base image to 3.0.1
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
1 Like
Hi,
I have a problem,
I previously connected an ESP32 dev board to my RPI.
now node-red will not start when the device is disconnected
19-03-28 08:33:56 INFO (SyncWorker_8) [hassio.docker.interface] Clean hassioaddons/node-red-armv7 Docker application 19-03-28 08:33:57 ERROR (SyncWorker_8) [hassio.docker] Can't start addon_a0d7b954_nodered: 500 Server Error: Internal Server Error ("linux runtime spec devices: error gathering device information while adding custom device "/dev/ttyUSB0": no such file or directory")
when i connect the device to the usb port, node-red starts up normally…
any ideas how I can solve this issue?
edit: uninstalling and reinstalling solved the issue, but I am afraid I will constantly be reinstalling this as I need to connect/disconnected different ESP32 devices to program with ESPHome
thanks
Release v3.0.0
This release adds Hass.io Ingress support to the add-on
Changed
-
Updates node-red-contrib-home-assistant-websocket to v0.10.2 (#183)
-
Updates js-yaml to v3.13.1 (#182)
-
Updates node-red to v0.20.5 (#181)
-
Upgrades base image to v3.1.0
-
Upgrades gcc to 8.3.0-r0
-
Adds Hassio Ingress support -
Simplifies add-on code logic -
Updates README for Hassio Ingress -
Updates README installation instructions
-
Removed obsolete embedding and FAQ sections from README
-
Updates node-red-node-serialport to v0.8.1 (#185)
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
After updating to the latest release, I can no longer open Nodered.
I am running hass.io 0.91.3 on a raspi 3b+. Whenever I try to open it via hassio, it tries to open through the panel iframe, it says duckdns cannot connect. When I try to open it through hassio.local:1880 and 192.168.x.xxx:1880, it says the site cannot be reached.
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…
Hass.io Add-on: Node-RED
Flow-based programming for the Internet of Things
Add-on version: 3.0.0
You are running the latest version of this add-on.
System: HassOS 2.11 (armv7 / raspberrypi3)
Home Assistant version: 0.91.3
Supervisor version: 159
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing…
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] node-red.sh: executing…
[19:46:05] INFO: Password is NOT in the Have I Been Pwned database! Nice!
up to date in 1.882s
found 0 vulnerabilities
[cont-init.d] node-red.sh: exited 0.
[cont-init.d] user.sh: executing…
[cont-init.d] user.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[19:46:11] INFO: Starting Node-RED…
hassio-addon-node-red@ start /opt
node $NODE_OPTIONS node_modules/node-red/red.js “–settings” “/etc/node-red/config.js”
14 Apr 19:46:16 - [info]
Welcome to Node-RED
===================
14 Apr 19:46:16 - [info] Node-RED version: v0.20.5
14 Apr 19:46:16 - [info] Node.js version: v10.14.2
14 Apr 19:46:16 - [info] Linux 4.14.98-v7 arm LE
14 Apr 19:46:17 - [info] Loading palette nodes
14 Apr 19:46:23 - [info] Settings file : /etc/node-red/config.js
14 Apr 19:46:23 - [info] Context store : ‘default’ [module=memory]
14 Apr 19:46:23 - [info] User directory : /config/node-red/
14 Apr 19:46:23 - [warn] Projects disabled : editorTheme.projects.enabled=false
14 Apr 19:46:23 - [info] Flows file : /config/node-red/flows.json
14 Apr 19:46:23 - [info] Server now running at http://127.0.0.1:46836/
14 Apr 19:46:24 - [info] Starting flows
14 Apr 19:46:24 - [info] Started flows
[19:46:24] INFO: Starting NGinx…
14 Apr 19:46:29 - [info] [server:Home Assistant] WebSocket Connected to http://hassio/homeassistant
[14/Apr/2019:19:52:19 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET / HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:19 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/bootstrap/css/bootstrap.min.css HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:19 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/jquery/css/smoothness/jquery-ui-1.10.3.custom.min.css HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:19 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/font-awesome/css/font-awesome.min.css HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/vendor.css HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /red/style.min.css HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /red/images/node-red.png HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 200 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /red/images/spin.svg HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 200 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/jsonata/jsonata.min.js HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/vendor.js HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 200 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/ace/ext-language_tools.js HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 200 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/ace/ace.js HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 200 192.168.1.1, 172.30.32.1(172.30.32.2) GET /red/main.min.js HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:20 -0500] 200 192.168.1.1, 172.30.32.1(172.30.32.2) GET /red/red.min.js HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:22 -0500] 304 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/font-awesome/fonts/fontawesome-webfont.woff?v=4.7.0 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
[14/Apr/2019:19:52:22 -0500] 200 192.168.1.1, 172.30.32.1(172.30.32.2) GET /vendor/font-awesome/fonts/fontawesome-webfont.ttf?v=4.7.0 HTTP/1.1 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36)
Just saw this tonight.
Node-RED 3.0.0 is available You are currently running version 2.0.2 This update is no longer compatible with your system.
I believe i’m running HASSIO on a rpi3.
*never mind, just restarted and I can update.
Ingress support has been added, which means the add-on works via the cloud connection as well, simply by clicking the “OPEN WEB UI” button on the add-on page.
You can still enable the “old” direct access method, by setting a port in the network section of the add-on configuration panel.
Hey Frenck, On the direct access method on port 1880, the HA credentials are failing upon login. keeps asking for credentials.
1 Like
Updated and everything seems to work. However, there is no info anymore showing when I node was last triggered and the Debug node does not show any information in the Debug panel.
Update, got Debug and Statuses to work by accessing hassio directly (ip:port) instead thru reverse proxy - so seems to be an issue when going thru reverse proxy server.
Same issue here.
Same here as well… at least using chrome. Using the WebGui link opens the “embeded” version but still does not login, showing an empty page with just the nodered logo on top.
Shift+F5 end up showing:
Update: Using Firefox the external site is working including login
In case it wasn’t clear for hass.io, to add a button in the sidebar, add something like this to configuration.yaml:
panel_custom:
- name: hassio-main
sidebar_title: Node-RED
sidebar_icon: mdi:wrench
js_url: /api/hassio/app/entrypoint.js
url_path: nodered
embed_iframe: true
require_admin: true
config:
ingress: a0d7b954_nodered
The ingress value may differ; when you click on the add-on in Hass.io, look at the end of the URL and use that.
2 Likes
While I am using the ingress for the web UI, I use direct access for a web socket connection from my smart meter box. I have a POST node:
[
{
"id": "f75b678a.15f718",
"method": "post",
"name": "",
"swaggerDoc": "",
"type": "http in",
"upload": false,
"url": "/eagleenergy",
"wires": [
[
"14341499.f6b37b",
"685b7d4e.bbd174",
"a50a796.8193688"
]
],
"x": 130,
"y": 100,
"z": "7765c2a1.8ef4ac"
}
]
Which listens on /eagleentery on port 1880. Is there a way to disable authentication or use some type of token that I can append to the URL that I add to my smart meter?
Thanks!
Replying to my own post, adding leave_front_door_open to the config and removing the username/password is letting my POST get through. I wish there was a way to secure the web UI, but allow other access. Maybe in a future version.
STATUS: The port method doesn’t let me login. On the Ingress method, I’m seeing webpage loading errors. This happens when accessing it the second time on the http load not on the https(works fine on https)…
Clearing cache helps load once again on http(local ip) and when i try to load page the second time it fails again to load and then i see the below page errors.
1 Like
Https (port 1880) login is possible for me but only using firefox, chome is not working. (ssl enabled via addon config/ ssl is not enabled for HA itself). The Ingress method is not working for me at all.
Looking to get a different adress to use with panel_iframe. When I take the url when using the web_ui from the add_on page and try to use it with panel_iframe I get the panel doubled. I had the same problem with configurator but was able to find another url following the instructions from this page:
When I look at the adress I have for node_red it is:
https://redacted.duckdns.org:8123/hassio/ingress/a0d7b954_nodered
The adress I got for the configurator is:
https://redacted.duckdns.org:8123/api/hassio_ingress/partiallyredactedp_bozBtcSU_QOroLZMqE6ZjcE/
It is interesting to se the different structure
hassio/ingress/…
vs.
api/hassio_ingress/…
Anyone who knows how to find the corresponding adress for node red?
I’ve been having a lot of trouble accessing Node-RED after 3.0. To access via ingress I seem to have to force refresh every single time in order to get it to load at all. Otherwise it just loads the basic frame but no content. When it does load, many of the icons for nodes are broken images. Which ones seem to vary. In addition, sometimes I have to force reload several times to get it to load. This is in Chrome.
After first enabling the port method again, I had the issue where it asked for credentials over and over and never loaded. But after clearing all my browser data, port method seems to be working and reliably loading.
1 Like