I have two Multipluses and I’ve updated each of them several times (via VRM) but this is the first failure I’ve had - it got to 30% and the last item on the checklist and then eventually gave a popup message in VRM about my not having permission to do it…at the same time I started getting errors in my Node-RED about certain parts of JSONata expressions being missing that wouldn’t go away until I fully rebooted the Cerbo which seems to imply some communication process went wrong. Can anyone tell me what the permission thing could be about? And should I shut down Node-RED before trying again?
What is the load on your cerbo? If you pull the dbus roundtrip time chart it should provide an indication.
My primary issue here is not being able to do the update, I only mentioned Node-RED as a side issue…are you suggesting the Cerbo is too busy and that’s how I could get an authorisation issue? Normally the time is between 0 and 2 with occasional spikes to 4 but the attempted update caused it to spike to 14ms…
If the GX becomes saturated, the process will add additional load, then it is possible for it to fault. In which case it would be prudent to at least stop busy flows, or just disable nodered for the update.
That said <4ms is pretty normal so maybe it was just a once-off hiccup.
OK…will turn it off when I try again…are you able to shed any light on the permission issue though, has anything changed there? I did afterwards migrate my ID on the professional site as part of researching this problem when I went to check on firmware releases - could it be something to do with that not having been migrated before or are there any other possible causes?
It is an incorrect error that sometimes crops up, has previously been an issue in VRM (but widespread at the time), or possibly a timeout, I would not worry about that it is likely a symptom not the cause.