after last update Node red stopped.
the error is “1 out of 1 hunk FAILED - saving rejects to file nodes / ui_base.html.rej”. files that are non-existent in my configuration
2 Likes
Same problem here. Had to restore last node red backup.
yes also for me
They already released version 7.2.10 which fixes the problem 
.
It works fine now
I’m facing the same issue after installing node-red-contrib-generic-ble:
20 Nov 10:12:27 - [red] Uncaught Exception:
20 Nov 10:12:27 - Error: connect ENOENT /var/run/dbus/system_bus_socket
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! 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 addon-node-red@ start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Can we access dbus via node-red? I know that addons can be configured to passthrough dbus from the host:
‘host_dbus bool’ - Default
false. Map the host D-Bus service into the add-on.
I am having trouble getting a couple nodes to install from the palette. Currently running the Node-RED add-on 7.2.10 on Hass.io 0.117.6 on a Raspberry Pi 3b. I keep getting the below error:
[15:45:22] INFO: Starting installation of custom NPM/Node-RED packages...
> [email protected] install /opt/node_modules/bufferutil
> node-gyp-build
make: Entering directory '/opt/node_modules/bufferutil/build'
CC(target) Release/obj.target/bufferutil/src/bufferutil.o
../src/bufferutil.c:2:10: fatal error: assert.h: No such file or directory
2 | #include <assert.h>
| ^~~~~~~~~~
compilation terminated.
make: *** [bufferutil.target.mk:105: Release/obj.target/bufferutil/src/bufferutil.o] Error 1
make: Leaving directory '/opt/node_modules/bufferutil/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
I’ve added the below system packages to my Node-RED addon’s config:
system_packages:
- make
- gcc
Is this a npm dependency issue? I know bufferutil is part of the npm addon “websocket” but if I add that to npm_packages, the Node-RED addon won’t boot.
Or could it be that the custom node won’t run on ARM based systems?
Any ideas? One of the nodes is https://www.npmjs.com/package/node-red-contrib-sony-audio in case anyone else is willing to try.
Tap the hamburger (3 lines stacked on top of each other) at top right with phone in landscape mode , then tap and hold view and slide your finger (don’t lift from screen) to the option that you want. Be sure to tap and hold or it will disappear. Also , i am able to slide in from the right to open the right sidebar but left will require the hamburger. And @TensE is right, while node red is very navigable from a large screen phone , the safest way is a pc. Most options are in a window when you tap and hold. Good luck
Did you find a solution for node-red-contrib-generic-ble ?
Same problem here with an NR addon.
Adding bufferutil to system packages does not solve the problem.
system_packages:
- make
- bufferutil
Bufferutil sems to be unavailable but I cannot understand how to do…
Is it bufferutil a known addon ?
Thanks in advance.
Is there a way to downgrade the node-red-contrib-home-assistant-websocket package back to a previous version? I tried listing [email protected] in the list of npm packages to install and while it did seem to acknowledge that I wanted that specific version in the log it also was still using 0.27.8 after startup finished.
There seems to be a nasty bug in 0.27.8 that broke a lot of my automations after update so I really want to roll back. It looks like there’s an open PR for 0.27.9 that fixes it so the problem may fix itself soon but idk exactly when since its been open for 6 days and my automation is really messed up right now. Also I figured it would be good to know if there was a way in case something similar happened in the future.
0.27.9 came out and issue is fixed so all good again. Still if someone does know a way to do this and can share it I’d appreciate it. I know you can downgrade custom npm packages by specifying @<version> like I did above in the include. But seems either that only works for custom packages or it specifically doesn’t work for the node-red-contrib-home-assistant-websocket.
EDIT: Found the solution, there was a server added which was using the module, deleted the server and problem was solved. It was probably added while I was testing a flow from someone else.
Hello everyone,
I have a strange issue, I looked around but I couldn’t find anything about it.
Every time when I restart the Node-RED add-on I have reinstall a module otherwise my flows won’t work.
I get next error after a Node-RED add-on restart or HASS.io server reboot:
All my flows don’t work anymore till I reinstall node-red-contrib-home-assistant-ws module.
It looks like really old module, I have the feeling I don’t even need it since I have a similar and newer version of it. I am using the Node-RED add-on only week or two, in the beginning it was working okay, I am not sure what I did to cause this issue.
My HA related modules are:
Any help is appreciated, it is not that big issue I can reinstall it every time but sometimes I forgot about it and get a angry wife since some lights don’t go on automatically 
Getting an error when installing node-red-contrib-m-bus (node) - Node-RED :
gyp ERR! not ok npm ERR! code ELIFECYCLE
Thanks for your work! I want to set up the Node-red for the first time. I have it up and running but when I try to add entity I’m struggling with this error:
‘This node requires Node-RED custom integration to be installed in Home Assistant for it to function.’
I followed the instruction of downloading files and copying them into the ‘custom_components’ but no luck.
Hy,
have you ever resolve this problem?
i have the same problem.
thks.
If I recall it was my SD card that was corrupted. I’ve since then moved to a more reliable solution with SSD.
Hi All,
I am a very old Node-Red user, and a few hours old to Home Assistant. I installed Home Assistant as a Supervised version on a Raspbian buster image. And added Node-Red as an Add-on using supervisor.
All works, Node-Red is running, Home Assistant is running. When I select the Node-Red addon, I can click on the WebUI button and edit the flow.
But when I try to launch the editor in a new browser, the use http://192.168.0.50:1880/ I cannot log in. I tried entering the login into the configuration, I even tries going into the config.js and add the adminAuth section to the Node Red settings file, but nothing works.
How can I get the “full screen” editor working?
Best Regards,
Csongor
Thanks to PickleSlice for the quick screenshot… it fixed my issue… sometimes a picture is a thousand words
I’m having issues with installing node-red-contrib-m-bus (https://flows.nodered.org/node/node-red-contrib-m-bus). I’m running Home Assistant OS 5.10 on a Raspberry Pi 4, Node-Red 7.2.11.
Am I doing anything wrong? I tried installing it through the pallette manager. Is there another way I could get this to work?
[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...
-----------------------------------------------------------
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 7.2.11
You are running the latest version of this add-on.
System: Home Assistant OS 5.10 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2021.1.4
Home Assistant Supervisor: 2021.01.5
-----------------------------------------------------------
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...
patching file nodes/ui_base.html
Hunk #1 succeeded at 1156 (offset 625 lines).
up to date in 3.318s
16 packages are looking for funding
run `npm fund` for details
[cont-init.d] node-red.sh: exited 0.
[cont-init.d] user.sh: executing...
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/main/aarch64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.12/community/aarch64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/main/aarch64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/community/aarch64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/edge/testing/aarch64/APKINDEX.tar.gz
v3.12.3-69-g09503eb40d [http://dl-cdn.alpinelinux.org/alpine/v3.12/main]
v3.12.3-62-gebf75fec7d [http://dl-cdn.alpinelinux.org/alpine/v3.12/community]
v3.13.0-369-gb09df703bd [http://dl-cdn.alpinelinux.org/alpine/edge/main]
v3.13.0-372-g79a3a9ce66 [http://dl-cdn.alpinelinux.org/alpine/edge/community]
v3.13.0-372-g79a3a9ce66 [http://dl-cdn.alpinelinux.org/alpine/edge/testing]
OK: 29953 distinct packages available
(1/1) Installing make (4.3-r0)
Executing busybox-1.31.1-r19.trigger
OK: 141 MiB in 52 packages
OK: 141 MiB in 52 packages
[15:17:38] INFO: Starting installation of custom NPM/Node-RED packages...
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/node-red-contrib-m-bus failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-01-20T14_17_47_421Z-debug.log
[15:17:47] FATAL: Failed to install a specified npm package
[cont-init.d] user.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
-----------------------------------------------------------
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[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.