Share Remote Console via a private link – is that possible?

DIY
, ,
1

In VRM, I can share my installation via a private link. The recipient doesn’t need an account and can view the installation.

My question is: can I also share the Remote Console via a private link? That would be perfect. Temporary users could see the current battery SOC, … in the new UI.

2

Over the internet no. There will need to be some insecurity measures in place like authentication or a login

Over a local LAN - easily.

3

Why not view the remote console via VRM?

4

Trying to avoid the customer needing an account…
Viewing a system is different to being able to navigate the console.
Not all user levels even allow the console view (I.e. basic user level)
You would also need to make it view only over the vrm. So it can’t be altered

5

Thanks for the replies. I realise I didn’t make my question clear enough. Here’s a clearer version.

There are guests at the installation. They need to be able to see the current consumption and battery charge (it’s an off-grid system). On site, there’s a Cerbo GX with a Touch 50. The Touch 50 is connected to the display in the lounge. Controls are normally locked (using a button on the Cerbo GX), so it’s just a display of the “Quick View”, with no controls available.

It would be useful if guests could also view this display on their mobile phones via a link (e.g. a QR code). But it should be read-only. I really like the Quick View in the new UI. Is this possible?

6

A work around for now would be to make the GX a static IP on the network.
Then just have a QR code that is the IP address of the console over LAN.
The level on the console locally would have to be set to user as the touch works on console over lan.

7

Thanks very much for the tip, I’ll give that a try.

8

Depending on your LAN configuration, you may be able to have a human-friendly URL in addition to the IP address on a QR code.

Your LAN probably uses IP numbers within one of the three IETF RFC 1918 private IPv4 networks (10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16). These IP addresses are not publicly routable, meaning your ISP won’t allow them to traverse the ISP’s own network. Conventionally, people assume this means you cannot have records for LAN hosts in your regular DNS server, but generally you can. Forward DNS (that is, converting a hostname like “energy.example.com” to an IP address like 10.35.12.68) is agnostic of the network address in the value. Reverse DNS can be trickier (but still doable), but you dont need reverse DNS for this situation.

I started to write a long explanation of how this works and several ways it can be implemented, but I stopped because (1) you may not be interested, (2) you may already know all of that, or (3) my previous paragraph may be utterly confusing if you’re not a network wiz. Instead, I’ll just say that if this discussion would be useful to you, feel free to ask, and I can elaborate.

9

I understand it now.

10

Thanks for the great explanation. That sounds like a good way forward. I should be able to test it in the next 2–4 weeks, once I’m back on site.