After struggling with SSL configuration between Node-Red and my Hass.io setup, I finally found a solution that works seamlessly. I wanted to share my experience in case anyone else is facing similar issues.
Initially, I noticed that my Node-Red instance was having trouble connecting to Hass.io via SSL. The error logs were a bit cryptic, but I realized it was an SSL certificate issue. After some research, I discovered that manually copying the certificates from my Hass.io server to my Node-Red server was the key. Here’s what I did:
-
Installed Node-Red and Necessary Packages: I started by installing Node-Red on my separate server. I also made sure to install the
node-red-contrib-home-assistantpackage to enable communication with Hass.io. -
Edited Settings.js: The next step was to modify the
settings.jsfile in Node-Red. I uncommented the SSL section and pointed it to the certificates I had copied over. This involved specifying the paths to my private key and certificate files. -
Certificate Management: I copied the Let’s Encrypt certificates from my Hass.io server to the Node-Red server. This was a bit tedious, but it ensured that both services were using the same certificates, which is crucial for SSL communication.
-
Testing the Connection: After restarting Node-Red, I tested the connection to Hass.io. It worked like a charm! I was able to add a Home Assistant service to my flows without any issues.
This solution has been a lifesaver for me. Offloading Node-Red to a separate server has also improved the overall performance of my Hass.io setup. If anyone else is dealing with SSL configuration issues, I hope this guide helps you as much as it helped me.
Happy automating! 