Luckily the shunt can still show me my SOC over BT but what was working with 3.54 is no longer working with 3.6.2. The so called “smart” shunt is no longer in the list of devices even though it shows up in VictronConnect 
Did you retry an extra reboot or two after loading 3.62. Sometimes new firmware needs 2 or 3 reboots to fully settle.
I’m trying it now. Seems like a bug if the SW needs multiple reboots to work though.
I had the same problem several times with my 3 Mppts … only 2 Mppts were displayed after the 1st reboot and my EM 24 for the AC Out PV was only found after another reboot.
However, the system is stable again.
For sure reboots shouldn’t be necessary.
@boatcoder if you enable remote support then someone can login and check. Is that ok?.
If yes, is it then also ok if we update / downgrade between the versions?
I’m willing to work with you to troubleshoot bugs but not sure I’m into remote changes to my system while I’m 103 miles from civilization and my friends multiplus II RMA is still unresolved after more than a month.
Luckily i was able to reconfig her boat to limp along with one of the two multiplus units but considering my access to parts should something go wrong I’m hesitant to just open up the system to experimentation.
Sort of kicking myself for trusting the update email at the moment.
Hi,
Sorry to hear about such experience; its not how things are supposed to proceed.
It won’t be experimentation, its more to see the detailed logs to better understand where the issue lies.
Meanwhile there are 100.000 + systems on v3.60, and this is quite a rare error report and doesn’t occur on our test systems: hence the only way we’ll move forward is to know more details.
But: if you’re familiar with ssh, then welcome to login and share logs here, for example cat /data/log/messages, both of a bootup where it works and one where it doesn’t. And lsusb output.
I can enable it in a few hours. I know there are lots of working systems out there, i have one and your reputation is what convinced both of us to buy Victron.
Her experience has not been the best though and since the death of her husband I’ve been trying to help keep her afloat electrically and have not been as impressed as i would have expected to be on the service front.
1 Like
solved! 
- see second post below
Sorry to just jump in here. I’m a new user of the Android display with Cerbo system. Just bought both and my experience is identical to the op.
Smart shunt visible on VictronConnect but not displaying just like op.
My software is 3.62.
MultI seems to know shunt is there because it shows 100% SOC….
Your comment that it’s a rare event doesn’t ring true at the moment.
Thanks in advance!
Hey @chutneylover thanks for adding to it; knowing there is more helps with the priorities.
If possible and OK, please enable Settings → General → Access → Remote support so we can login and hopefully see some details in the logs.
How is the SmartShunt connected, using a VE.Direct ↔ VE.Direct cable? Or via VE.Direct → USB?
All of mine are directly connected to the ve.Direct bus, no usb involved
Okay!
The immediate problem appears to be solved.
The initial problem was the smart shunt had become so “unsynchronised” that it wouldn’t play nice with the display.
Victron direct no usb cables.
This is actually mentioned in the documentation.
Second and simultaneous problem was the Bluetooth had frozen (steady blue), but nothing was connected to it…..
A software update 4.16 to 4.19 was required after I restarted the shunt by disconnecting the red wire!
That took two goes. I believe the first update attempt froze the Bluetooth but I can’t prove it…
Second time worked a charm and now the shunt is playing nicely with all the other devices.
Alooong way to go while I customise and fiddle, but reading all the thread’s around this subject sure helped get me on the right track.
Hope this helps someone else.
Regards
Alun
2 Likes