I’ve found that by setting a smartshunt (v4.19) to DC generic source, it makes the settings unreachable from VictronConnect.
The device is still alive in the Cerbo & VRM device lists but I can’t get to the settings. Tried a shunt power cycle, and deleting the device. Bluetooth is disabled so I’m stuck here. Cerbo v3.80~14 & v3.72 same results.
With victron connect since the BT is not available were you trying over the vrm tab in victron connect?
Yes VRM to Victron Connect or VictronConnect using VRM. I was able to change the firmware by uploading a file using VRM, no change in behavior.
It’s happened on two shunts. First one was a switch from alternator to generic source. The second was as a test, DC load to generic source.
Update: I was able to recover both shunts by using VictronConnect locally with a ve.direct to USB cable, bypassing the Cerbo.
I can reproduce the problem by selecting generic source when monitor mode is DC Energy Meter.
Invalid enum?
WRN.bmv: BMV monitor mode changed from 6 to -1. Exiting.
Hi,
Thank you for reporting this. I can confirm that this is a problem in VictronConnect and we are looking into it.
With kind regards,
Thiemo van Engelen
As a possible hint towards to cause: I remember something similar happened around the time virtual devices were introduced, which had to do with stale device ID’s and bookkeeping thereof. Back then we had to disable virtual devices, disconnect VE-direct devices, delete devices from VRM and GUI, reboot VenusOS, and step by step adding devices back in.