Hi,
I would like to request a feature similar to the Meshtastic virtual node concept.
The idea is to allow MeshMonitor to expose a virtual MeshCore node or remote node bridge, so that a phone could connect to a MeshCore node that is already connected to MeshMonitor.
For example:
- a real MeshCore node is connected to MeshMonitor
- MeshMonitor exposes this node as a virtual/local node interface
- the MeshCore mobile app can connect to it from a phone
- from the phone, it should be possible to interact with that remote node as if it were connected locally
This would be useful when the physical MeshCore node is not directly accessible from the phone, but it is available through MeshMonitor.
Possible use cases:
- remote access to a MeshCore node from the mobile app
- configuration of a node connected to MeshMonitor
- checking messages, telemetry and node status from a phone
- using MeshMonitor as a bridge between the mobile app and a real MeshCore node
- managing a node without needing direct BLE/USB access from the phone
This would not just be a simulated test node, but a virtual bridge to a real MeshCore node connected to MeshMonitor.
Is this kind of feature planned, or could it be considered for a future version?
Thanks.
Originally posted by @goodprogrammist in #3521
Hi,
I would like to request a feature similar to the Meshtastic virtual node concept.
The idea is to allow MeshMonitor to expose a virtual MeshCore node or remote node bridge, so that a phone could connect to a MeshCore node that is already connected to MeshMonitor.
For example:
This would be useful when the physical MeshCore node is not directly accessible from the phone, but it is available through MeshMonitor.
Possible use cases:
This would not just be a simulated test node, but a virtual bridge to a real MeshCore node connected to MeshMonitor.
Is this kind of feature planned, or could it be considered for a future version?
Thanks.
Originally posted by @goodprogrammist in #3521