Hi,
Where I can find an explanation of MQTT-RPC broker error #15?
When trying to connect to my smart devices (2 MPPTs and 1 SmartShunt) I am getting this massage:
Does anyone know what to do with it?
Best Regards.
This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hi,
Where I can find an explanation of MQTT-RPC broker error #15?
When trying to connect to my smart devices (2 MPPTs and 1 SmartShunt) I am getting this massage:
Does anyone know what to do with it?
Best Regards.
Hi
Do you still get an error? Have you tried signing out and signing back in again in the VictronConnect settings?
Kind regards,
Thiemo van Engelen
@Thiemo van Engelen (Victron Energy staff)
Yes.
I did what you suggested. Sign out and sing in.
Still get this error #R2
Also I get this massage:
Which is strange since I can get this:
Any ideas?
Best Regards,
Marek
@Thiemo van Engelen (Victron Energy staff)
Is there a problem with my connection to VRM through VictronConnect?
I still get this screen when I start VictronConnect.
Sometimes it is Error Code: #R3
I no longer see the #R15.
It looks like it is a permanent error.
Hi @MarekP
As far as we know there are no problems with the VRM connection in VictronConnect. I suspect that the problem lies somewhere in the network that you are connected to. Error #R3 means that the hostname that is used (vrmapi.victronenergy.com !!) cannot be converted to an IP address. Perhaps there is a form of DNS filtering or ad filtering active on the network and it does not provide access to this name and/or ip address?
Kind regards,
Thiemo van Engelen
Thank you for info about R3 error..
It would help me troubleshoot this problem if you would explain also the other errors I am getting.
MQTT-RPC
R2
R15
VRM
R204
Regards,
Marek
After digging into this problem and reading of all the possible reasons for this problem, I decided to first check if there is a new version of Victronconnect available. Found it on Appstore.
After updating to the latest version this problem vanished.
Best Regards to all,
Marek
28 People are following this question.