Przy uruchomieniu node-reda wyświetla sie komunikat “set the base url correctly”, wszystkie nody działają. Jak sie pozbyc tego komunikatu gdzie jest błąd?
No mam tak samo i sie błąd pokazuje
nie pomogło, cały czas to samo, ten błąd zaczął wyskakiwać po ostatnie aktualizacji Node-Reda
artpc
15 Sierpień 2024 13:08
6
To jeszcze napisz jaką masz wersję NR
I wersję node-red-contrib-home-assistant-websocket
I sprawdź czy nie masz innych serwerów na liście.
Node-Red v4.0.2
artpc
15 Sierpień 2024 13:56
8
Access token masz wygenerowany w HA i dodany w NR?
nie miałem, a jak dodałem nic sie nie zmieniło, i dodatkowo zauważyłem ze jak naciskam przycisk Deploy, to raz czekam po 5 min a innym razem 5 s, czasami pokazuje błąd “Deploy failed: 502: Bad Gateway” i musze kliknąć jeszcze raz
artpc
15 Sierpień 2024 14:31
10
Wygeneruj token w HA. wpisz go w NR, deploy i zrestartuj NR.
Typowe błędy gdy contener jeszcze nie wystartował, albo ma problemy z połączeniem.
nawal
17 Sierpień 2024 10:10
12
Mam podobny problem. U mnie NR uruchamia się bez problemu, ale po naciśnięciu Deploy raz zapisze, a wiele razy czekam i failed 502. Co ciekawe gdy wejdę na NR z telefonu wszystko się zapisuje bez zwłoki po naciśnięciu na Deploy. Co jeszcze ciekawsze, gdy się połączę z HA przez ZeroTier, problemy znikają. To wszystko zaczęło się po ostatniej aktualizacji NR.
artpc
17 Sierpień 2024 23:50
13
Długi Deploy i błąd 502: Bad Gateway
opened 11:34PM - 16 Aug 24 UTC
# Problem/Motivation
I recognized that I am not able to deploy node-red chang… es anymore... It never stops loading...
Is there probably an issue with any new home assistant update?
## Expected behavior
Usually, it just takes some seconds to deploy changes
## Actual behavior
Now it starts loading but never completes the deployment of the changes
## Steps to reproduce
It's probably a problem with a new HA or node-red update, so I don't know.
## Home Assistant Version
Core
2024.8.2
Supervisor
2024.08.0
Operating System
13.0
## Node-Red Add-On Version
Current version: 18.0.5
## Node-Red Companion Version
Current version: 4.0.2
Problem z uruchomieniem dodatku.
opened 05:51PM - 13 Aug 24 UTC
# Problem/Motivation
I keep receiving the following dialogbox - after clickin… g start i reappears
When I try it in the HA app on my iphone it goes to the log after 3 times
## Expected behavior
After clicking start add-on I would expect that Node Red starts
## Actual behavior
The dialog box keeps opening
## Steps to reproduce
I don't know for sure, but the only thing that has happened is that updates have been installed.
## Log
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 18.0.5
You are running the latest version of this add-on.
System: Home Assistant OS 12.4 (amd64 / qemux86-64)
Home Assistant Core: 2024.8.1
Home Assistant Supervisor: 2024.08.0
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
up to date, audited 258 packages in 3s
25 packages are looking for funding
run `npm fund` for details
15 vulnerabilities (2 moderate, 13 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.8.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.8.2
npm notice To update run: npm install -g npm@10.8.2
npm notice
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[19:50:16] INFO: Starting Node-RED...
s6-rc: info: service legacy-services successfully started
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
/opt/node_modules/@node-red/util/lib/util.js:772
})
^
SyntaxError: Unexpected token ')'
at internalCompileFunction (node:internal/vm:76:18)
at wrapSafe (node:internal/modules/cjs/loader:1283:20)
at Module._compile (node:internal/modules/cjs/loader:1328:27)
at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
at Module.load (node:internal/modules/cjs/loader:1203:32)
at Module._load (node:internal/modules/cjs/loader:1019:12)
at Module.require (node:internal/modules/cjs/loader:1231:19)
at require (node:internal/modules/helpers:177:18)
at Object.<anonymous> (/opt/node_modules/@node-red/util/index.js:19:14)
at Module._compile (node:internal/modules/cjs/loader:1364:14)
Node.js v18.20.3
[19:50:16] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[19:50:16] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Tymczasowe rozwiązanie to wejście po adresie IP http://HAIP:1880
