I have a flow that retrieves data from my Tesla Powerwall and posts its to an MQTT server. The PW uses self-signed certs, therefore in order to avoid errors with the HTTP request node I need to start a standalone (non Hassio) Node Red docker container with the argument:
-e NODE_TLS_REJECT_UNAUTHORIZED="0"
Can I get the Hassio Node Red addon to start with the same argument, thus avoiding having to run a standalone container for this one flow?
You should be able to set the environment variable in the settings.js, if you look at the readme around Timezone config, you can do the same thing, but set process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";
I have a structure like that - Synology -> Docker->Hassio->Add-on Node-Red. I have many node-red things on that and works well, But now I need move "moniotring system to my Hassio- Node-RED, I use for that exec node and inside command using the query snmpwalk -v 2c -c public 192.168.126.60 1
and when looking from LOG - then /bin/sh: snmpwalk: not found, when I use same command directly on synology root, then all works.
My question is - how I can add snmp packet to docker ? From node-red palette I added snmp node - that’s not helps.
Now I find - I can go to docker contaniner in synology - but apt-get /yum … don’t works - how can I add packet?
Following discussion here and hope my topic is not “out of place”. I am new to alot of this and wonder if anyone has managed to send a api request from their pc to node-red ? I have home assistant- node-red addon , running om pi4 , and am trying to send a api request from my fibaro home center. Works in browser when i enter; 192.xxx.xx.xxx:1880/endpoint/lgtv/youtube - asks for user/password to node -red. Thanking in advance for any help or links,information, thanks
I was hoping to get a snapshot from motioneye in the notification (HA app) when alarm is triggered. Im using the “snapshot url” in motioneye, in my nodered flow but I dont get any image (notification works). Am i missing something?
On HA 0.107.1, click on Supervisor on side bar, go to Node-RED addon, scroll down to Config part, you will see the npm_packages settings. Something like this:
Hi there,
silly question, but I think I’m missing something.
The documentation states that we can use “!secret” in the configuration for the Addon.
But if I’m placing
password: !secret node_pw
I get Invalid YAML and I’m not able to save the configuration box.
If I’m wrapping this in quotes like password: "!secret node_pw"
I get the following and am not able to save:
Failed to save addon configuration, not a valid value for dictionary value @ data['options']. Got {'credential_se..
@ChrisHaPunkt An easy mistake to make. Notice my TOP line of my Node Red config is:
credential_secret: ‘!secret red_secret’
dark_mode: true
http_node:
username: ‘’
password: ‘’
http_static:
username: ‘’
password: ‘’
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
require_ssl: false
system_packages: []
npm_packages: []
init_commands: []
I thought this would be easy but maybe I’m going blind.
Where are the logs that I can see under Supervisor, Node-Red, log stored?
I have an issue that occurs occasionally, and I want to try to go back in time and see if there’s anything useful in them, but I only usually get a few minutes worth (primarily because of “Sun Stuff” which is chatty and I don’t see how to slow it down, but that’s a different matter).
I’ve hunted around in the docker image the hass.io images and even the containing linux VM in which I run HA and don’t see them. if they aren’t on disk, is there a simple way to put them on disk to persist?
Or better still, to put the debug pane on disk?
Yes, I try to catch this by leaving the node-red window open and debug pane up but the issue I have is intermittent, and Murphy is hanging around, and it never seems to fail when I prepare.
Release
Changes
Updates node-red-contrib-time-range-switch to v1 (#463)
Add troubleshooting step for upgrade (#462)
is it normal ???
?