Access to Node-Red Add-on

[timmills]

Claude cant seem to authorize to the Node-Red Add in while running witin HA. External Claude can access Node-Red any ideas?

[1liminal1]

I had to tell it to use the API and set 'leave the front door open' :(

It does work though

[ESJavadex]

Hi @timmills, thanks for the report!

Why this happens

Home Assistant runs each add-on in its own isolated container for security. When Claude Code tries to authenticate with the Node-RED add-on, the request comes from a different container, which can cause authentication issues.

Solutions

Option 1: Use Node-RED's WebSocket API (recommended)

Node-RED exposes a WebSocket API that Claude can use directly. From the Claude terminal, Claude can interact with Node-RED via the API instead of going through the browser authentication flow.

Option 2: Configure Node-RED with static token authentication

Go to Settings → Add-ons → Node-RED → Configuration and edit node-red.conf to add simpler authentication.

Option 3: Add-on volume mapping (if editing Node-RED flows)

If you want Claude to edit Node-RED flows directly, we can add the Node-RED data directory to the add-on's volume mounts in a future release.

---

@1liminal1 thanks for sharing the API approach! That's a good workaround — using the WebSocket API directly bypasses the browser-based auth flow.

Let us know if any of these solutions work for you!

[1liminal1]

Yeah, my work around is really not great :( having a volume map to NR would be best

[mojatt]

Second vote for Option 3! :)

[ESJavadex]

Estado (triaje, jul 2026)

Dos cosas distintas aquí:

• Editar flows/config de Node-RED — depende de dónde los guarde tu instalación. El add-on de Node-RED suele almacenar en /config/node-red/, que este add-on ya ve vía config:rw; si es tu caso, Claude puede editarlos hoy. Para add-ons que usan el layout moderno /addon_configs/<slug>/, haría falta el mapping addon_configs:rw (la "Opción 3"). Es un cambio pequeño pero implica ampliar permisos + una release, así que lo dejo como decisión de producto, no lo meto en caliente.

• Interacción en runtime con Node-RED (disparar/leer flows) — sigue necesitando la API WebSocket de Node-RED (el workaround de @1liminal1 con la API + token). La auth cross-addon entre contenedores es la parte no trivial.

• Desconexiones (mencionadas de pasada): ✅ resueltas con la persistencia tmux de 2.0.13.

Dejo el issue abierto para (a) decidir si añadimos addon_configs:rw y (b) el acceso vía API. Votos a favor de la Opción 3 anotados (@mojatt, @1liminal1). Gracias a todos.