Why is my grid meter gone after a simple firmware update (v1.08 to v1.10)?
It states in the GX MKII device that it is still communicating, using VE.Can, but all I get is a dash symbol instead of a normal value in VRM and on the display. This is the first time that this happens to me. No idea where to look for what 
B.T.W. The Multiplus II is in passthru mode right now.
Had the same issue with Venus OS v3.55. I downgraded the VM-3P75CTto V 1.08 again then it worked again.
Thanks mate. You nailed it 
Well kind of 
it probably needs a fix by victron @mpvader : whats the proper way to escalate this so your team can look into it?
Sure. A workaround until a proper fix is released. First time for me, in years, that one of my battery wouldnāt charge. Pretty shocking I must say.
I had the same problems today, but after updating the Cerbo software to version 3.66, it is working normally again.
I had a similar issue when updating my VM to 1.08 a couple of weeks ago.
At that time the Cerbo GX was running FW 3.5x and after the update the VM was not detected by the installation any more (even after all sorts of resets and reboots - no help) and the Multi Plusses went into āPassthroughā mode.
Much later during troubleshooting I updated the GX to 3.64 (as far as I remember, at least 3.6x) a the VM was immediately back on line. I checked the release notes to see if there were any restrictions published regarding FW compatibility, but I didnāt find any. Same for the a.m. issue with VM FW 1.10.
I know Victronās policy is āDonāt update without a reasonā and I normally donāt. But any imcompatibilities that render devices inoperative MUST be published. If only for more effective troubleshooting.
Best regarrds, Jochen
Iāll check if there is a minimum Venus OS firmware version to be used with the VM-3P75CT and confirm back.
Thanks for your reports
Moin!
This morning I have made the firmware upgrade on my VM-3P75CT [VM3] device from V1.08 to V1.10. The Victron Connect App gave me the hint for the upgrade.
The VM3 is connected via VE.Can to the gx device (instance 0).
(ā¦and in my special case via modbus; instance 40)
After the upgrade my ESS goes to PASSTROUGH. Mhhhhā¦.
In the cerbo gx console I saw voltage and current values but no POWER values in the list.
The Victron Connect App shows new values, Phase Sequence and others.
Could it be, the data format (VE.Can) was changed?
I inspected the gx device. Here was also an firmware upgrade (to V3.66) available. Made this.
Power values are now visible. The ESS runs.
Ergo:
Best Regards
M.
Moin!
Yes it must be VE.Can related. I pulled the RJ45 plug out of it, and that made it work for a second or so. After that it was broken again, yet it states that it is connected and communicating.
I cannot update to v3.66 due to Enphase Envoy related issues that we need to get sorted first.
How can I install an OLDER firmware version the VM3ā¦. a good knowledge for the future?
For older versions I use https://professional.victronenergy.com
Something positive:
No problems updating the firmware to 1.10.
Operation via CAN works smoothly with 3.6X.
@mpvader Iām not sure if this is the same issue but it appears to show wattage in the remote portal but not in VRM I changed mine to EV so Iām not sure if itās the same as I was told that 1.10 wasnāt implemented into the VRM so would give wattage. Cerbo GX running 3.65 See screen shots
Hi Dirk. Iām not even surprised. Still. A warning would have stopped me from updating to v1.10 Anyway. Sooner or later I too will use v3.66 but for now Iām stuck.
Hi,
what restrictions do you have about Enphase Envoy that prevent you from updating?
And what Venus OS version do you have? I couldnāt find it when I quickly skimmed through it.
Have you tried using Ethernet instead VE.CAN or did you a downgrade?
Ethernet runs in my environment, all the time. It was the backup solution for me until I found the cause of the communication failure.
I switched from Ethernet to can about other issues 
Oh that is more a matter of not having enough free time to convert some old scripts and a NodeRED flow or two to the new virtual PV inverter. Iām still using v3.55 on the Cerbo at home. I use Ve.Can and simply restored v1.08
Simple solutions are often the best.
Virtual PV inverter with shellys are easy, but also not as easy as expected.
