I've read many discussions, articles etc regarding firmware updating of Victron devices.
This is what I understood:
Now my questions are:
Thanks a lot.
Hello you all
I have been working on the Cerbo GX pretty much the last days and also playing around with Node Red, which I have to say, offers a lot of possibilities if you dont need to get your hands dirty with Modbus Communication, anyways ... I wonder if it is possible to update the firmware and install the large image in a Cerbo GX with an SD/USB stick because in some places I dont have internet access and for being honest, I havent found the way of doing it without using "Online Updates".
Thanks a lot !
Just installed new firmware on my Cerbo GX, updated from 2.80~21-large-23 (20210925...) to v2.90~12 (20220606...) which is also LARGE firmware.
After update, my node-red flows are EMPTY!! and even when I tried to start from backup, the older firmware, still empty FLOWS... Is there any way to return those?
Should the firmware upgrade clear flows from node-red or did I experience some major bug? I understand that node-red is updated a few versions up, was it 2.0.5 and after update 2.2.2 or something like that, but is it meant to clear all flows? Where to get them back...
Raspberry pi 3B+, VenusOS Large V280.11/20
I clicked "update to 1.4.2" by the victron energy nodes in the node-red palette. I currently have 1.4.1 installed and working. The installation failed with the following output in the event log:
2021-09-07T04:44:28.988Z Install : @victronenergy/node-red-contrib-victron 1.4.2
2021-09-07T04:44:29.152Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict @email@example.com
2021-09-07T04:45:08.431Z [err] npm
2021-09-07T04:45:08.432Z [err] WARN rollback Rolling back @firstname.lastname@example.org failed (this is probably harmless): ENOTDIR: not a directory, lstat '/data/home/root/.node-red/node_modules/@victronenergy/node-red-contrib-victron'
2021-09-07T04:45:09.965Z [err] npm
2021-09-07T04:45:09.965Z [err] ERR! code EEXIST
2021-09-07T04:45:09.966Z [err] npm ERR! syscall
2021-09-07T04:45:09.967Z [err] mkdir
2021-09-07T04:45:09.967Z [err] npm
2021-09-07T04:45:09.967Z [err] ERR! path /data/home/root/.node-red/node_modules/@victronenergy
2021-09-07T04:45:09.967Z [err] npm
2021-09-07T04:45:09.968Z [err] ERR! errno -17
2021-09-07T04:45:09.989Z [err] npm
2021-09-07T04:45:09.989Z [err] ERR! EEXIST: file already exists, mkdir '/data/home/root/.node-red/node_modules/@victronenergy'
2021-09-07T04:45:09.990Z [err] npm ERR! File exists: /data/home/root/.node-red/node_modules/@victronenergy
2021-09-07T04:45:09.990Z [err] npm
2021-09-07T04:45:09.991Z [err] ERR! Remove the existing file and try again, or run npm
2021-09-07T04:45:09.991Z [err] npm ERR!
2021-09-07T04:45:09.992Z [err] with --force to overwrite files recklessly.
2021-09-07T04:45:10.080Z [err] npm ERR! A complete log of this run can be found in:
2021-09-07T04:45:10.080Z [err] npm
2021-09-07T04:45:10.081Z [err] ERR! /home/root/.npm/_logs/2021-09-07T04_45_10_053Z-debug.log
When I ssh into the raspi and go to the node_modules directory I see that @victronenergy is not a directory but a file with 0 bytes. The file config.nodes.json file, however, seems to point to "/usr/lib/node_modules/@victronenergy/node-red-contrib-victron/src/nodes/config-client.js" so maybe that's why the update do not work.
My question is, how do I make it work without screwing something up? :)
I would like some clarity please before I continue.
Which file do I use to do a manual firmware update, seems like this is not clearly stated in an easily accessible place. (I did look, maybe I am just unlucky in finding it.)
When one does a manual update what happens to all your settings? Do you require a settings backup before the update and then a restore of just the settings? If so then just to be clear how does one do this.