@Frank3 Same “Addon is not running” message when attempting to edit flows. Red dot and nothing special in the logs. Flows seemed slow today so wanted to check for errors. I could edit a couple of days ago. Did you find a solution?
@frenck - if you’re reading this,
Since you’re one of the NR masterminds here, do you have any advice as to make palette manager once again be able to install nodes requiring Node v14?
Can you confirm that v14 is still included in NodeRed 13.x as @maxym mentioned?
Either way, I’m kinda grasping at straws here, as I’ve already tried re-installing NR and I’m unsure how to tackle this problem, preventing me from installing nodes I need to work with.
So at the risk of sounding like the broken record, I’m starting to wonder here:
- Anyone out there capable of installing other palette nodes requiring Node 14 after Node Red v13 ?
- Did someone make a decision to ‘unsupport’ any palette nodes which does not support Node 16?
- If that’s not the case and Node14 is still in the mix, what can cause it to remain invisible to the palette installer, even after a NR reinstall?
- Other than downgrading to an old Node Red 12, which I don’t even know if and how can be done on a Supervised HA environment, what can be done here?
- Is this a general problem, or am I being the global village idiot here? If it’s simple to solve and I’m overlooking it, please provide a push in the right direction.
- If this is something nobody else than I is experiencing, I seriously need some advice how to get Node 14 enabled in NR 13.2
Thanks
/Max
I upgraded node-red today and I can’t run my flows again. All HA nodes have disappeared, so I don’t really know how to proceed. I could try to delete all the HA nodes, but that would be quite a lot of work. Has anyone come up with a solution? I may also downgrade, but I do not have a backup for node red.
Hi, did you find a way to connect to HomeSeer using the add-on? I’m looking for the same solution. Since I have all my z-wave devices on HomeSeer and some events I still want to use. Over time I will port everything over to HA. But for now it seems to be a nice solution.
- I assume that the HomeSeer module you arereferring to is the one in NoderRed?
- I already have create a webhook in HomeAssistant but I’m not sure if that is ok. Which IP url should I use there the HomeSeer machine url or the HA url??
So hopefully you can point me out how to achieve the connection 
Or maybe even share some sample code you used for it? Thanks.
Ok, managed to get this working myself. Using the right (HS4 user and admin will help to connect as well
Now I have the HS4 devices and events listed. Next I need to get familiar with creating flows and how to get t hat into the HA dashboard.
For others looking for a way to get this implemented. This info helped me out (select an add-on in the Node red settings) and follow the instructions:
Now I have Node-red connected to HomeSeer I’m looking to build a simple first flow, to get the idea how this works. But most howto are about flows in HA and not in combination with HomeSeer. So anyone who has a simple to understand flow which helps me to build a first flow having a device status in HomeSeer set from Off to On. Using a switch (from the dashboard) or an inject as I tried in my example. since I have no idea how to get there. Any howto (youtube) or other samples are appreciated as well. Thanks.
[{"id":"6bc9179586104c63","type":"hs-device","z":"dc1404c404fe1bd4","name":"Beneden Bijkeuken Fibaro Switch Binary Node 18 Root Switch Binary 1","device":"24","server":"367ff7807724edc9","feature":"25","reportonstartup":true,"x":560,"y":460,"wires":[["f03e96688bdbd1ba"]]},{"id":"f03e96688bdbd1ba","type":"debug","z":"dc1404c404fe1bd4","name":"debug 1","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":920,"y":600,"wires":[]},{"id":"3fd5ad04e634e898","type":"inject","z":"dc1404c404fe1bd4","name":"On","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"On","payload":"control","payloadType":"str","x":170,"y":440,"wires":[["6bc9179586104c63"]]},{"id":"9c5b0ec41354855e","type":"inject","z":"dc1404c404fe1bd4","name":"Off","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"Off","payload":"control","payloadType":"str","x":170,"y":500,"wires":[["6bc9179586104c63"]]},{"id":"367ff7807724edc9","type":"hs-server","name":"HomeSeer Server","host":"192.168.0.30","port":"80"}]
Edit!
Got it working now. Both for devices and events it seems to work. Nice!
Hello Node Red experts!
I’ve already NodeRed set-up and running but there is one thing I don’t know how to do or if it is possible at all.
One device has a register for the device status. Imagine there are 3 possible values 0,1 or 2
0 => stop
1 => running
2 => fault
I can easily create a sensor (numeric) and report that value up to HA. But, what I really want to do is to use a switch with 3 outputs, a function to transform each output into a string value “stoped”, “running”, “broken” and send that string up to HA. this is because in the history of that sensor I don’t want to see the values in the Y axis of a line graph but the text returned bu the sensor in a single row.
I’ve tested multiple configurations but I have been unable to get it done.
Help will be appreciated!
I found the reason of my problem and is worth commenting it here!
During the process of creating the entity in Node Red I used to do a Copy & Paste of another similar entity and later modify only the entity name. The consequence was I was NOT creating a new sensor but modifying an existing sensor and attaching it to the new input! That was causing troubles in the previously created entities so Copy and Paste of existing entities is not a good idea!
Guys, I need some advice.
I am trying to communicate to some EZO sensors and dosing pumps stacked/connected to my RPI4 via I2C, using the i2c Nodes (node-red-contrib-i2c 0.9.0) and get the “Error: EPERM: operation not permitted, open ‘/dev/i2c-1’” message.
The I2C is enabled, I followed @adamoutler 's I2C Configurator (used it for the PIjuice Hat and on another setup for the ArgonOne cooling fan. Many thanks @adamoutler)
Home Assistant 2022.12.8
Supervisor 2022.11.2
Operating System 9.4
Frontend 20221213.1 - latest
Node-RED Current version: 14.0.0
Any advice?
Just to verify, you have the i2c-1 device found in the logs of the addon, correct? If so, it’s probably a permissions problem in this addon, being not able to access the port, or the port is locked by the other addon.
Yes, that is correct.
Log from i2c Configurator:
/dev/i2c-1
/dev/i2c-0 /dev/i2c-1 /dev/i2c-10 /dev/i2c-22
Found i2c access! Nothing to do! You can remove this add-on.
Plus the Argon One Active Linear Cooling add-on found 1a and its running fine.
Is there any way to fix this?
Thx
EDIT: I don’t think I need this so I won’t be trying to figure this out. I was trying to get zwave working in Node-RED in HA. I was over-complicating this and now I realize I just need to use the sensors that I have in HA already.
I am trying to get the Node RED Zwave contrib plugin to work. I am getting an error; “Error listing serial ports” and I have not been able to fix this. Also getting “ZWaveError: Failed to open the serial port: Error Resource temporarily unavailable Cannot lock port (ZW0100)”.
I use a Linux virtual machine, not a Raspberry PI, but this hopefully will work —
"For people running Node-RED in docker on a rpi, the issue is caused by serial port 10.1.0 which is not compatible with ARM architecture serialport/node-serialport#2438 (comment).
Proposed workaround is to run npm rebuild --build-from-source (inside the docker as @marcus-j-davies sayed).
Now my Node-RED 3.0.2 works with node-red-contrib-zwave-js 8.0.0 through Docker on my rpi."
How do I run “npm rebuild --build-from-source” for Node RED in Home Assistant and hopefully fix this?
I wanted to debug a flow and have added a few debug nodes (in fact they have been there for months). However nothing appears in the debug window.
This has worked in the past. Couldn’t find any errors in the log.
Why is this not showing?
Did you enable the debug widget? It’s the button on the right.
Also you may want to change it from “payload” to “complete msg object”.
Yes I did 
and saw the notification that the node is successfully activated
Even selecting all nodes for the debug scope nothing appears in the debug window on the right.
How do I get further debug information for this?
Ok have fixed that up
but still no debug messages. Even if I select all nodes there’s nothing showing.
Had a look at the log and the only question is on the line saying
1 critical severity vulnerability
Where do I run npm? I tried the HA command line but that didn’t work
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: 14.1.5
You are running the latest version of this add-on.
System: Home Assistant OS 10.1 (amd64 / qemux86-64)
Home Assistant Core: 2023.5.2
Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
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
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
up to date, audited 86 packages in 3s
10 packages are looking for funding
run `npm fund` for details
1 critical severity vulnerability
To address all issues, run:
npm audit fix
Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:03:44] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
10 May 09:03:48 - [info]
Welcome to Node-RED
===================
10 May 09:03:48 - [info] Node-RED version: v3.0.2
10 May 09:03:48 - [info] Node.js version: v18.14.2
10 May 09:03:48 - [info] Linux 6.1.25 x64 LE
10 May 09:03:49 - [info] Loading palette nodes
10 May 09:03:59 - [info] Dashboard version 3.4.0 started at /endpoint/ui
10 May 09:04:00 - [info] Settings file : /etc/node-red/config.js
10 May 09:04:00 - [info] Context store : 'default' [module=memory]
10 May 09:04:00 - [info] User directory : /config/node-red/
10 May 09:04:00 - [warn] Projects disabled : editorTheme.projects.enabled=false
10 May 09:04:00 - [info] Flows file : /config/node-red/flows.json
10 May 09:04:00 - [info] Server now running at http://127.0.0.1:46836/
10 May 09:04:00 - [info] Starting flows
10 May 09:04:01 - [info] Started flows
10 May 09:04:01 - [info] [mqtt-broker:SR90 Production Broker] Connected to broker: mqtt://192.168.2.97:1883
[09:04:01] INFO: Starting NGinx...
10 May 09:04:05 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 May 09:04:05 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 May 09:04:05 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 May 09:04:06 - [info] [server:Home Assistant] Connected to http://supervisor/core
10 May 09:04:06 - [info] [server:Home Assistant] Connected to http://supervisor/core
10 May 09:04:06 - [info] [server:Home Assistant] Connected to http://supervisor/core
After updating NR today to v14.2.0 it no longer comes up with a complete UI. Only the top black line with the NR logo in the left hand corner is visible - after a while (5-8 seconds). I’ve restarted both HA v2023.5.3 and NR several times, but to no avail.
I found - after some more testing, that it does load If I use Chrome on a PC, but it fails when using Samsung Smart TV Browser v3.21.22 which is built into my Tizen based Samsung Neo QLED TV (and which cannot be replaced or updated).
However, the previous version of NR worked just fine, so I was wondering how can I downgrade NR to the previous version?
What’s a good way to program HA with some “hooks” into a Node-RED automation where the hook could be presented on a Card in order to do some manually interaction with the automation like; unschedule, disable, run actions? The kind of the things you can do with an HA automation already.