I’m kind of reopening this issue as it’s happening more commonly with our equipment and it’s almost impossible to recover our remote hardware without a very expensive site visit, so I’m really keen to get this fully resolved.
I’ve never really had much trouble remotely updating firmware on Cerbo GX devices, however since about 3.5. onwards, I’m getting communications problems and strange dashboard issues after firmware updates.
Note that our equipment is running Cerbo GX with the Victron GX LTE 4G modem for comms.
We are getting unusual interaction between the Cerbo device and the VRM server:
After updating from 3.64 to 3.66, I get this on the VRM device List:
and on the remote dashboard, it is showing this:
For reference, a working system looks like this:
Looking for any advice from those working on the back end - as there seems to be a common issue here.
@guystewart and @mpvader Just looping you in on this as it seems related to my previous issue - although in this case, we are able to retain remote communications.
I would also like some insight into a resolution to this problem as well. Very similar set-up with our test bench (Cerbo GX and LTE4G modem). I updated it to the latest firmware a while back and since then have lost communications with local Ruuvi sensors and now struggle to maintain a remote access to the equipment. I previously restored the Cerbo to an older version and was able to get it all to function properly. However, I had to go back to 3.66 as I need to test a smart regulator configuration that will be installed on a customer’s vessel that only works with 3.60 and beyond.
Recently tried the factory reset on the cerbo gx (hq2211) and reinstalled the 3.66 update, however the ruuvi sensors are still gone and i have lost all bluetooth connectivity with the cerbo.
