Is it how does range node normally work (I can not find it in documentation)?: scalling range 0 to 100 on 0 to 10 or 0 to minus 100 on 0 to minus 10 works great. But scalling minus 100 to 100 on minus 10 to 10 do not work well. I looks like it take only some negative values.
Just installed this but unable to access the dashboard using any method (via Ingress, using the sidebar, direct to port 1880). My Hass.io server is running Ubuntu 18.04 and I’ve opened port 1880, but cannot access Node-RED (using the direct method I do get a login screen now but when I log in it says ‘Please add some UI nodes to your flow and redeploy’). I’ve tried opening various ports with no success. If I disable UFW entirely it works just fine, but I’d rather not disable the whole firewall. Which ports should I open so I can access Node-RED?
Open SSH terminal (via the SSH & Web Terminal add-on under Hassio)
Open the Phoscon App (open web-ui in the deCONZ add-on under Hassio)
In the Phoscon App goto: Hamburger menu → Gateway → Advanced → Click ‘Authenticate app’ (This will open the gateway for 60 seconds)
In the SSH terminal type:
curl -d ‘{“devicetype”: “[give the application name, for instance Node-RED]”}’ -H “Content-Type: application/json” -X POST http://[your local ip address for Hassio / deCONZ]:40850/api
This should result in:
[{“success”:{“username”:“[this is the api-key]”}}]#
Goto Node-RED and install the ‘node-red-contrib-deconz’ pallette
Drag the ‘deconz-event’ node in a flow
Fill in the server details:
Name: Conbee2
IP Adress: [your local ip address for Hassio / deCONZ]
Port: 40850
API key: [the api-key from above]
WebSocket Port: 40860
Followed your path (carefull quotes and double quotes in the forum are not the right ones in curl command line), then I had to do a nmap -p to find the websocket port (8081 in my case). I’m running in Docker over Ubuntu 19, my setup is
Name: Conbee2
IP Adress: 172.30.33.1
Port: 40850
API key: [the api-key ]
WebSocket Port: 8081
Hey all. I’ve googled a bit and not found a working answer to this problem.
All my automations appear to be running on UTC. Interestingly, the time shown in the debug notifications is correct, but timestamp nodes output UTC and my automations don’t appear to be triggering correctly.
Not seeing an answer in this thread. Does anyone have a good solution for this that works across flows?
Hey all, having some issues with Node Red after upgrading either Node Red or HA. I currently run HA on HASS.IO on a raspberry Pi3+. I am not sure what information is needed so I will do my best to add below.
When trying to access node red I get 502: Bad Gateway
This error I get in the homeassistant log 20-01-22 15:54:32 ERROR (SyncWorker_19) [hassio.docker] Can't start addon_a0d7b954_nodered: 403 Client Error: Forbidden ("endpoint with name addon_a0d7b954_nodered already exists in network host")
Inside the Node Red add on, I get the following:
Add-on version: 6.0.2
You are running the latest version of this add-on.
System: HassOS 2.12 (armv7 / raspberrypi3)
Home Assistant version: 0.104.3
Supervisor version: 195
-----------------------------------------------------------
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...
[12:46:57] INFO: Password is NOT in the Have I Been Pwned database! Nice!
[12:47:05] INFO: Password is NOT in the Have I Been Pwned database! Nice!
patching file nodes/ui_base.html
Hunk #1 succeeded at 1243 (offset 712 lines).
audited 36 packages in 5.072s
found 1 moderate severity vulnerability
run `npm audit fix` to fix them, or `npm audit` for details
[cont-init.d] node-red.sh: exited 0.
[cont-init.d] user.sh: executing...
[cont-init.d] user.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[12:48:50] 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"
22 Jan 12:50:54 - [info]
Welcome to Node-RED
===================
22 Jan 12:50:56 - [info] Node-RED version: v1.0.3
22 Jan 12:50:56 - [info] Node.js version: v12.14.0
22 Jan 12:50:56 - [info] Linux 4.14.98-v7 arm LE
22 Jan 12:50:57 - [info] Loading palette nodes
Terminated
[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.
I have tried at this point to uninstall and reinstall as well as resets etc. but have not made any headway. Any help would be greatly appreciated. Please let me know if any more information is needed.
Release v5.0.4
Changes
Updates node-red-node-email to v1.7.2 (#362)
Update add-on installation instructions
Fixes Node-RED dashboard patch to be compatible with 2.19.1 and higher
Updates maintenance/license year to 2020
Funding adjustments