Noticed that after upgrading HA to 2024.11.1 that Node-Red has seemingly broke for me. I can access it via the HA add on however most installed nodes are missing, which obviously has broken many flows. The inject and debug nodes are present but broken. I’ve read that some folks have had websocket issues and instructions for work around were to update the websocket in the pallet. I attempted that and also to reinstall missing nodes but get the following error each time I attempt to update or add anything to the pallet.
I did update to 2024.11.2 today and the same issue is present.
NR is on V4.0.3
Any help here is greatly appreciated.
-----------------------------------------------------------
2024-11-16T00:11:24.884Z Install : node-red-contrib-home-assistant-websocket 0.74.2
2024-11-16T00:11:24.890Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict [email protected]
2024-11-16T00:11:26.496Z [err] npm warn deprecated [email protected]: This module has moved and is now available at @hapi/cryptiles. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.
2024-11-16T00:11:26.499Z [err] npm warn deprecated [email protected]: This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.
2024-11-16T00:11:26.500Z [err] npm warn deprecated [email protected]: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
2024-11-16T00:11:26.504Z [err] npm warn deprecated [email protected]: this library is no longer supported
2024-11-16T00:11:26.516Z [err] npm warn deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
2024-11-16T00:11:26.534Z [err] npm warn deprecated [email protected]: This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
2024-11-16T00:11:26.549Z [err] npm warn deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
2024-11-16T00:11:26.549Z [err] npm warn deprecated
2024-11-16T00:11:26.549Z [err] npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
2024-11-16T00:11:26.588Z [err] npm warn deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
2024-11-16T00:11:26.589Z [err] npm warn deprecated [email protected]: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
2024-11-16T00:11:26.603Z [err] npm warn deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
2024-11-16T00:11:27.137Z [err] npm error code E404
2024-11-16T00:11:27.138Z [err] npm error 404 Not Found - GET https://registry.npmjs.org/node-red-contrib-stoptimer3/-/node-red-contrib-stoptimer3-0.1.2.tgz - Not found
2024-11-16T00:11:27.138Z [err] npm error 404
2024-11-16T00:11:27.138Z [err] npm error 404 'node-red-contrib-stoptimer3@https://registry.npmjs.org/node-red-contrib-stoptimer3/-/node-red-contrib-stoptimer3-0.1.2.tgz' is not in this registry.
2024-11-16T00:11:27.138Z [err] npm error 404
2024-11-16T00:11:27.138Z [err] npm error 404 Note that you can also install from a
2024-11-16T00:11:27.138Z [err] npm error 404 tarball, folder, http url, or git url.
2024-11-16T00:11:27.139Z [err]
2024-11-16T00:11:27.139Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2024-11-16T00_11_24_971Z-debug-0.log
2024-11-16T00:11:27.147Z rc=1
Thanks for the suggestion. I did try safe mode and attempted to update the pallet and also attempted to reinstall the websocket as per this note on Github but did not have any luck. Same error in the logs.
The error occurs because the node-red-contrib-stoptimer3 package cannot be found in the npm registry. I checked manually, and it’s not listed. Boot into safe mode, remove the package, and restart Node-RED. If you were using this node in your flows, you’ll need to find an alternative node to replace it.
Did you manage to solve this? I’m struggling, since 2024.11.2 my node red is really broken.
I’m getting the following:
Flows stopped due to missing node types.
pushover-keys
light-scheduler-settings
google-notify-config
sonos-config
sonosevents-config
ttsultimate-config
sonos-universal
ttsultimate
light-scheduler
weekday
pushover api
timerswitch
And If I look at the palettes, node-red-contrib-home-assistant-websocket is not the latest but wont update.
This is the error log.
2024-11-17T13:41:09.924Z Install : node-red-contrib-home-assistant-websocket 0.74.2
2024-11-17T13:41:10.017Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --omit=dev --engine-strict [email protected]
2024-11-17T13:41:26.015Z [err] npm warn deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
2024-11-17T13:41:26.234Z [err] npm warn deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
2024-11-17T13:41:26.357Z [err] npm warn deprecated [email protected]: this library is no longer supported
2024-11-17T13:41:26.854Z [err] npm warn deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
2024-11-17T13:41:28.266Z [err] npm warn deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
2024-11-17T13:41:28.539Z [err] npm warn deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
2024-11-17T13:41:28.564Z [err] npm warn deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
2024-11-17T13:41:28.626Z [err] npm warn deprecated [email protected]: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
2024-11-17T13:41:29.828Z [err] npm warn deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
2024-11-17T13:42:16.953Z [err] npm error code E404
2024-11-17T13:42:16.999Z [err] npm error 404 Not Found - GET https://registry.npmjs.org/node-red-contrib-stoptimer3/-/node-red-contrib-stoptimer3-0.1.2.tgz - Not found
2024-11-17T13:42:17.000Z [err] npm error 404
2024-11-17T13:42:17.049Z [err] npm error 404 'node-red-contrib-stoptimer3@https://registry.npmjs.org/node-red-contrib-stoptimer3/-/node-red-contrib-stoptimer3-0.1.2.tgz' is not in this registry.
2024-11-17T13:42:17.049Z [err] npm error 404
2024-11-17T13:42:17.049Z [err] npm error 404 Note that you can also install from a
2024-11-17T13:42:17.049Z [err] npm error 404 tarball, folder, http url, or git url.
2024-11-17T13:42:17.073Z [err]
2024-11-17T13:42:17.073Z [err] npm error A complete log of this run can be found in: /root/.npm/_logs/2024-11-17T13_41_11_342Z-debug-0.log
2024-11-17T13:42:17.304Z rc=1
‘’’
Sometimes there are schema updates for node red.
Your affected nodes will then typically be with yellow names, but I have experienced that if you ignore it, then you can suddenly make the yellow text disappear without updating their schema.
The result is that at some point they will simply stop working.
A reinstall will typically download the newest version of the nodes and palettes and the ones the can not find will be errored out in the GUI, instead of keep running with an old version that are not in sync with the schema.
