I can confirm the upgrade to NR 1.3.2 worked – and I’ve since upgraded all nodes that needed upgrading – without ANY issues – but for one tiny thing – this time, the NR upgrade script did NOT try to upgrade Node.JS which remained at 10.23.3 – since then I’ve spoken to the guys on the Node-Red forum (Colin and Dave in particular) and FINALLY – I’m BANG up to date with Node-Red AND Node-JS… if only I’d had this knowledge in the past… see this discussion… which includes (vitally) changing a file on the RPi which tells it which version of NodeJS it should be upgrading to… THIS time after rebooting, I used the official Node-Red upgrade script as above – and everything WORKED without any messing with SQLITE, no i2c or serial issues. Thanks to help from the NR forums – I went back to my clone of an earlier NR – but this time, before running the official NR/Node upgrade script – I performed: sudo-apt update Node-Red said “node-red-node-sqlite (0.6.0): sqlitedb, sqlite” so I tried something from a long time ago – deleting /home/pi/.node-red/node_modules/node-red-node-sqlite and re-ran the 4-line script – no further forward. Firstly I2c failed “Error: Could not locate the bindings file” – I was not actually using i2c in NR so I simply removed reference to it in the Node-red setting.js file – this time however that 4-line upgrade script failed – “This is NOT a problem with NPN” it said… so I tried rebooting and ran the SQLITE3 4-liner again – STILL no SQLITE…. – I ran the NR upgrade script which Killed node.js v10 – installed node v12.22.1 and npn 6.14.12 – installed node-red 1.31 (previously was 1.2.9)… no other messages. Update April 2021 – upgrading to NR 1.32. That’s it, nothing else, just those 4 lines EXACTLY as above and despite all those warnings, the SQLITE upgrade worked just fine using NodeJS 10 – well, that is, this has worked well in the past but By April 2021, Node-Red was wanting to use NodeJS 12.x – and I found myself back at square one. They are mainly utterly pointless warnings but watch out for any ERRORS – they will be reasonably obvious. The above represents a TINY fraction of the warning messages you see during the SQLITE rebuild. Once you have done the Node-RED upgrade as user PI…you can use these 4 lines (again as user PI). These days whenever I upgrade Node-Red I use that script above ( a link to which is also included in my own “The Script”) and I subsequently (no reboot required) use the 4 lines below on my Raspberry Pi 4 installations which came to life years ago on RPI2 and Raspbian Stretch and which have been upgraded to Raspbian Buster (now called Raspberry Pi OS) and updated regularly (without starting from scratch or losing valuable data). bash <(curl -sL )Īfter a successful upgrade to Node-Red 1.2.5 (leaving the SQLITE node slightly behind as it can be painful to update when there are node-js upgrades involved), I was feeling quite perky when along came NR 1.3.2 – which completely trashed my setup. Over the years I have upgraded my Node-Red installation which currently statnds at NR 1.32 – using the script below – which you will find on the Node-Red website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |