I realise that SQLITE3 is an external module and not the responsibility of the Node-Red guys, but honestly, every time there is an upgrade showing in the NR palette manager for SQLITE3 in Node-Red (and thanks to DCJ and others that at least rebuilding works) SQLITE3 has to be rebuilt after stopping …

Righto guys, also valid point that this likely isn't the right forum to get the problem fixed.. Nick, I check "manage palette" regularly just as I do "apt-get update/apt-get upgrade". Anyway this week, the response was (for example) that "node-red-node-sqlite is 0.3.6 - upgrade to 0.3.7". NOW, I'm …

Did you try a fresh npm install in your workspace dir (.node-red)? This has solved most of my update problems when something got stuck, especially with native code. Your dependencies should be declared in package.json anyway, so just delete or move node_modules and more importantly the package-lock…

Kuema - can you please clarify. Assuming I need to stop NR first, and hence then after that, sitting in the /home/pi/.node-red directory as user pi - "rm node_modules" then "rm package-lock.json" then "npm install" ?

[image] scargill: sitting in the /home/pi/.node-red directory as user pi - "rm node_modules" then "rm package-lock.json" then "npm install" ? Exactly. That will reinstall all packages with the latest versions depending on your package.json. Removing the package-lock.json is an important step…

I would be cautious about following this advice. I would first find why you have the problem that you do with the upgrade apparently not working. First I would see what these commands show (run from the .node-red folder). npm list node-red-node-sqlite npm list -g node-red-node-sqlite

Good point, Colin! Almost forgot about global modules. I try to avoid using them because they gave me more trouble than they are worth. Instead I try to keep everything local in my workspace directory. That way I can use the upgrade procedure I described without having to care about global stuff.

Thank you Colin.... I did what you asked from the .node-red dir and got this... pi:.node-red:13:17[127]> npm list node-red-node-sqlite node-red-project@0.0.1 /home/pi/.node-red └── node-red-node-sqlite@0.3.6 pi:.node-red:13:18[0]> npm list -g node-red-node-sqlite /usr/lib └── (empty) So there…

what does npm outdated (in that dir) report ?

It appears the install failed Run the install again from the .node-red directory and copy/paste the whole command and results. The last few lines of the install should tell you whether it succeeded.

Sorry about the delay Dave, broadband here went off earlier. Here.. and this surprises me.. pi:.node-red:15:34[0]> npm outdated Package Current Wanted Latest Location node-red-contrib-blynk-ws 1.0.0 0.9.2 1.0.0 node-red-project i2c-bus …

Node-RED

Node-RED Forum

Sqlite3 constant issues

General

Colin 9 August 2019 17:19 22

If it worked ok then don't need log I think. By log was meant the terminal output.
I wonder whether you ran it from the wrong directory, or forgot the unsafe-perms the first time.

Topic		Replies	Views
Node-Red SQLITE General	6	625	25 June 2019
Node-Red 1.3.1 and sqlite3 again General	27	1774	12 April 2021
Sqlite nodes not working after update? General	10	898	23 January 2021
Sqlite doesn t work after update General	14	4874	24 December 2018
Can't get sqlite node installed General	10	3957	24 July 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Sqlite3 constant issues

Related topics