installation issues with 4.2.1

[effen28]

Hello together,

I´m new and a have since the latest version of hue magic 4.2.1 issues with the installation.

After trying to update to 4.2.1, I have no chance to install hue magic.

I get all the time the following error. also after completly new installing of iob on the rasperry pi.

2022-03-21T18:28:24.903Z Installieren : node-red-contrib-huemagic 4.2.1

2022-03-21T18:28:25.089Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production node-red-contrib-huemagic@4.2.1 2022-03-21T18:28:32.412Z [err] npm 2022-03-21T18:28:32.413Z [err] WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 2022-03-21T18:28:34.913Z [err] npm WARN 2022-03-21T18:28:34.914Z [err] deprecated har-validator@5.1.5: this library is no longer supported 2022-03-21T18:28:34.917Z [err] npm WARN 2022-03-21T18:28:34.918Z [err] deprecated uuid@3.4.0: 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. 2022-03-21T18:28:48.559Z [out] 2022-03-21T18:28:48.559Z [out] > es5-ext@0.10.59 postinstall /opt/iobroker/iobroker-data/node-red/node_modules/es5-ext 2022-03-21T18:28:48.559Z [out] > node -e "try{require('./_postinstall')}catch(e){}" 2022-03-21T18:28:48.559Z [out] 2022-03-21T18:28:49.137Z [err] npm notice 2022-03-21T18:28:49.138Z [err] created a lockfile as package-lock.json. You should commit this file. 2022-03-21T18:28:49.141Z [out] + node-red-contrib-huemagic@4.2.1 2022-03-21T18:28:49.141Z [out] added 121 packages from 110 contributors in 22.841s 2022-03-21T18:28:49.175Z rc=0

Hopefully someone can help me with this problem.

And sorry, I´m a complete beginner........

[andesse]

I have the same issue

[ptweety]

Hi all,

even if I've seen the same messages in the log of my dev environment the issue seems to hide from me.

I installed with the following command:

npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-huemagic@4.2.1

Note the --engine-strict option.

These are the versions:

$ npm -v
6.14.15
$ node -v
v14.18.3

I suppose some packages may need an update / replacement in the future.

So. let me track down the dependencies:

"_id": "get-image-colors@4.0.1", "_requiredBy": [ "/node-red-contrib-huemagic" ],
"_id": "get-pixels@3.3.3", "_requiredBy": [ "/get-image-colors" ],
"_id": "request@2.88.2", "_requiredBy": [ "/get-pixels" ],
"_id": "har-validator@5.1.5",  "_requiredBy": [ "/request" ],
"_id": "uuid@3.4.0", "_requiredBy": [ "/request" ],

I haven't found a fast and up-to-date replacement for get-image-colors which is well maintained and has minimal dependencies.

"_id": "color-namer@1.4.0", "_requiredBy": [ "/node-red-contrib-huemagic" ],
"_id": "es6-weak-map@2.0.3", "_requiredBy": [ "/color-namer" ],
"_id": "es5-ext@0.10.59", "_requiredBy": [ "/d", "/es6-iterator", "/es6-weak-map" ],

A possible alternative could be: https://github.com/meodai/color-names - it's activly maintained and has zero dependencies.

[andesse]

@ptweety thanks for figuring this out. I'll wait now for the next release, I won't try it a third time and need to restore my whole system.

[Foddy]

Do you guys have the supported Node-RED version >= 2.1 installed?

https://github.com/Foddy/node-red-contrib-huemagic/issues/351#issuecomment-1075965192

[andesse]

Do you guys have the supported Node-RED version >= 2.1 installed?

https://github.com/Foddy/node-red-contrib-huemagic/issues/351#issuecomment-1075965192

@Foddy ugh... I think a reasonable amount of people here running a Raspberrymatic (Homematic) System with a Redmatic (NodeRed) addon.

https://github.com/rdmtc/RedMatic

This is stuck at 1.2.9 (NodeRed) since s year.

There are already a lot of issues regarding installation problems, I just found out yesterday. In this case, this seems to be the problem for als Raspberrymatic users.

[Foddy]

Hmm.. I should probably remove this requirement in the package.json then. The problem is it makes sense somehow to keep this requirement to get the most out of Node-RED and be able to use new features for the nodes in future :S…