It seems that with the new VC 6.30, the Multi RS inverter is not seen anymore on the Devices tab of VictronConnect…
When you click on its installation, it says Connecting… goes to 40% and stays there for about 30 seconds.
Then it shows the installation in the System tab, it shows the historic data on Data tab, but in the Devices tab there is no Multi RS.
In another installation with a MP2-3000, it works OK, on all tabs.
Multi RS is with v1.16, Cerbo with v3.32.
If will work only after upgrading to lastest firmwares… hmmm… for me will mean losing a functionality.
It works OK with this combination of firmwares, don’t want to upgrade only to work in VictronConnect…
Worked perfectly until today with 6.24.
Now, if I roll back to 6.24, it doesn’t work with 6.24 either.
LE:
Also in VRM, the Multi RS installation is not saying anymore “Realtime” on “Last Updated” field.
So I’ve lost Realtime updates too, despite “Two way comms” being enabled.
On the MP2 installation, it still saying “Realtime”, so with MP2, like I was mentioning above, it’s OK.
Hi @Barbara
Here it is…
The VC 6.24 on my Android phone behaves the same.
Up until yesterday it worked OK.
The sole fact that up until yesterday with no modifications on my part the 6.24 worked and now it doesn’t, leads to believe that it’s something that changed in the way things are handled on your server side…
Or, if for the VC comms something has changed, why on VRM, since yesterday, without changing anything on my side from config/firmware point of view, the installation with Multi RS has lost Realtime updates?..
Don’t get me wrong, but I dare to ask this because I see it says “AU - Test” system in your video…
Could you please, for a short time to downgrade the Multi RS firmware to 1.16 and see if you can reproduce the issue?
Normally is should not take more than 5 minutes and the settings on the Multi RS should persist…
And, please, if you decide to do it, don’t forget to reboot all after downgrade in order to transmit clean the new config/firmware versions to VRM servers.
Again, today, it was not working…
It seems, that after a while, the mqtt connection/daemon is terminated and when it’s starting again, it can’t connect.
Relevant portion of the mqtt-rpc log looks like this below, something not allowing connections on port 1883.
@4000000069a303a4028e7504 *** starting mqtt-rpc ***
@4000000069a303a812413d9c INFO:__main__:/opt/victronenergy/mqtt-rpc/mqtt-rpc.py v1.100 is starting up
@4000000069a303a8125561dc INFO:__main__:Loglevel set to INFO
@4000000069a303a813053594 INFO:__main__:Paho failed to connect: '[Errno 111] Connection refused'. Retrying in thread, silently. Will report on success.
@4000000069a303a813738bac INFO:__main__:Plugins:
@4000000069a303a8137dd864 INFO:__main__:Starting mainloop, responding on only events
After forcing a reboot, it works again…
Remember, we are talking here about a 3.32 version of the Venus OS…
@4000000069a305cb18ba0e24 *** CCGX booted (0) ***
@4000000069a305db0f1336fc *** starting mqtt-rpc ***
@4000000069a305e90c2d7c2c INFO:__main__:/opt/victronenergy/mqtt-rpc/mqtt-rpc.py v1.100 is starting up
@4000000069a305e90c3d4b0c INFO:__main__:Loglevel set to INFO
@4000000069a305e90e351b9c INFO:__main__:Plugins:
@4000000069a305e90e42c79c INFO:__main__:Starting mainloop, responding on only events
@4000000069a305e90e9446e4 INFO:__main__:Response from broker to connect request (0 is good): 0
@4000000069a305fc20635414 INFO:__main__:vreg-get-set received
.............
