Hi
New to Rio and Node-Red, but not to an awful lot of other stuff.
I’m trying to install node-red-contrib-mssql-plus. I’m trying to do it through the browser and installing via manage palette. The failure I get appears to say that the version of node.js is too old. Am I correct in this, and how does one go about upgrading node.js on the Rio? Via SSH?
Any helps, thanks.
RRR
Here is the failure log:
Welcome to the Opto Forums Russell.
Upgrading nodejs is not currently an option. (Even via shell).
For now, the best option is to find the highest old version of the node you can install.
(I have not used the one you mention, so I don’t have an exact number to suggest).
Terry describes how in this post here:
Thank you Beno. I naively assumed that a quick ssh and package update would do it, I guess I was wrong. I saw the page that Terry uses in his solution, but it wasn’t clear to me what it’s function was. Now I know! Also, sorry for not putting in the actual error message. The forum doesn’t let new users do too much.
I’m very much looking forward to using this system. Thanks again.
RRR
@rrradant Do you recall which version of node-red-contrib-mssql-plus you were able to install in your EPIC? Current version (from 1 year ago) is v0.12.2, but I have gone back several years to v0.9.1 and still not having any success. My EPIC is v3.6.0-b.32 with Nodejs v14.20.0
Do you really need the features of the -plus node? I have a feeling that the mssql node might be different.
If so, the newest old version I found that will install is 0.2.1
The issue is actually it’s dependency, not the actual MySQL node itself.
Regardless, we know its annoying and the good news is that the new version of firmware that will finally fix this newest old version insanity has started the very first steps in our QA cycle. Still no ETA, but its a LOT closer now than the start of the year.
Thanks Ben. I installed v0.2.1 and unfortunately it does not support stored procedures (neither does the regular node-red-contrib-mssql v0.0.7).
v0.2.1 (almost the same as 0.0.7)
latest (taken from a RPi running the latest everything):
Thanks @Beno
Just for clarity, does this mean that the next firwmare update for EPIC (or Rio) will simply have nodejs v16 (or higher)? In other words, when the new firmware is released, this issue will be resolved? Or was there going to be some other release whereby only Nodejs would be updated?
Not ‘simply’, but yes, the new firmware has pretty much new everything.
New Ignition.
New Node-RED
New nodejs
New Python
New…
This problem will be gone gone when its released.
That “simply” sure is doing a lot of heavy lifting. I’m sure the groov developers appreciate @grant1’s summary of their hard work. 
???
I thought ChatGPT was doing all the heavy lifting nowadays.
(/sarcasm)
Rare personal comment… I’m starting up my personal blog again to talk more about AI/ML (I did a lot of blogging when ‘IoT’ was all the rage).
I’ve been trying to use it to write JavaScript for function nodes in Node-RED and some REGEX stuff for the same. Its been really interesting testing the different models.
Personal stuff aside, Benson has tasked Terry and I with keeping up to date and speed with different LLM’s and Pytorch stuff with the view that one day we might see a compelling use case for groov hardware.
Yes, some of our dev’s are starting to see some light use of it now and then, but that’s a different use case.
