I am getting very slow response with node red as well. I had this before when i tried out the new authentication with legacy api, when i changed back to just api it was working fine again, maybe it something to do with them trying to implement that as the new standard, just some thing you may want to look in to.
To be honest i dont even know what the new authentication legacy api is… i am quite new to HA 
OK, so it was to do with the API interface.
Switched to http://hassio/homeassistant and no more error.
Got rid of the delay issue too.
Presumably if you don’t use the direct API it actually goes via the internet and hence introduces a delay.
Anyway working now. Thanks!
Latest Hass.OS (1.9) and supervisor (125).
Btw, the URL is the same regardless if you are using https or not.
1 Like
Disregard. All fixed up
After upgrading to supervisor 125 and HA 0.75.3 the api calls to http://hassio/homeassistant are working again.
Sadly yesterday I found that none of the nodes was running (every HA related node was green “connected” but there was no real communication, or at least the “api-current-state” weren’t updating, so the automations with some condition didn’t run)
Had to restart node-red from hassio panel to get it working again.
Thinking of implementing some kind of watchdog (maybe a HA automation) that watches node-red running and if not restarts the addon (or at least warns me)
I have setup af watch-dog flow with through the guide here.
i dont have any problems with nodes not responding.
Hope it helps
4 Likes
Thanks, I had something similar in mind. I’ll give it a try!
Ever since enabling the new auth component in .69, my log is full of messages about “Please change to use bearer token access” with the node red add-on. I remember reading something about that, but my google fu isn’t working for this issue. I posted this in the hassio and node-red discord room, but figured I would check here too, any help? I think this is causing some slowness / misfires for my automations
Hi! First of all, thanks for the add-on. It has been working great for me for a month.
Recently I had to reflash HassIO for my Rpi 3B+ (with this method, as HassOS USB Boot is not working) as there were troubles with HassIo 0.75 HassIO panel not showing up. Anyways my setup is back alive and I’m trying to get Node-Red working again. Currently HassIO version is: 0.75.3 and Supervisor: 125
I have tried:
- Restoring via snapshot
- Node-Red Add-On Clean install (Deleted the node-red folder in the /config directory, Uninstalled and Installed again).
but no matter what, it just doesn’t fire up.
The Error I’m getting is the following:
> [email protected] start /opt
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
Failed to start server:
SyntaxError: Error parsing /opt/node_modules/options/package.json: Unexpected token in JSON at position 0
at JSON.parse (<anonymous>)
at readPackage (module.js:126:52)
at tryPackage (module.js:136:13)
at Function.Module._findPath (module.js:218:20)
at Function.Module._resolveFilename (module.js:545:25)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/opt/node_modules/ws/lib/WebSocket.js:16:15)
at Module._compile (module.js:652:30)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] 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 [email protected] 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/2018-08-15T18_32_34_969Z-debug.log
Any ideas what could be wrong with my setup? Tried to search for similar issue, but no results.
As seen reported on gitgub HA generates this message when an api call is made using the old auth methods.
As far as I know in v0.75.x the warning is only generated once per api call. Still annoying (specially for an average user that can’t change much in HA) but at least doesn’t fill the whole log screen.
Release v0.6.0
Release v0.6.0! Things are getting crazy now! 
I’ve added support for GPIO! Here, have a Pi! 
This release adds password checks against the HaveIBeenPwned password database and now supports the use of your Home Assistant secrets file! So you can now use !secret nodered_password as your password and the add-on will fetch the actual password from your secrets file. 
Also upgraded: Node-RED; now running on version v0.19.1!
Added
- Enforces authentication and HaveIBeenPwned checks
- Adds support for GPIO
Changed
- Updates node-red-contrib-time-range-switch to version 0.6.1 (#18)
- Upgrades base image to v2.1.1
- Enables SSL by default
- Sets default Shell
- Use empty username/password in default configuration
- Updates README and links
- Upgrades node-red to version 0.19.1 (#20)
- Upgrades NodeJS to 8.11.4-r0
- Downgrades Python to 2.7.15-r1
Removed
- Removes Know issues and limitations section from README
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work 
: https://patreon.com/frenck
1 Like
How do I put the payload from the previous node (msg.payload from a switch node for example) into the entity_id section of my service call? I have a switch node coming in with 0-100 for brightness and I want it to flow into this service node and set the brightness accordingly.
https://i.imgur.com/wBGabbK.png
@smartsoldier That question is not specific add-on question, but more like a general Node-RED question.
You would have more success on getting it answered if you created a separate topic in #third-party:node-red or hop into the Home Assistant Discord chat (channel #node-red)
Understood. Thanks for the advice.
Does anyone know what the issue is here? I receive the following error while starting the addon after updating to the version just released:
v0.6.0 / armhf[cont-finish.d] 99-message.sh: exited 99.
[cont-finish.d] done.
s6-maximumtime: warning: unable to wait for child process: Operation timed out
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.@roninfr Look a little higher, there should be more info. Those logs that matter usually start with FATAL:.
Thanks Got it:
FATAL: You need to set a http_node username!
Is this new to this version?
Yes, authentication is now enforced and passwords are checked against the HaveIBeenPwned Password database. For new installations, SSL is now enabled by default.
Reasoning: “One should do effort to lower the security, not the other way around.”
Ok so the
!secret nodered_password
can be used for credential_secret and the password for the username as well?
Yes, you can use it on all “strings” / text fields.
1 Like