Replies: 1 comment 9 replies
-
If you're running the NR add-on, it sets an environment variable
If you connect to HA using the add-on proxy or directly your entity ids are not going to be different.
It works for "some period"? What stops working? What do your NR logs show? |
Beta Was this translation helpful? Give feedback.
-
I've been using Node-RED running in a docker, and HA in its standard VM, happily talking via node-red companion for at least a year.
My Node-RED updated to Version 3.0, and now my HA-related nodes are unable to connect and on NR startup I get these three errors:
6 Aug 19:52:06 - [error] [server:Home Assistant Connect] Supervisor token not found.
6 Aug 19:52:06 - [error] [webhookrelay:76652f56.8700a] No Webhook Relay token key set
6 Aug 19:52:06 - [error] [webhookrelay:76652f56.8700a] No Webhook Relay token secret set
On the HA side, I'll get:
2022-08-06 14:51:35.432 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139999888081344] Error handling message: Unauthorized (unauthorized)
Clearly this is some sort of login problem and some token gets generated somewhere, but I can't figure out where or how to fix.
What's odd is that if I change the HA configuration in a node red icon and UNCHECK "Using the Home Assistant Add-on" and populate a key, I can connect to HA, although this breaks some of my automations since the entity names seem to differ slightly when using the Add-On vs. not using the add on.
If I think recheck "Use the Add-On" it seems to work for some period.
Things I've tried:
Any ideas would be greatly appreciated since 100% of my automation (and there's a fair amount) is in NR. Thanks!!!
Beta Was this translation helpful? Give feedback.
All reactions