Home Assistant Community Add-on: Node-RED

:tada: Release v1.2.1

This release updates the nodes used by this add-on to the latest and greatest versions.
It also replaces node-red-contrib-google-home-notify with node-red-contrib-cast, which allows you to use your Google Cast and Home devices again for streaming media.

Full Changelog

Changed

  • Upgrades node-red-contrib-home-assistant-websocket to 0.4.3
  • Upgrades node-red-node-ping to 0.0.16
  • Replaces node-red-contrib-google-home-notify with node-red-contrib-cast (#84) (@tjorim)

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck or https://buymeacoff.ee/frenck

There are a number of us experiencing problems here, frenck, and so far our questions have gone unanswered. Maybe this is the wrong venue. Is there a better place to ask for assistance than here?

Thanks.

If there are reproducible errors with an add-on, you can file an issue ticket on the github page for the add-on itself. Just be sure to describe the issue in detail, such as what version it last worked, which version created the issue, any relevant logs, etc.

Things than an issue report would need:

  • Hass.io type: Generic Linux (Ubuntu Bionic, xenial?), ResinOS, HassOS?
  • OS version?
  • Hass.io Supervisor version?
  • Beta channel?
  • Home Assistant version?
  • Add-on version?
  • When did this issue start occurring?
  • Is the used server URL in node-red http://hassio/homeassistant ?
  • Is the password used by node-red to connect to the server a weird long token like string? Your password? Or empty?
  • Please provide Node-RED add-on logs which shows a failure (or taken at the moment the issue occurred)
  • Please provide Hass.io System logs which shows a failure (or taken at the moment the issue occurred)

Take the answers to these questions and put them into a GitHub ticket (or add it to a matching existing ticket).

This is the github issue tracker page for the node-red add-on.

Frenck said to post issue there a few posts up.

I’m having a hard time believing that the problem was fixed by adding

{}

to my previously empty package.json file. Version 1.2.1 up and running now.

I have been struggling with this for hours now,

I am trying to install Node-Red, but keep getting an error that ui-base and ui-tab are missing

    15 Dec 21:33:01 - [info] Server now running at http://127.0.0.1:1880/
    15 Dec 21:33:01 - [info] Waiting for missing types to be registered:
    15 Dec 21:33:01 - [info]  - ui_base
    15 Dec 21:33:01 - [info]  - ui_tab

I’m running on a RP3 and have tried to reinstall 3 times now (I even deleted the Node-Red directory)
Once, it all looked good on the LOG until I tried to start a flow with just a “Debug” node. Then the error shows up again.

I would like to add the Amazon Dash node, however I need to install some dependencies first.

# dependancy on libpcap for reading packets
$ sudo apt-get install libpcap-dev
npm install node-red-contrib-amazondash

Can this be done or is there an easier way with reading Dash events?

Simply installing the dependencies (system packages) and node itself is actually very easy!

Use the system_packages and npm_packages options as defined in the README document.

Thank you… I never knew that.

I’ll try it out now

I did not remove my googlehome-config-node before upgrading, now my flows won’t work because its missing - but none of my flows use any of the nodes anymore… What can I do? If I look at my config nodes there isn’t anything except for HA that I can delete.

:tada: Release v1.2.2

Full Changelog

Changed

  • Upgrades node-red-contrib-bigtimer to 2.0.7
  • Upgrades node-red-contrib-home-assistant-websocket to 0.5.0

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck or https://buymeacoff.ee/frenck

Help please, I know this has been posted before but I can’t find the answer.
I’m running HA 84.6 hassIo

this is my nod red log

[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…

this is my nod red setup

{
“log_level”: “info”,
“credential_secret”: “BaseBall”,
“http_node”: {
“username”: “”,
“password”: “”
},
“http_static”: {
“username”: “”,
“password”: “”
},
“port”: 1880,
“ssl”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“require_ssl”: true,
“system_packages”: [],
“npm_packages”: [],
“init_commands”: []
}

First of all, as mentioned on each page of the forum, use code blocks!

Next, what is the problem? There seems nothing wrong, the add-on is just starting up.

I just started using the add on this week and am amazed at it! I’ve converted a bunch of pieces from my Vera over to it and it is working well. One issue I’m seeing is that I’ve added and remove some entities, but the call service and the events: state node still have an old list of entity ids. I suspect they are being cached somewhere as HA is no longer listing the removed entities and is showing the new entities. While I can manually enter the entity ids, I’d like to get the auto complete working again.

Any ideas?

Thanks!

@sgruby After adding or removing entities in HA, you need to manually restart NodeRed, it does not automatically refresh the entities.

Of course, that makes total sense! I was looking for a way to restart it and then it dawned on me to restart it via the add-on. I restarted HA a few times and thought that it restarted the add-ons, but now that I think about it, the smb service was still running when HA was restarting.

Thanks for the quick response!

Just installed it and keep getting:

Red-Node log: 27 Dec 10:35:55 - HA Auth - Failed to authenticate: myusername
System log: 18-12-27 15:24:34 WARNING (MainThread) [hassio.auth] Wrong login from myusername

Don’t see any other errors…

{
  "log_level": "info",
  "credential_secret": "*****",
  "http_node": {
    "username": "myusername",
    "password": "*****"
  },
  "http_static": {
    "username": "myusername",
    "password": "*****"
  },
  "port": 1880,
  "ssl": false,
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "require_ssl": false,
  "system_packages": [],
  "npm_packages": [],
  "init_commands": []
}

Tried re-installing, rebooting, several various passwords nothing works…

OK I fixed the issue…

What is the solution of the problem?

Fix:

{
“log_level”: “info”,
“credential_secret”: “your_secret”,
“http_node”: {
“username”: “”, <- leave blank
“password”: “” <- leave blank
},
“http_static”: {
“username”: “”, <- leave blank
“password”: “” <- leave blank
},
“port”: 1880,
“ssl”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“require_ssl”: true, <- set to true if using DuckDns and add 1880 port forwarding in router
“system_packages”: [],
“npm_packages”: [],
“init_commands”: []
}

Now you can login using your Hassio credentials…

Hi, When I open UIO I dont have a connection.

Do you have an other proposal?

Thx