Crashed the system upon adding BLE nodes

im running node-red as a home assistant addon and was playing around downloading ble palettes when i crashed the system. Any and all help is welcome

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: 17.0.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.4  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.1.6
 Home Assistant Supervisor: 2023.12.1
-----------------------------------------------------------
 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
npm WARN deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs

up to date, audited 460 packages in 15s

44 packages are looking for funding
  run `npm fund` for details

25 vulnerabilities (12 moderate, 13 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.2.3 -> 10.4.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.4.0>
npm notice Run `npm install -g npm@10.4.0` to update!
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
s6-rc: info: service legacy-services successfully started
[10:51:06] INFO: Starting Node-RED...

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

31 Jan 16:51:10 - [info] 

Welcome to Node-RED
===================

31 Jan 16:51:10 - [info] Node-RED version: v3.1.3
31 Jan 16:51:10 - [info] Node.js  version: v18.19.0
31 Jan 16:51:10 - [info] Linux 6.1.63-haos-raspi arm64 LE
31 Jan 16:51:12 - [info] Loading palette nodes
31 Jan 16:51:13 - [info] Node-RED Contrib Theme Collection version: v3.1.8
31 Jan 16:51:19 - [info] Dashboard version 3.6.2 started at /endpoint/ui
31 Jan 16:51:21 - [warn] ------------------------------------------------------
31 Jan 16:51:21 - [warn] [node-red-contrib-noble/noble] Error: Cannot find module '../build/Release/binding.node'
Require stack:
- /config/node_modules/bluetooth-hci-socket/lib/native.js
- /config/node_modules/bluetooth-hci-socket/index.js
- /config/node_modules/noble/lib/hci-socket/hci.js
- /config/node_modules/noble/lib/hci-socket/bindings.js
- /config/node_modules/noble/lib/resolve-bindings.js
- /config/node_modules/noble/index.js
- /config/node_modules/node-red-contrib-ignoble/ignoble-node.js
- /opt/node_modules/@node-red/registry/lib/loader.js
- /opt/node_modules/@node-red/registry/lib/index.js
- /opt/node_modules/@node-red/runtime/lib/nodes/index.js
- /opt/node_modules/@node-red/runtime/lib/index.js
- /opt/node_modules/node-red/lib/red.js
- /opt/node_modules/node-red/red.js
31 Jan 16:51:21 - [warn] [node-red-contrib-ignoble/noble] Error: Cannot find module '../build/Release/binding.node'
Require stack:
- /config/node_modules/bluetooth-hci-socket/lib/native.js
- /config/node_modules/bluetooth-hci-socket/index.js
- /config/node_modules/noble/lib/hci-socket/hci.js
- /config/node_modules/noble/lib/hci-socket/bindings.js
- /config/node_modules/noble/lib/resolve-bindings.js
- /config/node_modules/noble/index.js
- /config/node_modules/node-red-contrib-ignoble/ignoble-node.js
- /opt/node_modules/@node-red/registry/lib/loader.js
- /opt/node_modules/@node-red/registry/lib/index.js
- /opt/node_modules/@node-red/runtime/lib/nodes/index.js
- /opt/node_modules/@node-red/runtime/lib/index.js
- /opt/node_modules/node-red/lib/red.js
- /opt/node_modules/node-red/red.js
31 Jan 16:51:21 - [warn] [node-red-contrib-ble/uartBLE] Error: Cannot find module '../build/Release/binding.node'
Require stack:
- /config/node_modules/bluetooth-hci-socket/lib/native.js
- /config/node_modules/bluetooth-hci-socket/index.js
- /config/node_modules/noble-device/node_modules/noble/lib/hci-socket/hci.js
- /config/node_modules/noble-device/node_modules/noble/lib/hci-socket/bindings.js
- /config/node_modules/noble-device/node_modules/noble/lib/noble.js
- /config/node_modules/noble-device/node_modules/noble/index.js
- /config/node_modules/noble-device/lib/util.js
- /config/node_modules/noble-device/index.js
- /config/node_modules/node-uartble/lib/uartble.js
- /config/node_modules/node-uartble/index.js
- /config/node_modules/node-red-contrib-ble/uartble/node-red-uartble.js
- /opt/node_modules/@node-red/registry/lib/loader.js
- /opt/node_modules/@node-red/registry/lib/index.js
- /opt/node_modules/@node-red/runtime/lib/nodes/index.js
- /opt/node_modules/@node-red/runtime/lib/index.js
- /opt/node_modules/node-red/lib/red.js
- /opt/node_modules/node-red/red.js
31 Jan 16:51:21 - [warn] ------------------------------------------------------
31 Jan 16:51:21 - [info] Settings file  : /etc/node-red/config.js
31 Jan 16:51:21 - [info] Context store  : 'default' [module=memory]
31 Jan 16:51:21 - [info] User directory : /config/
31 Jan 16:51:21 - [warn] Projects disabled : editorTheme.projects.enabled=false
31 Jan 16:51:21 - [info] Flows file     : /config/flows.json
31 Jan 16:51:21 - [info] Server now running at http://127.0.0.1:46836/
31 Jan 16:51:21 - [warn] 

---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.

If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

31 Jan 16:51:21 - [info] [GenericBLE] Start BLE scanning
31 Jan 16:51:21 - [info] Starting flows
[10:51:21] INFO: Starting NGinx...
31 Jan 16:51:21 - [error] [pythonshell in:e0f9f4f63e19d55f] configured virtualenv not exist, consider remove or change
31 Jan 16:51:22 - [info] [GenericBLE] Start BLE scanning
31 Jan 16:51:22 - [info] Started flows
31 Jan 16:51:22 - [info] [server:Home Assistant] Connecting to http://supervisor/core
31 Jan 16:51:22 - [info] [server:Home Assistant] Connected to http://supervisor/core
on -> stateChange: poweredOn
on -> advertisingStart: success
31 Jan 16:51:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
31 Jan 16:51:26 - [info] [server:Home Assistant] Connected to http://supervisor/core

First thing I would do would be to uninstall this node. If you go to the FLOW Tabe here on the forum you will notice that it hasn't been updated in 8 years!

I would also uninstall any other blue nodes that you installed.

1 Like

was able to get it straightened out in safe mode and then connecting to ip of home assistant :1880 , delete palettes then reboot

1 Like