I’m a new HA user coming from OpenHab. Still haven’t fully transfered yet since I’m still making my mind on HA. But, I already use a docker with Node-Red for all my automation. Since I’m also using docker for HomeAssistant (because I’m running unraid and everything is on that server), I understand that add-ons are not available. from my understanding, add-ons also install software like nodered addons install nodered on the server, which I don’t need. How can I use my seperate installation of nodered with home assistant?
The current release, 17.0.7, is not working for a few of us. There are issue reports on the git page, but the first issue report was made by someone over 2 weeks ago and the issues are still assigned to be investigated. When node-red is running, the HA instance becomes unstable, unresponsive, and crashes frequently. Uninstalling and reinstalling did not help. The logs show errors from the node-red addon. Can someone from the dev team look at the addon?
Hi everyone,
I created this discussion on the node-red site:
They, rightly, told me to ask here… So I ask two questions:
Why did I lose the flows I had created (and, moreover, there was no .flows.json.backup file in the node-red directory) by restoring HassOS from a FULL backup from GDrive?
What is the easiest (or most correct) way to install node-red on HassOS to make sure I don’t lose the flows (even in the event of a restore from backup from GDrive )?
I think I was able to fix this issue. The problem appears to be that there are nodes that need to be updated (I had three). It took a long time, but I got them all updated and everything seems to be working now. I started node-red and entered the webui. I had to wait until it came up because everything was running really slow. Then I updated the first node. I let it sit until I got a pop up that said node added. I then restarted node-red and then updated the next node. Once I got the pop up add box, I restarted node-red again. I kept doing this until all the nodes were updated. Again, it will take a while. Once all the nodes were updated, I stopped node-red and rebooted the HA server. Once HA was up and running, node-red started and so far everything seems to be working again.
Pretty disappointed that in over two weeks, the dev has not answered any of these issues on github.
Checked today and node-red is still causing issues. Updating the nodes was not the fix. Does anyone have any idea what is wrong with node-red? It seems it is just a few of us experiencing this. I have unistalled node-red, deleted its storage folder, and reinstalled and it is still not working.
Ni, but I have massives of these:
“domain” is not allowed to be empty
14 Mar 20:34:25 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
14 Mar 20:34:26 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
14 Mar 20:34:27 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
14 Mar 20:34:28 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
14 Mar 20:34:29 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
14 Mar 20:34:30 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
14 Mar 20:34:31 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
14 Mar 20:34:32 - [error] [api-call-service:Zet Time] ValidationError: “domain” is not allowed to be empty
The new version, 17.0.10 seems to have fixed the freezing and crashing. There are no errors in the supervisor log either. That ks to the devs for fixing this addon.
I’m encountering an issue with the Bitpool - Edge BACnet module within Node-RED. Although the module installs correctly, I’m facing difficulties configuring the Bitpool Bacnet Gateway Node as it doesn’t detect any network interfaces.
It appears that Node-RED isn’t able to access the host’s network interfaces properly. Node-RED community add-on is configured with the network set to “host”, which theoretically should grant Node-RED direct access to the host’s network interfaces.
Any insights or suggestions on how to troubleshoot and resolve this issue would be awesome. Also is this a add-on issue or hass OS issue?
Network Interfaces missing adaptors from dropdown.
English below ## - In case it is not allowed to support this solution in this way please delete this post @frenck
Hey Leute,
mein Name ist Tristan vom Youtube-Channel “Tristan’s Smartes Heim”.
Neben vielen Videos über Home Assistant im Zusammenspiel mit Node-RED, habe ich vor einiger Zeit begonnen, eine deutschsprachige Youtube-Shorts Serie über Node-RED zu erstellen - frei nach dem Motto: Wie benutzte ich Node-RED und Home Assistant zusammen.
Dort veröffentliche ich jeden Tag um 18 Uhr neue Videos. Wenn du Interesse hast, klick gerne hier:
Gruß, Tristan
Hi,
my name is Tristan from the Youtube-Channel “Tristan’s Smartes Heim”.
Next to a lot of videos about Home Assistant and Node-RED I create a german Youtube Shorts Serie about “How To use Node-RED with Home Assistant”. In case you are interested have a look here:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 17.0.12
You are running the latest version of this add-on.
System: Debian GNU/Linux 12 (bookworm) (armv7 / raspberrypi4)
Home Assistant Core: 2024.4.3
Home Assistant Supervisor: 2024.04.0
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
[09:17:48] INFO: Starting installation of custom NPM/Node-RED packages...
s6-rc: info: service init-nginx successfully started
npm WARN config optional Use `--omit=optional` to exclude optional dependencies, or
npm WARN config `--include=optional` to include them.
npm WARN config
npm WARN config Default value does install optional deps unless otherwise omitted.
npm WARN config only Use `--omit=dev` to omit dev dependencies from the install.
npm notice
npm notice New patch version of npm available! 10.5.0 -> 10.5.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.5.2>
npm notice Run `npm install -g [email protected]` to update!
npm notice
npm ERR! code 1
npm ERR! path /opt/node_modules/i2c-bus
npm ERR! command failed
npm ERR! command sh -c node-gyp rebuild
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | linux | arm
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! find Python Python is not set from command line or npm configuration
npm ERR! gyp ERR! find Python Python is not set from environment variable PYTHON
npm ERR! gyp ERR! find Python checking if "python3" can be used
npm ERR! gyp ERR! find Python - executable path is ""
npm ERR! gyp ERR! find Python - "" could not be run
npm ERR! gyp ERR! find Python checking if "python" can be used
npm ERR! gyp ERR! find Python - executable path is ""
npm ERR! gyp ERR! find Python - "" could not be run
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! find Python **********************************************************
npm ERR! gyp ERR! find Python You need to install the latest version of Python.
npm ERR! gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
npm ERR! gyp ERR! find Python you can try one of the following options:
npm ERR! gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
npm ERR! gyp ERR! find Python (accepted by both node-gyp and npm)
npm ERR! gyp ERR! find Python - Set the environment variable PYTHON
npm ERR! gyp ERR! find Python - Set the npm configuration variable python:
npm ERR! gyp ERR! find Python npm config set python "/path/to/pythonexecutable"
npm ERR! gyp ERR! find Python For more information consult the documentation at:
npm ERR! gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
npm ERR! gyp ERR! find Python **********************************************************
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Could not find any Python installation to use
npm ERR! gyp ERR! stack at PythonFinder.fail (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:306:11)
npm ERR! gyp ERR! stack at PythonFinder.findPython (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:164:17)
npm ERR! gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
npm ERR! gyp ERR! stack at async configure (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:23:18)
npm ERR! gyp ERR! stack at async run (/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js:81:18)
npm ERR! gyp ERR! System Linux 6.1.0-rpi7-rpi-v8
npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /opt/node_modules/i2c-bus
npm ERR! gyp ERR! node -v v18.20.2
npm ERR! gyp ERR! node-gyp -v v10.0.1
npm ERR! gyp ERR! not ok
npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-04-16T21_17_49_557Z-debug-0.log
[09:17:57] FATAL: Failed to install a specified npm package
s6-rc: warning: unable to start service init-customizations: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service init-nginx: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Any fix or anything else here? I’m also having these issues where there is connection/disconnection and then NodeRed and HA no longer talk with each other:
