Please see the add-on documentation on that. It allows you to install custom system & npm packages to fulfil those dependency requirements.
1 Like
Did you get this configured? I have been attempting but I think the Canvas dependency the color thief plugin is calling is out of date…
I did not manage to get it working yet, I think you could be right I was thinking of trying this with Node-RED installed on my server as opposed to HASSIO I have been wanting to move off this dependency for a little while.
Hi,
my Node-Red stopped working some days ago with the error “Error: Cannot find module ‘ipaddr.js’”, i tried several repairs:
- Uninstall Node-Red, delete node-red folder, reboot, install again - not working
- copying node_modules/ipaddr.js/lib/ipaddr.js to node_modules/ipaddr.js/index.js - not working
- recover Node-Red from an older snapshot - not working
Any hints, how this error can be fixed?
[07:02:25] 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”
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module ‘ipaddr.js’
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)
at Object. (/opt/node_modules/proxy-addr/index.js:24:14)
at Module._compile (internal/modules/cjs/loader.js:689:30)
at Object.Module._extensions…js (internal/modules/cjs/loader.js:700:10)
at Module.load (internal/modules/cjs/loader.js:599:32)
at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
at Function.Module._load (internal/modules/cjs/loader.js:530:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! hassio-addon-node-red@ start: node $NODE_OPTIONS node_modules/node-red/red.js “–settings” “/etc/node-red/config.js”
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the hassio-addon-node-red@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-05-29T05_02_29_379Z-debug.log
My config:
{ "credential_secret": "my-secret-credential", "dark_mode": false, "http_node": { "username": "", "password": "" }, "http_static": { "username": "", "password": "" }, "ssl": false, "certfile": "fullchain.pem", "keyfile": "privkey.pem", "require_ssl": true, "system_packages": [], "npm_packages": [], "init_commands": [] }
I just did a update and I am seeing this connection error?
server setup is just as normal:
on device tracker I have some log files:
Any ideas on what is broken would be highly appreciated
Best regards
Casperse
Update seems NR dosent see the binary sensors anymore?
Hey there, maybe this is a stupid question but i cant find a way to change the displayed language in node-red. The german translation is very annoying and often not correct translated. Can i change it back to english?
Release v3.1.2
This is a general maintenance release.
Changes
-
Upgrades add-on base image to 3.1.1 -
Quick formatting cleanup and a couple typos. (#232) (@heytcass) -
Updates dark theme to v0.2.10 (#231) (@tjorim)
-
Updates node-red-contrib-home-assistant-websocket to v0.12.2 (#234)
-
Updates node-red-dashboard to v2.15.4 (#228)
-
Updates node-red-node-geofence to v0.1.1 (#236)
-
Updates snyk to v1.171.1 (#237)
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
This version has given me some work
I fought like pig on the ice but (I guess) I’m the winner (at least for now).
Release v3.1.3
This is a general maintenance release.
Changes
-
Updates node-red-contrib-moment to v3.0.3 (#238)
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Hey @frenck
Did a recent Release change how flow. variables are handled?
After upgrading to v3.1.3 my flow doesn’t get past this current state node using a flow. variable
As soon as I change the variable to msg. or if I restore v3.1.1 it works. I found no hint about a change like this. Is there something I should be aware of?
I am seeing similar issues
Release v3.1.4
This is a general maintenance release.
Changes
-
Updates node-red-contrib-home-assistant-websocket to v0.12.3 (#240)
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
I found recreating the state nodes solved the problem.
Im getting alot of updated nodes. See picture.
Is there a way to update them all so i dont have to go trough them all manually?
AFAIK, yes, you have to do it manually, just enter each node, click Done and deploy.
Hi
I’m new to HASSIO and node red, I having problems with accessing the node red dashboard via nabu casa. I get a “404: Not Found”.
Is it possible to access the dashboard though Nabu casa? I can access it though the local ip address, without problems.
I’m getting the same message in my Node Red log.
- NR add-on version 3.1.4
- HASSIO v 0.94.1
- HASSIO running as docker on Ubuntu 18.04 server
Same error message after updating to HASSIO 0.94.3
My NR flows are responding slow right now, taking 5-15 seconds to register a motion sensor trigger. No idea if that is related, but I’d like to be able to remove the LuaJIT message as a factor.
Thanks!
I’am getting an error when i try to install the addon
Unhandled exception
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py”, line 447, in start
await resp.prepare(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py”, line 353, in prepare
return await self._start(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py”, line 667, in _start
return await super()._start(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py”, line 410, in _start
await writer.write_headers(status_line, headers)
File “/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py”, line 112, in write_headers
self._write(buf)
File “/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py”, line 67, in _write
raise ConnectionResetError(‘Cannot write to closing transport’)
ConnectionResetError: Cannot write to closing transport
Hi All,
I’ve very recently moved my Hassio and Node-Red setup from a Windows Hyper-V VM to a docker setup on Ubuntu.
Hassio itself has moved pretty much perfectly but Node-Red is showing odd behaviour.
After about 12 or so hours (not been home when it happens so not 100% sure) Node-Red seems to crash and throws up the following error on loop:
1. > node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js",
2. > [email protected] start /opt
3. Error loading settings file: /etc/node-red/config.js,
4. TypeError: Cannot read property 'length' of undefined,
5. at Object.<anonymous> (/opt/node_modules/node-red/red.js:115:20),
6. at require (internal/module.js:11:18),
7. at Module.require (module.js:579:17),
8. at Function.Module._load (module.js:489:3),
9. at tryModuleLoad (module.js:497:12),
10. at Module.load (module.js:554:32),
11. at Object.Module._extensions..js (module.js:646:10),
12. at Module._compile (module.js:635:30),
13. at Object.<anonymous> (/etc/node-red/config.js:27:19),
I can get it working again by either rolling the installation back using the Hassio backup page or simply reinstalling the addon but again after 12 or so hours it crashes with the same error.
I’ve tried googling all the errors but i’m not finding anything of any value. (Saw a mention about an issue with Watchtower however i don’t use that on my server)
Any help would be greatly appreciated!