3.60 beta local access issue with vc app

Beta testing Venus OS beta testing
1

I’m not exactly sure with what beta version it was introduced but at some point local lan access to our MP II 5000 GX and connected devices(s) stop working:

  • MQTT-RPC Error Code: #R1
    Screenshot_20250325-115932
    Screenshot_20250325-115932800×1340 34.6 KB
  • GX wifi accesspoint cannot be accessed anymore (fails to connect)
  • GX wifi accesspoint disabled (did not help)
  • GX connected to router by ethernet cable, wifi disconnected
  • Firmware updated to latest v3.60~49 and rebooted
  • MP II is found in Victron connect … BUT: see Error Code above
  • Host IP varies between 169.254.xxx.yyy and the local lan provided DHCP adress, seems not to matter but might be a hint to what the issue is.
  • Access through VRM and by bluetooth still work (but should preferably be disabled)
2

Just checked by reverting to 3.54 stable: this is indeed a beta issue.

3

Re-installed v3.60~49 and issue is back.

4

Hi, could you try with v3.60~53 and let me know if that solves it?

5

Screenshot_20250331-101515
Screenshot_20250331-101515800×1340 34.8 KB

Tested access to SmartBMV through local lan on MP II GX:
v3.54 working
v3.60~53 not working see screenshot

6

Local lan access to SmartBMV tested: not fixed.
See: 3.60 beta local access issue with vc app

7

@mpvader can see the same behaviour trying to access the LAN instance of a Cerbo. The Multi is never LAN accessible, it is just the built in GX that presents itself.
Also using beta VC app.

IMG_5A16371A527C-1
IMG_5A16371A527C-11320×1714 158 KB

8

I can confirm the MQTT-RPC error when connecting with VictronConnect on my Android phone.
VenusGX running v3.54 : works
Pi3 running v3.60~53 : doesn’t work
CerboGX MK2 running v3.60~53 : doesn’t work

9

That’s correct: lan access to cerbo connected gear.

10

It’s not a big issue in a beta firmware where it is acceptable to keep bluetooth access open but it becomes an issue when preparing the hardend connectivity for delivery of a production system.

11

As a side note: why are the historical ‘Trends’ records only accessible through bluetooth and not through other means, such as the lan-via-cerbo route as well as a victrondirect-usb cable?
And can that restriction please be lifted?

12

Hi @UpCycleElectric and all - thanks for your reports!

Fixed per v3.60~57.

Would be great if you could confirm.

13

Will report asap

14

Tested: local access is fixed per v3.60~57
Still no historical trends data when accessing over other means than direct bluetooth but that’s another issue.

15

hi @UpCycleElectric , historic trends data is only accessible over Bluetooth indeed. And making that available in another way is quite a huge project and not a priority at the moment.

16

Hard to imagine why that would be a huge project but I’ll take that on your blue eyes. Still a dearly missed function to access that historical data via (vpn’d) local access, remotely. For monitoring purposes. Even more so for the BMV7xx without BT.

17

Its because that trend data is stored in a separate microcontroller, which takes care of the bluetooth connection.

So to retrieve it, bi-directional comms needs to be set -up, which there currently is not, and so forth and so forth.

18

ps. thanks for confirming that the local access is solved!

19

Makes sense, thanks for sharing