I am getting this error
20 Aug 02:07:49 - [error] [server:Home Assistant] Home assistant connection failed with error: Connection to home assistant could not be established with config: https://aabbcc.duckdns.org:8123
Even after a fresh install…
You should not use that URL. Please use http://hassio/homeassistant as the server URL.
After inserting / setting that URL, restart the add-on so the add-on can take care of the authentication for you.
Please check previous posts in this topic, for more details, which makes your question obsolete to begin with.
Thank you for the quick response. I am new to Node-RED. I just installed this an hour ago. This worked like magic. Thanks a ton @frenck.
Anyway to disable this or is it checked locally?
Just use a different, better password, security first! Otherwise, please read the documentation.
I sense a small concern here. If this is the case, let me explain:
The password are not checked locally, since the Password database of HaveIBeenPwned is about 10Gb.
So the password is checked against HaveIBeenPwned.com using their API.
However, we are not sending your password and are using the K-Anomity model for this. It works as follows:
- You password will be hashed using SHA-1.
- The first 5 characters of this resulting hash is send to the API of HaveIBeenPwned.
- HaveIBeenPwned will respond with all the hashes, in their database, that start with those 5 characters.
- We locally check the received hashes from HaveIBeenPwned against the full hash of your password in step one.
- If we’ve found a match, well… We stop with a warning.
TL;DR: We do use a public service, but we DO NOT send your password over the wire. NEVER EVER.
The code is publicly available, so feel free to check it out:
1 Like
I am using node-red-contrib-moment which is my workaround for the relative_time bug in template sensors.
Sadfully, the payloads are generated in English like “a minute ago”.
Is it possible to change the locale of Node-RED somehow?
greetz Bob
Wow, what a nice explanation. Thank you really much 
My Node-RED is stuck in a boot loop. It began right after I tried to add alexa-local to my palette. Getting this repeatedly:
> 21 Aug 11:31:46 - [info] Started flows
> 21 Aug 11:31:46 - [red] Uncaught Exception:
> 21 Aug 11:31:46 - Error: bind EADDRINUSE 0.0.0.0:1900
> at Object._errnoException (util.js:992:11)
> at _exceptionWithHostPort (util.js:1014:20)
> at _handle.lookup (dgram.js:266:18)
> at _combinedTickCallback (internal/process/next_tick.js:141:11)
> at process._tickCallback (internal/process/next_tick.js:180:9)
> 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-21T16_31_46_909Z-debug.log
I tried deleting the 2 json package files in config/node-red, but it didn’t help. I have a backup from a week ago, but I’d really like to get a current copy of my data before I reinstall. Where can I find it?
EDIT: \\hassio\config\node-red\.flows.json.backup
Whew. Didn’t see in in Windows initially, since it starts with a period.
1 Like
If you have the Samba addon running, you can access your data in the ‘/config/node-red’ folder:
In Windows Explorer:
\\HASSIO\config\node-red
/edit after your edit:
Why not the flows.json? It should be more recent than the .backup?
Since i updated HA to 0.76.1 and the addon to 0.6.1 it wont start
[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...
-----------------------------------------------------------
Hass.io Add-on: Node-RED v0.6.1
Flow-based programming for the Internet of Things
From: Community Hass.io Add-ons
By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
armhf / HassOS 1.7 / HA 0.76.1 / SU 127 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
INFO: Password is NOT in the Have I Been Pwned database! Nice!
FATAL: You need to set a http_node username!
[cont-init.d] 10-requirements.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] syncing disks.
[s6-finish] sending all processes the TERM signal.Have you set that in the config for the addon?
I havent configured it before. Is it necessary? What is it used for?
It was mentioned by Frenck in the change-log of a recent update, I believe.
Always read them (and the documentation for the addon of course).
/edit
And check the error itself, not to forget. It tells you what’s wrong.
Seems to fix the problem. Thank you for your help
1 Like
Haha. I must be blind. I may have deleted it while dicking with the package fails, or more likely I’m a moron.
FYI, got the same boot looping immediately after installing alexa-local again. I guess it could also be the imported flow for it.
The default location for dashboard images is: \\hassio\config\node-red\node_modules\node-red-dashboard\dist\
1 Like
It’s only necessary if you make use of node’s HTTP endpoint APIs but since 0.6.0 the fields now have to have something in them.
I don’t have a use for them so I just mashed the keyboard in all 4 fields so it would make a random enough string to pass the password database check.
I’m using httpNodes with IFTTT webrequests. How do I setup IFTTT that it can access the http_node? Also, my mqtt does not seem to get through anymore either. Any ideas?
EDIT: Got it: “https://user:[email protected]”
1 Like
Am I completely stupid or what. Since going to 0.6.1 Node Red I can’t deploy anything because it says “not authorized”. Docs say * or read so assume * is all.
"users": [
{
"username": "*******",
"password": "*********",
"permissions": "*"
},
{
"username": "********",
"password": "**********",
"permissions": "*"
}
],
"http_node": {
"username": "*************",
"password": "*************"
},
"http_static": {
"username": "*****************",
"password": "****************"
`I upgraded hass to 0.76.2 and node red to 0.6.1 on my rpi3 and now nodered not working:
CONFIG:
{
“log_level”: “info”,
“credential_secret”: “test”,
“users”: [
{
“username”: “test”,
“password”: “test123”,
“permissions”: “*”
}
],
“http_node”: {
“username”: “test”,
“password”: “test123”
},
“http_static”: {
“username”: “”,
“password”: “”
},
“port”: 1880,
“ssl”: false,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”,
“require_ssl”: false,
“system_packages”: [],
“npm_packages”: [],
“init_commands”: []
}
Error:
[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...
-----------------------------------------------------------
Hass.io Add-on: Node-RED v0.6.1
Flow-based programming for the Internet of Things
From: Community Hass.io Add-ons
By: Franck Nijhof <[email protected]>
-----------------------------------------------------------
armhf / Resin OS 2.3.0+rev1 / HA 0.76.2 / SU 127 / stable
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing...
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing...
[cont-init.d] 10-requirements.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] syncing disks.
[s6-finish] sending all processes the TERM signal.