Ha-sensor crashed in node-red-contrib-home-assistant-websocket

I have a NodeREd sensor with holds attributes.

It crashed some weeks ago, “ha-sensor unknown”

the flow

I have found this error in nodered logs

4 Aug 10:11:52 - [warn] [node-red-contrib-home-assistant-websocket/all] SyntaxError: Malformed JSON in file: /config/node-red//node-red-contrib-home-assistant-websocket.json
Unexpected token  in JSON at position 0

Any insight ?
I am on a supervised installation

complete log

s6-rc: info: service s6rc-oneshot-runner: starting
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: 14.4.3
You are running the latest version of this add-on.
System: Home Assistant OS 10.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.8.0
Home Assistant Supervisor: 2023.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 11 packages in 3s
found 0 vulnerabilities
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
s6-rc: info: service legacy-services successfully started
[10:11:35] INFO: Starting Node-RED…

start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
4 Aug 10:11:40 - [info]
Welcome to Node-RED
===================
4 Aug 10:11:40 - [info] Node-RED version: v3.0.2
4 Aug 10:11:40 - [info] Node.js version: v18.17.0
4 Aug 10:11:40 - [info] Linux 6.1.21-v8 arm64 LE
4 Aug 10:11:42 - [info] Loading palette nodes
4 Aug 10:11:50 - [info] Dashboard version 3.5.0 started at /endpoint/ui
4 Aug 10:11:52 - [warn] ------------------------------------------------------
4 Aug 10:11:52 - [warn] [node-red-contrib-home-assistant-websocket/all] SyntaxError: Malformed JSON in file: /config/node-red//node-red-contrib-home-assistant-websocket.json
Unexpected token in JSON at position 0
4 Aug 10:11:52 - [warn] ------------------------------------------------------
4 Aug 10:11:52 - [info] Settings file : /etc/node-red/config.js
4 Aug 10:11:52 - [info] Context store : ‘default’ [module=memory]
4 Aug 10:11:52 - [info] User directory : /config/node-red/
4 Aug 10:11:52 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Aug 10:11:52 - [info] Flows file : /config/node-red/flows.json
4 Aug 10:11:52 - [info] Server now running at http://127.0.0.1:46836/
4 Aug 10:11:52 - [warn] Encrypted credentials not found
4 Aug 10:11:52 - [info] Waiting for missing types to be registered:
4 Aug 10:11:52 - [info] - server
4 Aug 10:11:52 - [info] - ha-entity-config
4 Aug 10:11:52 - [info] - ha-sensor
4 Aug 10:11:52 - [info] - server-state-changed
4 Aug 10:11:52 - [info] - api-call-service
4 Aug 10:11:52 - [info] - api-current-state
[10:11:52] INFO: Starting NGinx…

The storage file has gotten corrupted. Delete this file should allow Node-RED to start.

1 Like

Thank you, i had the same bug

You also had it ?!
I also had it recently (since some weeks i’d say)
I tried to delete the filed but without success

I think I had to reinstall nodered addon the first time it occured.

Which I just did, but addon wont start now -_-

Post your logs from the addon page.

Thanks for the advice.
It was the configuration (ssl)

Thus said, I could not get rid of the contrib-websocket crash even after reinstalling and importing my flows.

I restored a 17.0.11 backup and finally got my flows running.