Can’t update palette packages

Third party integrations Node-RED
1

Hello first post here so sorry if it’s not quite right. I wanted to update the homeassistant-web-socket package and was greeted with an error. Any package I update results from n the same error - unsurprisingly. It seems as though node red needs another update ? I am using supervised Core-2021.9.4 with node-red version 10.0.0 so the latest as far as I can tell.

The error output follows.

Thanks
Robert

2021-09-07T19:56:59.128Z Install : node-red-contrib-home-assistant-websocket 0.33.1

2021-09-07T19:56:59.202Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2021-09-07T19:57:02.626Z [err] npm
2021-09-07T19:57:02.626Z [err] ERR! code EBADENGINE
2021-09-07T19:57:02.632Z [err] npm ERR!
2021-09-07T19:57:02.632Z [err] engine Unsupported engine
2021-09-07T19:57:02.632Z [err] npm ERR!
2021-09-07T19:57:02.632Z [err] engine Not compatible with your version of node/npm: [email protected]
2021-09-07T19:57:02.632Z [err] npm
2021-09-07T19:57:02.633Z [err] ERR! notsup Not compatible with your version of node/npm: [email protected]
2021-09-07T19:57:02.633Z [err] npm ERR! notsup
2021-09-07T19:57:02.633Z [err] Required: {“node”:">= 0.10.0 < 0.11.0"}
2021-09-07T19:57:02.633Z [err] npm ERR!
2021-09-07T19:57:02.633Z [err] notsup Actual: {“npm”:“7.17.0”,“node”:“v14.17.4”}
2021-09-07T19:57:02.641Z [err]
2021-09-07T19:57:02.641Z [err] npm ERR! A complete log of this run can be found in:
2021-09-07T19:57:02.641Z [err] npm ERR!
2021-09-07T19:57:02.642Z [err] /root/.npm/_logs/2021-09-07T19_57_02_634Z-debug.log
2021-09-07T19:57:02.653Z rc=1

2

Did you get this to work?

I have the same problem.

3

I’m also getting a similar error. I can’t install any new palette items, and I also cannot update the palette items either.

2022-05-25T13:16:04.312Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-05-25T13:16:08.758Z [err] npm
2022-05-25T13:16:08.759Z [err]  ERR! code EBADENGINE
2022-05-25T13:16:08.764Z [err] npm ERR! 
2022-05-25T13:16:08.764Z [err] engine Unsupported engine
2022-05-25T13:16:08.764Z [err] npm ERR! engine Not compatible with your version of node/npm: [email protected]
2022-05-25T13:16:08.764Z [err] npm ERR!
2022-05-25T13:16:08.764Z [err]  notsup Not compatible with your version of node/npm: [email protected]
2022-05-25T13:16:08.764Z [err] npm ERR! 
2022-05-25T13:16:08.764Z [err] notsup Required: {"node":"^0.12.7"}
2022-05-25T13:16:08.764Z [err] npm ERR!
2022-05-25T13:16:08.764Z [err]  notsup Actual:   {"npm":"8.1.3","node":"v16.14.2"}
2022-05-25T13:16:08.781Z [err] 
2022-05-25T13:16:08.781Z [err] npm
2022-05-25T13:16:08.781Z [err]  ERR! A complete log of this run can be found in:
2022-05-25T13:16:08.781Z [err] npm ERR!     /root/.npm/_logs/2022-05-25T13_16_08_766Z-debug.log
4

If you are using the addon, the configuration page add the line fore safe mode. See documentation page. Once in safe mode you should be able to remove the problem node.

If stand alone version, use --safe with the start command.

5

Similar problem with a possibly different root cause for me (running Home Assistant 2022.7.7,
Supervisor 2022.07.0, Operating System 8.4 and Node-RED 3.0.1 add on).

For example, attempting to update the HA websocket node from the palette yields this set of errors:

2022-07-29T16:35:45.909Z Install : node-red-contrib-home-assistant-websocket 0.44.0

2022-07-29T16:35:47.176Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-07-29T16:35:47.629Z [err] npm
2022-07-29T16:35:47.630Z [err]  WARN config
2022-07-29T16:35:47.630Z [err]  production Use `--omit=dev` instead.
2022-07-29T16:35:49.938Z [err] npm ERR! 
2022-07-29T16:35:49.938Z [err] code ENOTEMPTY
2022-07-29T16:35:49.938Z [err] npm
2022-07-29T16:35:49.938Z [err]  ERR! syscall rename
2022-07-29T16:35:49.938Z [err] npm ERR! path /config/node-red/node_modules/node-red-node-email
2022-07-29T16:35:49.939Z [err] npm ERR! dest /config/node-red/node_modules/.node-red-node-email-9kimBKpy
2022-07-29T16:35:49.939Z [err] npm ERR! errno -39
2022-07-29T16:35:49.940Z [err] npm ERR! ENOTEMPTY: directory not empty, rename '/config/node-red/node_modules/node-red-node-email' -> '/config/node-red/node_modules/.node-red-node-email-9kimBKpy'
2022-07-29T16:35:49.941Z [err] 
2022-07-29T16:35:49.941Z [err] npm ERR! A complete log of this run can be found in:
2022-07-29T16:35:49.941Z [err] npm
2022-07-29T16:35:49.941Z [err]  ERR!     /root/.npm/_logs/2022-07-29T16_35_47_588Z-debug-0.log
2022-07-29T16:35:49.952Z rc=217
6

I think there is some type of bug. I was able to update the HA nodes but I get this error when I try to update the modbus nodes.

7

I have exactly the same problem, with the same node even… A few other nodes as well. Can’t update them, always the same error pops up. Tried disabling the nodes and then updating, but the same thing happens.

Haven’t been able to resolve it so far.

8

Have you been able to fix the problem and can the Node-RED palette packages now be updated without errors?

I’m using Home Assistant 2022.10.2, Supervisor 2022.10.0, Operating System 9.0,Frontend 20221006.0 - latest with Node-RED 13.4.0 and have still problems with updating. It also makes no difference if I start Node-RED in safe mode.

9

Same here and no clue why. Other packages can be updated just fine…

10

Same here

-----------------------------------------------------------
2022-12-10T15:47:28.788Z Install : node-red-contrib-home-assistant-websocket 0.47.1

2022-12-10T15:47:29.872Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2022-12-10T15:47:30.682Z [err] npm
2022-12-10T15:47:30.683Z [err]  WARN config
2022-12-10T15:47:30.683Z [err]  production Use `--omit=dev` instead.
2022-12-10T15:47:40.684Z [err] npm ERR! code ENOTEMPTY
2022-12-10T15:47:40.685Z [err] npm ERR! syscall rename
2022-12-10T15:47:40.685Z [err] npm ERR! path /config/node-red/node_modules/node-red-node-email
2022-12-10T15:47:40.685Z [err] npm
2022-12-10T15:47:40.685Z [err]  ERR! dest /config/node-red/node_modules/.node-red-node-email-9kimBKpy
2022-12-10T15:47:40.685Z [err] npm ERR! errno
2022-12-10T15:47:40.685Z [err]  -39
2022-12-10T15:47:40.687Z [err] npm ERR!
2022-12-10T15:47:40.688Z [err]  ENOTEMPTY: directory not empty, rename '/config/node-red/node_modules/node-red-node-email' -> '/config/node-red/node_modules/.node-red-node-email-9kimBKpy'
2022-12-10T15:47:40.689Z [err] 
2022-12-10T15:47:40.690Z [err] npm 
2022-12-10T15:47:40.690Z [err] ERR! A complete log of this run can be found in:
2022-12-10T15:47:40.690Z [err] npm ERR!
2022-12-10T15:47:40.690Z [err]      /root/.npm/_logs/2022-12-10T15_47_30_619Z-debug-0.log
2022-12-10T15:47:40.703Z rc=217
11

I have the same issue, still no solution?

12

The solution that worked for me was:

  • Disable IPV6 in HA
  • Rename te directory /config/node-red/node_modules/node-red-node-email to something else

After that I was able to update the palettes

13

i have the problem:

2023-02-18T18:16:56.092Z Installieren : node-red-contrib-nina 0.0.1

2023-02-18T18:16:55.177Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected]
2023-02-18T18:16:56.891Z [err] npm
2023-02-18T18:16:56.892Z [err] WARN config production Use --omit=dev instead.
2023-02-18T18:17:01.708Z [err] npm ERR! code
2023-02-18T18:17:01.708Z [err] EBADENGINE
2023-02-18T18:17:01.715Z [err] npm ERR! engine
2023-02-18T18:17:01.715Z [err] Unsupported engine
2023-02-18T18:17:01.715Z [err] npm ERR! engine Not compatible with your version of node/npm: [email protected]
2023-02-18T18:17:01.716Z [err] npm ERR! notsup Not compatible with your version of node/npm: [email protected]
2023-02-18T18:17:01.716Z [err] npm ERR!
2023-02-18T18:17:01.716Z [err] notsup Required: {“node”:"^12.19.0 || ^14.15.0 || ^16.13.0"}
2023-02-18T18:17:01.716Z [err] npm ERR!
2023-02-18T18:17:01.716Z [err] notsup Actual: {“npm”:“9.1.2”}
2023-02-18T18:17:01.723Z [err]
2023-02-18T18:17:01.723Z [err] npm ERR! A complete log of this run can be found in:
2023-02-18T18:17:01.723Z [err] npm ERR! /root/.npm/_logs/2023-02-18T18_16_56_767Z-debug-0.log
2023-02-18T18:17:01.758Z rc=1

Anyone can help me?

It´s not the only Node i can´t install. Also Update are problem.

14

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
patching file nodes/ui_base.html
Hunk #1 succeeded at 1164 (offset 633 lines).
s6-rc: info: service init-nginx successfully started
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘[email protected]’,
npm WARN EBADENGINE required: { node: ‘^12.19.0 || ^14.15.0 || ^16.13.0’ },
npm WARN EBADENGINE current: { node: ‘v18.12.1’, npm: ‘9.1.2’ }
npm WARN EBADENGINE }
npm ERR! Cannot convert undefined or null to object
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-02-18T20_15_18_210Z-debug-0.log
[21:15:26] WARNING: Failed un-installing conflicting packages
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
[21:15:27] INFO: Setting safe mode startup
[21:15:27] INFO: Starting Node-RED…

i don´t know the package…(unsupported enging).

Any help?

15

any progress on this?

same issue here.
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: ‘[email protected]’,
npm WARN EBADENGINE required: { node: ‘^12.19.0 ^14.15.0 ^16.13.0’ },
npm WARN EBADENGINE current: { node: ‘v18.12.1’, npm: ‘9.1.2’ }
npm WARN EBADENGINE }
npm ERR! Cannot convert undefined or null to object
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-02-19T16_54_23_024Z-debug-0.log
WARNING: Failed un-installing conflicting packages

16

Same issues as everyone else, can’t install or update packages. results in “Unsupported Engine” error.