search

hardillb / node-red-contrib-alexa-home-skill

A Node-RED node to control things via Amazon Alexa
https://alexa-node-red.bm.hardill.me.uk/
Apache License 2.0
89 stars 42 forks source link

Not usable whit node-red version v2.1.3 #121

Closed Ned-Tom closed 2 years ago

Ned-Tom commented 2 years ago

After installing and configuring the configuration node "by adding user and user name" when you press deploy this plugin stops on node-red v2.1.3. node-err

also when installing i get this log:

-----------------------------------------------------------
2021-11-24T10:53:35.140Z Install : node-red-contrib-alexa-home-skill 0.1.19

2021-11-24T10:53:35.162Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-alexa-home-skill@0.1.19
2021-11-24T10:53:45.831Z [err] npm
2021-11-24T10:53:45.831Z [err]  WARN deprecated har-validator@5.1.5: this library is no longer supported
2021-11-24T10:53:46.107Z [err] npm
2021-11-24T10:53:46.107Z [err]  WARN 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.
2021-11-24T10:53:46.174Z [err] npm
2021-11-24T10:53:46.175Z [err]  WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
2021-11-24T10:53:46.579Z [out] 
2021-11-24T10:53:46.579Z [out] added 139 packages in 11s
2021-11-24T10:53:46.617Z rc=0

I use this plugin in my old configuration but when upgrading nod-red i got this while creating my new clean install.

I don't know what I'm missing here but hope there is an easy fix.

Thanks in advanced. Tom

hardillb commented 2 years ago

Those entries in the logs are npm warnings and can be safely ignored.

Your description doesn't really make sense, because you would be unable to open the nodes configuration dialogues if the nodes are missing.

Best bet is to restart node-red, in the early part of the log it will then show any nodes it considers missing either because they are not installed or because there has been a problem while trying to load them.

Also include information about what version of NodeJS you are using.

Ned-Tom commented 2 years ago

I just restarted the container and everything seem to work "I'm a bit surprised that it was so simple, why i don't think about that"

Also i use Node 17.1.0

But therefore isn't an issue anymore, thanks for the help.