Pallete Update generates error (Raspberrymatic on RP4)

Hi,
I'm a bit new to this world so sorry if this is well known and simple.

I'm using Raspberrymatic on an RP4. The homeautomisation is done in node-red. At first everything worked well now on attempt to install further Palletes I get an error. The log looks like.


2022-03-20T12:06:09.128Z installieren : node-red-contrib-samsung-tv-control 1.3.15

2022-03-20T12:06:08.830Z npm install --no-package-lock --global-style --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production node-red-contrib-samsung-tv-control@1.3.15
2022-03-20T12:06:12.209Z [err] npm
2022-03-20T12:06:12.210Z [err] WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-K27/45WTa9DazO5s2sLDsL57To+czUAY/UjbFQ+9M5DFcwLXbwDfvyB/3P7jMySZBx7voWQMnbqzrgzlXAr+CA== integrity checksum failed when using sha512: wanted sha512-K27/45WTa9DazO5s2sLDsL57To+czUAY/UjbFQ+9M5DFcwLXbwDfvyB/3P7jMySZBx7voWQMnbqzrgzlXAr+CA== but got sha512-kZpFmhy781IeaTdwoE8P+HFmw3EfxceBut96xWdAjtfRY2N+RPb+6msl/J4PX7HzrPDyxfXWC5P7EFAh9s6DMQ==. (52736 bytes)
2022-03-20T12:06:12.210Z [err] npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
2022-03-20T12:06:12.276Z [err] npm
2022-03-20T12:06:12.276Z [err] ERR! code EINTEGRITY
2022-03-20T12:06:12.276Z [err] npm ERR! errno
2022-03-20T12:06:12.277Z [err] EINTEGRITY
2022-03-20T12:06:12.295Z [err] npm ERR!
2022-03-20T12:06:12.295Z [err] Invalid response body while trying to fetch htps://registry.npmjs.org/node-red-contrib-samsung-tv-control: sha512-K27/45WTa9DazO5s2sLDsL57To+czUAY/UjbFQ+9M5DFcwLXbwDfvyB/3P7jMySZBx7voWQMnbqzrgzlXAr+CA== integrity checksum failed when using sha512: wanted sha512-K27/45WTa9DazO5s2sLDsL57To+czUAY/UjbFQ+9M5DFcwLXbwDfvyB/3P7jMySZBx7voWQMnbqzrgzlXAr+CA== but got sha512-kZpFmhy781IeaTdwoE8P+HFmw3EfxceBut96xWdAjtfRY2N+RPb+6msl/J4PX7HzrPDyxfXWC5P7EFAh9s6DMQ==. (52736 bytes)
2022-03-20T12:06:12.328Z [err]
2022-03-20T12:06:12.329Z [err] npm ERR! A complete log of this run can be found in:
2022-03-20T12:06:12.329Z [err] npm ERR!
2022-03-20T12:06:12.331Z [err] /usr/local/addons/redmatic/var/npm-cache/_logs/2022-03-20T12_06_12_297Z-debug.log
2022-03-20T12:06:12.400Z rc=1

(since as a new user I can add only 2 links I hat to ommit one t in the registry link, so that is not the source :-)) any on how knows what to do?
Thanks René

Did you try a search on the forum for that error code?

Thanks for your fast reply, yes I did try and didn't find it (yet) Similar topics but those solutions didn't work

Change to your .node-red folder and run this command
npm cache clear --force
then try installing from the command line
npm install node-red-contrib-samsung-tv-control
If it still fails then delete the folder
.node-red/node_modules/node-red-contrib-samsung-tv-control
and try again. If still no joy then what to these commands show
node -v
npm -v

hello Colin,
thanks for your extensiv describtion, which I had seen for some other problems like this before. As I'm using raspberrymatic, I'm not in the 100% standard Unix environment (sudo e.g. is not installed which will become important down the road I'm afraid).
So the keep it short it didn't work.
node has version 12.22.7
npm has version 6.14.15 (I know far from current) update didn't work and as sudo istn't installed I couldn't update tru using sudo :frowning:
any further help is gratefully acknowledged

René

Is it specifically that node you can't install or is it any node? Try, for example, node-red-contrib-simple-gate. If not, were you previously able to install contrib nodes?

Did anything significant happen before the problem appeared? A power fail maybe?

Is the device working perfectly in all other respects?

Hi Colin,

the problem is general hence any other I've tried to install had the same issue.

I did remove some other nodes prior to the issue one did have problems, I needed to stop several times until it worked.

Node-red (or here called redmatic) works fins, and I can programm as needed with all the installed nodes, but as said nothing with possibility to include

René

Have you ever been able to install contrib nodes? You didn't make that clear.

I don't understand what that means.

Try
npm -g cache clean --force

Another thought. Try making a complete copy of the .node-red directory (in case this goes horribly wrong), then delete the file package-lock.json in the original and run
npm install
If that doesn't show any errors then try installing the node again (using the npm command, which I hope is what you have been doing in these experiments). If it works then restart node-red.
If the experiment is a disaster then you can restore the original .node-red and restart node-red.

So I did your first suggestion


as you cann see errors.
Yes I've been adding several nodes before. Wenn I wanted to delet one which wasn't doing what I had hoped for. I had to press the inactivate button on the user settings several times prior to truly being able to delete, despite the fact that the node wasn't in use. that is the only problem I occured :frowning:
I'll try your solution from the second thread in a moment and will report..

That isn't the command I suggested. You have forgotten the clean

Is that a Redmatic thing? I don't remember seeing an inactivate button in the display where nodes are deleted. Or do you mean Disable. I wonder whether with multiple clickings there you have somehow messed up npm. I have another more drastic idea if the suggestions so far don't work.

I meant to post what it looks like in a normal node-red
image

Hi Colin,
after your reinstall it worked so I do hope it was a one time issue, maybe due to a power blidge or so. With regard to theinactivate button. I did have to translate from german to englisch for this thread so maybe Disable would have been correct.

Thank you very much for your help.

René

For the future can you tell us exactly which suggestion fixed it please, as this has come up before.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.