Repository: NotoriousBDG Add-Ons (Node-RED, HA Bridge, and Gogs)

@NotoriousBDG thank you…will try today when back home.

Hi all
Thanks to @NotoriousBDG for sharing.
I just finished installing to my HASSIO test on a RPi 3 B but II don’t see the home-assistant nodes in the list.
Is it normal?
Should I install node-red-contrib-home-assistant from Palette?
In this case, I’ve tried but after 1-2 minutes seems nothing happens and the module is not installed.

Any suggestions?

Thanks

Yes. Install node-red-contrib-home-assistant from palette manager.

Try giving it a few more minutes. The Pi-Hole addon can cause name resolution problems if you don’t have a static IP setup of if you don’t have hassio configured to use an external DNS server. If it still doesn’t install, check the addon logs at http://hassio.local:8123/hassio/addon/27e642c6_nodered.

Thanks.
I’ve added and now I see the nodes.

One more question, regarding the HASSIO Config parameters in Nodered.

In my configuration.yaml I have:

http:
    base_url: !secret conf_base_url
    api_password: !secret conf_api_password

where my base_url is my ddns address.

I’ve set https://mylocalhassioip:port in the “Base URL” field (not the one in the http:base_url) and the api_password that I have in configuration.yaml into the field “API Pass”, but I’m getting an error:

[error] [server:Home Assistant] Home assistant connection failed with error: Connection to home assistant could not be established with config: https://mylocalhassioip:port <password redacted>

Is it correct this configuration?

Sorry, but I’m a newbie in this!!!

Thanks

Attempting to install from the addon store and getting the following:

18-05-09 16:29:42 INFO (SyncWorker_16) [hassio.docker.addon] Start build 27e642c6/amd64-addon-nodered:0.1.11
18-05-09 16:29:42 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 381, in start
resp = await self._request_handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web_app.py”, line 322, in _handle
resp = await handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py”, line 88, in impl
return await handler(request)
File “/usr/lib/python3.6/site-packages/hassio/api/security.py”, line 48, in token_validation
return await handler(request)
File “/usr/lib/python3.6/site-packages/hassio/api/utils.py”, line 33, in wrap_api
answer = await method(api, *args, **kwargs)
File “/usr/lib/python3.6/site-packages/hassio/addons/addon.py”, line 607, in install
if not await self.instance.install(self.last_version):
File “/usr/lib/python3.6/site-packages/hassio/utils/init.py”, line 25, in wrap_api
return await method(api, *args, **kwargs)
File “/usr/lib/python3.6/concurrent/futures/thread.py”, line 56, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/lib/python3.6/site-packages/hassio/docker/addon.py”, line 273, in _install
return self._build(tag)
File “/usr/lib/python3.6/site-packages/hassio/docker/addon.py”, line 287, in _build
**build_env.get_docker_args(tag))
File “/usr/lib/python3.6/site-packages/docker/models/images.py”, line 258, in build
resp = self.client.api.build(**kwargs)
File “/usr/lib/python3.6/site-packages/docker/api/build.py”, line 162, in build
path, exclude=exclude, dockerfile=dockerfile, gzip=gzip
File “/usr/lib/python3.6/site-packages/docker/utils/build.py”, line 31, in tar
root=root, fileobj=fileobj, gzip=gzip, extra_files=extra_files
File “/usr/lib/python3.6/site-packages/docker/utils/build.py”, line 151, in create_archive
fileobj = tempfile.NamedTemporaryFile()
File “/usr/lib/python3.6/tempfile.py”, line 540, in NamedTemporaryFile
prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir)
File “/usr/lib/python3.6/tempfile.py”, line 130, in _sanitize_params
dir = gettempdir()
File “/usr/lib/python3.6/tempfile.py”, line 296, in gettempdir
tempdir = _get_default_tempdir()
File “/usr/lib/python3.6/tempfile.py”, line 231, in _get_default_tempdir
dirlist)
FileNotFoundError: [Errno 2] No usable temporary directory found in [’/tmp’, ‘/var/tmp’, ‘/usr/tmp’, ‘/’]

Anyone have any idea how to fix this?

Someone posted the same issue on GitHub too (https://github.com/notoriousbdg/hassio-addons/issues/37). That error suggests there might a an issue in the latest hassio supervisor. Adding @pvizeli for his insight.

Your best option is to use the API proxy address builtin to hassio of http://hassio/homeassistant within Node-RED.

Thanks @NotoriousBDG

I’ve tried with:
https://hassio/homeassistant
https://192.168.x.x:8123/homeassistant
https://xxx.duckdns.org:xxx/homeassistant

But I always get the same error message in the debug panel (changing only the address part).

Home assistant connection failed with error: Connection to home assistant could not be established with config: https://hassio/homeassistant <password redacted>

You shouldn’t need to enter your password if you use the api proxy.

1 Like

Solved using http://hassio/homeassistant without SSL (http instead of https, that wasn’t working) with no passwd.

Thanks @NotoriousBDG!

1 Like

I am using Hass.io on a PI3 with Node Red. I use SSL (DuckDNS) and have managed to set up Node Red. It is working fine. However, when setting it up I was fooled by a trailing “/” in the url and I constantly get error messages for all the different urls I tested even though I have just one HA-server set up in Node Red. I have tried to remove the other servers from the config pane (configuration nodes) without getting rid of the error messages. Is there a way to get rid of these error messages? They make debugging hard.

5/13/2018, 9:38:26 PMnode: Home Assistant
msg : string[153]
"Home assistant connection failed with error: Connection to home assistant could not be established with config: http://localhost:8123 <password redacted>"
5/13/2018, 9:38:26 PMHome Assistant
msg : string[164]
"Home assistant connection failed with error: Connection to home assistant could not be established with config: https://[redacted].duckdns.org/ <password redacted>"
5/13/2018, 9:38:26 PMnode: Home Assistant
msg : string[153]

I only have a single config node for Home Assistant, and I’m not getting those errors. Not sure what else to suggest if you’ve already removed all of the bad config nodes.

1 Like

Hi guys,
i can install Node-RED anymore. I always run into this error:

Can't build 27e642c6/armhf-addon-nodered:0.1.11: The command '/bin/sh -c apt-get update &&     apt-get install -y jq &&     npm install -g node-red-admin' returned a non-zero code: 132

Has someown an idea how to solve it ?

Greetings,

Hi, I´m getting this error when trying to install Node-RED
18-05-15 19:59:18 ERROR (SyncWorker_1) [hassio.docker.addon] Can’t build 27e642c6/amd64-addon-nodered:0.1.11: Please provide a source image with from prior to commit

My setup is Hassio docker running on Ubuntu VM (ESXI)
Home Assistant 0.69.1

I’m unable to repro that error. Perhaps the issue was temporary. Can you retry?

You need to upgrade Docker (Install Docker Engine on Ubuntu | Docker Docs).

@NotoriousBDG thanks alot! :smiley:

That solved it! to be honest i was running Docker version 1.13 :roll_eyes: I had no idea!!! hahha

1 Like

I too am getting the same error as Supersonical but am using Hassio from image. I see the solutions to update docker but cannot find any info on how to do so on resinos. Feel like I’m missing something.

Home Assistant 0.70.0b1

this is also showing in the logs

INFO (MainThread) [hassio.api.security] /addons/27e642c6/armhf-addon-nodered/update access from core_ssh

Any thoughts?

If you’re running on resios, you’re likely experiencing a different issue. What version of resinos do you see on the hassio System tab? Can you post more of your log?

thanks for your quick response

Hass.io supervisor
Version 103.3
Latest version 103.3

Log is only showing a few lines at a time, tried ssh to access as well and got this…

core-ssh:~# hassio su logs
Error decoding json invalid character ‘\x1b’ looking for beginning of value: 18-05-22 14:26:08 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3
18-05-22 14:36:09 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3
18-05-22 14:41:25 INFO (MainThread) [hassio.api.security] /supervisor/logs access from core_ssh

just tried stopping appdaemon, and installing node red, this is what is showing in the system log now

18-05-22 14:46:43 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 381, in start
resp = await self._request_handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web_app.py”, line 322, in _handle
resp = await handler(request)
File “/usr/lib/python3.6/site-packages/aiohttp/web_middlewares.py”, line 88, in impl
return await handler(request)
File “/usr/lib/python3.6/site-packages/hassio/api/security.py”, line 36, in token_validation
return await handler(request)
File “/usr/lib/python3.6/site-packages/hassio/api/proxy.py”, line 200, in websocket
await client.send_str(server_read.result())
File “/usr/lib/python3.6/site-packages/aiohttp/web_ws.py”, line 392, in receive_str
msg.type, msg.data))
TypeError: Received message 8:1000 is not WSMsgType.TEXT
18-05-22 14:46:48 INFO (SyncWorker_7) [hassio.docker.interface] Clean hassioaddons/appdaemon3-armhf docker application
18-05-22 14:48:54 INFO (SyncWorker_5) [hassio.docker.addon] Start build 27e642c6/armhf-addon-nodered:0.1.11
18-05-22 14:48:54 ERROR (SyncWorker_5) [hassio.docker.addon] Can’t build 27e642c6/armhf-addon-nodered:0.1.11: Please provide a source image with from prior to commit

That’s interesting. It does look like you’ve got an old version of Docker. What do you see for “System” under “Host system”?