Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After updating recent Home Assistant, Node-RED stopped working. After updating, still nothing #1701

Closed
alber70g opened this issue Dec 3, 2024 · 4 comments

Comments

@alber70g
Copy link

alber70g commented Dec 3, 2024

Describe the bug

After updating Home Assistant (I assume, because before everything worked fine), the node-red-contrib-home-assistant-websocket was out of date. I tried updating, but it still gives me the error that flows don't work because certain nodes types were missing:

Flows stopped due to missing node types.

server
ha-device-config
ha-entity-config
poll-state
ha-sensor
api-call-service

To Reproduce

No response

Expected behavior

No response

Screenshots

There's also an error rendering a warning. It shows [object Object]

image

Example Flow

No response

Environment Information

Home Assistant doesn't show up in the top right

image

Additional context

No response

@zachowj
Copy link
Owner

zachowj commented Dec 3, 2024

What do the Node-RED logs display during startup?

@alber70g
Copy link
Author

alber70g commented Dec 3, 2024

Logs
-----------------------------------------------------------
 Add-on: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 18.1.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 13.2  (amd64 / qemux86-64)
 Home Assistant Core: 2024.11.3
 Home Assistant Supervisor: 2024.11.4
-----------------------------------------------------------
 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 274 packages in 2s
64 packages are looking for funding
  run `npm fund` for details
15 vulnerabilities (9 moderate, 6 high)
To address issues that do not require attention, run:
  npm audit fix
To address all issues possible (including breaking changes), run:
  npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
npm notice
npm notice New minor version of npm available! 10.7.0 -> 10.9.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.9.1
npm notice To update run: npm install -g [email protected]
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:48:17] 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
3 Dec 19:48:18 - [info] 
Welcome to Node-RED
===================
3 Dec 19:48:18 - [info] Node-RED version: v4.0.3
3 Dec 19:48:18 - [info] Node.js  version: v18.20.4
3 Dec 19:48:18 - [info] Linux 6.6.54-haos x64 LE
3 Dec 19:48:18 - [info] Loading palette nodes
3 Dec 19:48:18 - [info] Node-RED Contrib Theme Collection version: v4.0.11
3 Dec 19:48:20 - [info] Dashboard version 3.6.5 started at /endpoint/ui
3 Dec 19:48:21 - [warn] ------------------------------------------------------
3 Dec 19:48:21 - [warn] [node-red-contrib-home-assistant-websocket/all] SyntaxError: Malformed JSON in file: /config//node-red-contrib-home-assistant-websocket.json
Unexpected token  in JSON at position 0
3 Dec 19:48:21 - [warn] ------------------------------------------------------
3 Dec 19:48:21 - [info] Settings file  : /etc/node-red/config.js
3 Dec 19:48:21 - [info] Context store  : 'default' [module=memory]
3 Dec 19:48:21 - [info] User directory : /config/
3 Dec 19:48:21 - [warn] Projects disabled : editorTheme.projects.enabled=false
3 Dec 19:48:21 - [info] Flows file     : /config/flows.json
3 Dec 19:48:21 - [info] Server now running at http://127.0.0.1:46836/
3 Dec 19:48:21 - [info] Waiting for missing types to be registered:
3 Dec 19:48:21 - [info]  - server
3 Dec 19:48:21 - [info]  - ha-device-config
3 Dec 19:48:21 - [info]  - ha-entity-config
3 Dec 19:48:21 - [info]  - poll-state
3 Dec 19:48:21 - [info]  - ha-sensor
3 Dec 19:48:21 - [info]  - api-call-service
[19:48:21] INFO: Starting NGinx...
 Live

@zachowj
Copy link
Owner

zachowj commented Dec 3, 2024

It seems the JSON file storing node information got corrupted. Delete the node-red-contrib-home-assistant-websocket.json file from the Node-RED configuration directory and restart Node-RED.

Copy link
Contributor

This issue has been automatically marked as abandoned because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Jan 29, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants