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?
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.
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.
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
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)
My IFTTT --> Node-RED webhooks stopped working. I did not change any of my configs or anything. Do I need to change the path to node-RED on IFTTT when using ingress? I don’t know what other reason might be causing this problem.
i’m not abble to start the add-on, it gives me the following error :
Welcome to Node-RED
===================
20 Jun 17:56:00 - [info] Node-RED version: v0.20.5
20 Jun 17:56:00 - [info] Node.js version: v10.14.2
20 Jun 17:56:00 - [info] Linux 4.14.98-v7 arm LE
20 Jun 17:56:01 - [info] Loading palette nodes
20 Jun 17:56:08 - [info] Dashboard version 2.15.4 started at /endpoint/ui
20 Jun 17:56:09 - [red] Uncaught Exception:
20 Jun 17:56:09 - Error: bind EADDRINUSE 0.0.0.0:9898
at state.handle.lookup (dgram.js:242:18)
at process._tickCallback (internal/process/next_tick.js:63:19)
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-06-20T16_56_09_816Z-debug.log
[17:56:09] 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”
/usr/lib/bashio/net.sh: line 18: 585 Terminated timeout ${timeout_argument} “${timeout}” bash -c “until echo > /dev/tcp/${host}/${port} ; do sleep 0.5; done” > /dev/null 2>&1
[cont-finish.d] executing container finish scripts…
[cont-finish.d] 99-message.sh: executing…
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
Release v3.1.2
Changes
Upgrades add-on base image to 3.1.1
Quick formatting cleanup and a couple typos. (#232) (@heytcass)
Removes now deprecated ssl directive
Changes dark theme repository link (
Maintaince -> Maintenance
Adds FUNDING.yml