s6-rc: info: service legacy-cont-init successfully starteds6-rc: info: service init-nginx: startings6-rc: info: service init-customizations: startings6-rc: info: service init-customizations successfully starteds6-rc: info: service init-nodered: startings6-rc: info: service init-nginx successfully startedup to date, audited 1 package in 1sfound 0 vulnerabilitiess6-rc: info: service init-nodered successfully starteds6-rc: info: service nodered: startings6-rc: info: service nodered successfully starteds6-rc: info: service nginx: startings6-rc: info: service nginx successfully starteds6-rc: info: service legacy-services: startings6-rc: info: service legacy-services successfully started[18:03:39] INFO: [color=var(--success-color)]Starting Node-RED...> start> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js30 Nov 18:03:43 - [info] Welcome to Node-RED===================30 Nov 18:03:43 - [info] Node-RED version: v3.1.030 Nov 18:03:43 - [info] Node.js version: v18.18.230 Nov 18:03:43 - [info] Linux 6.1.59 x64 LE30 Nov 18:03:44 - [info] Loading palette nodes30 Nov 18:03:49 - [info] Dashboard version 3.6.1 started at /endpoint/ui30 Nov 18:03:51 - [info] Settings file : /etc/node-red/config.js30 Nov 18:03:51 - [info] Context store : 'default' [module=memory]30 Nov 18:03:51 - [info] User directory : /config/30 Nov 18:03:51 - [warn] Projects disabled : editorTheme.projects.enabled=false30 Nov 18:03:51 - [info] Flows file : /config/flows.json30 Nov 18:03:51 - [info] Server now running at http://127.0.0.1:46836/30 Nov 18:03:51 - [warn] ---------------------------------------------------------------------Your flow credentials file is encrypted using a system-generated key.If the system-generated key is lost for any reason, your credentialsfile will not be recoverable, you will have to delete it and re-enteryour credentials.You should set your own key using the 'credentialSecret' option inyour settings file. Node-RED will then re-encrypt your credentialsfile using your chosen key the next time you deploy a change.---------------------------------------------------------------------30 Nov 18:03:51 - [info] Starting flows[18:03:51] INFO: [color=var(--success-color)]Starting NGinx...30 Nov 18:03:51 - [error] [server-state-changed:3652c1211685eb51] ConfigError: Entity ID is required30 Nov 18:03:51 - [info] Started flows30 Nov 18:03:56 - [info] [server:Home Assistant] Connecting to http://supervisor/core30 Nov 18:03:56 - [info] [server:Home Assistant] Connected to http://supervisor/core30 Nov 18:03:56 - [error] [api-current-state:客厅区无人] InputError: Entity could not be found in cache for entityId: binary_sensor.presence_sensor_fp2_6517_presence_sensor_130 Nov 18:03:56 - [error] [api-current-state:妹妹房无人] InputError: Entity could not be found in cache for entityId: binary_sensor.dced8308611d_occupancy30 Nov 18:03:56 - [error] [api-current-state:嘟嘟房无人] InputError: Entity could not be found in cache for entityId: binary_sensor.dced83085f8e_occupancy30 Nov 18:03:56 - [error] [api-current-state:主人房无人] InputError: Entity could not be found in cache for entityId: binary_sensor.dced8309073b_occupancy30 Nov 18:03:56 - [error] [api-current-state:客卫无人] InputError: Entity could not be found in cache for entityId: binary_sensor.dced8311212f_occupancy30 Nov 18:03:56 - [error] [api-current-state:主卫无人] InputError: Entity could not be found in cache for entityId: binary_sensor.dced83084dc6_occupancy30 Nov 18:04:02 - [red] Uncaught Exception:30 Nov 18:04:02 - [error] Error: Invalid property expression: unexpected " at position 1 at createError (/opt/node_modules/@node-red/util/lib/util.js:195:13) at normalisePropertyExpression (/opt/node_modules/@node-red/util/lib/util.js:237:27) at Object.getObjectProperty (/opt/node_modules/@node-red/util/lib/util.js:428:24) at Memory._getOne (/opt/node_modules/@node-red/runtime/lib/nodes/context/memory.js:36:26) at Memory.get (/opt/node_modules/@node-red/runtime/lib/nodes/context/memory.js:52:26) at Object.value (/opt/node_modules/@node-red/runtime/lib/nodes/context/index.js:349:43) at CallService.getApiData (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/call-service/controller.js:129:40) at CallService.onInput (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/call-service/controller.js:74:30) at CallService.preOnInput (/opt/node_modules/node-red-contrib-home-assistant-websocket/dist/nodes/BaseNode.js:208:18) at /opt/node_modules/@node-red/runtime/lib/nodes/Node.js:210:26[18:04:02] INFO: [color=var(--success-color)]Service Node-RED exited with code 1 (by signal 0)s6-rc: info: service legacy-services: stoppings6-rc: info: service legacy-services successfully stoppeds6-rc: info: service nginx: stopping[18:04:02] INFO: [color=var(--success-color)]Service NGINX exited with code 0 (by signal 0)s6-rc: info: service nginx successfully stoppeds6-rc: info: service init-nginx: stoppings6-rc: info: service nodered: stoppings6-rc: info: service init-nginx successfully stoppeds6-rc: info: service nodered successfully stoppeds6-rc: info: service init-nodered: stoppings6-rc: info: service init-nodered successfully stoppeds6-rc: info: service init-customizations: stoppings6-rc: info: service init-customizations successfully stoppeds6-rc: info: service legacy-cont-init: stoppings6-rc: info: service legacy-cont-init successfully stoppeds6-rc: info: service fix-attrs: stoppings6-rc: info: service base-addon-log-level: stoppings6-rc: info: service fix-attrs successfully stoppeds6-rc: info: service base-addon-log-level successfully stoppeds6-rc: info: service base-addon-banner: stoppings6-rc: info: service base-addon-banner successfully stoppeds6-rc: info: service s6rc-oneshot-runner: stoppings6-rc: info: service s6rc-oneshot-runner successfully stopped
发表于 2023-11-30 18:09:49
