Meshmonitor -> Virtual Node - `Packet Feed?

[antonov124]

Hello, ive a Question, my Idea is: Companion > Meshmonitor > RemoteTerm for Meshcore. RT connect correctly to the Virtualnode Port, but there is no packet feed, and so its not possible to me, for exacmple to use channel finder. Any Ideas?

[Yeraze]

sorry, I'm not familiar with "RemoteTerm".. Can you share some info ?

[antonov124]

Here is the Project https://github.com/jkingsman/Remote-Terminal-for-MeshCore

Thx :)

[Yeraze]

interesting.. What kind of error were you getting in RemoteTerm? And was anything showing up in the MeshMonitor logs while it was trying to connect?

[Yeraze]

and what do you see in the MeshMonitor logs during this?

[antonov124]

Sorry for the question where can i find it ? Then i can Look Into

[Yeraze]

What version of MeshMonitor are you using?

If it's docker, then you should be able to do something like docker logs meshmonitor .

[antonov124]

No its a normal Install in a proxmox CT

[Yeraze]

Ah, I'm not familiar with proxmox so I can't really help you there. You say "normal install", so you may be able to get logs via journalctl -u meshmonitor

[antonov124]

journalctl -u meshmonitor -f
Jul 06 18:45:39 MeshMonitor npm[239]: [INFO] [FirmwareUpdateService] Fetched 20 firmware releases
Jul 06 18:45:45 MeshMonitor npm[239]: [INFO] [MeshCorePoller:299c4365-ef82-4adb-b456-7804ab81be0d] get_stats(core) reported batteryMv=0 — not persisting (need a value > 0). Low-battery notifications for this companion will never fire until a positive voltage reading is observed.
Jul 06 18:46:11 MeshMonitor npm[239]: [ERROR] Failed to connect to Meshtastic node: Error: Connection timeout
Jul 06 18:46:11 MeshMonitor npm[239]: at Timeout._onTimeout (file:///opt/meshmonitor/dist/server/tcpTransport.js:186:28)
Jul 06 18:46:11 MeshMonitor npm[239]: at listOnTimeout (node:internal/timers:585:17)
Jul 06 18:46:11 MeshMonitor npm[239]: at process.processTimers (node:internal/timers:521:7)
Jul 06 18:46:11 MeshMonitor npm[239]: [ERROR] Failed to connect to Meshtastic node on startup: Error: Connection timeout
Jul 06 18:46:11 MeshMonitor npm[239]: at Timeout._onTimeout (file:///opt/meshmonitor/dist/server/tcpTransport.js:186:28)
Jul 06 18:46:11 MeshMonitor npm[239]: at listOnTimeout (node:internal/timers:585:17)
Jul 06 18:46:11 MeshMonitor npm[239]: at process.processTimers (node:internal/timers:521:7)
Jul 06 18:47:51 MeshMonitor npm[239]: [INFO] 📱 [MeshCore VN 299c4365-ef82-4adb-b456-7804ab81be0d] client disconnected: mcvn-1 (0 remaining)
Jul 06 18:47:53 MeshMonitor npm[239]: [INFO] 📱 [MeshCore VN 299c4365-ef82-4adb-b456-7804ab81be0d] client connected: mcvn-2 (1 total)
Jul 06 18:47:53 MeshMonitor npm[239]: [INFO] [MeshCore VN 299c4365-ef82-4adb-b456-7804ab81be0d] AppStart from mcvn-2 (app "mccli") → SelfInfo for "POTA Guy Term"
Jul 06 18:48:11 MeshMonitor npm[239]: [ERROR] Reconnection failed: Connection timeout
Jul 06 18:48:16 MeshMonitor npm[239]: [INFO] [MeshCore] Advert sent (Companion)
Jul 06 18:48:19 MeshMonitor npm[239]: [INFO] [MeshCore:299c4365-ef82-4adb-b456-7804ab81be0d] Auto-pathfinding: running on 77 companions + 1 repeaters
Jul 06 18:48:19 MeshMonitor npm[239]: [INFO] [MeshCore] Path discovery sent for 401af27ebf3817cb…
Jul 06 18:48:33 MeshMonitor npm[239]: [INFO] [MeshCore] Advert sent (Companion)

You can see that i disconnect the RemoteTermClient and reconnect it

after the i make a advert to check if the advert is also showing in remote term. but it isnt.
(

any ideas? if i directly connect the remote Term to the companion everything is fine. but via virtual node ;(

hope this helps

[antonov124]

so here is a fresh log:

root@MeshMonitor:~# journalctl -u meshmonitor -f
Jul 06 19:21:30 MeshMonitor npm[352]: [INFO] [MeshCorePoller] Starting local-node telemetry poll every 300s
Jul 06 19:21:31 MeshMonitor npm[352]: [INFO] [MeshCoreRemoteTelem] Scheduler starting (tick=30s, min-interval=60s)
Jul 06 19:21:33 MeshMonitor npm[352]: [INFO] [RoomSyncScheduler] Starting (tick=60000ms)
Jul 06 19:21:36 MeshMonitor npm[352]: [INFO] [WebSocket] Client disconnected: XKQ3Np9nUjKcR4maAAAB (reason: client namespace disconnect)
Jul 06 19:21:36 MeshMonitor npm[352]: [INFO] [WebSocket] Client connected: FTlit_NclihnuQl9AAAD (user: admin)
Jul 06 19:21:39 MeshMonitor npm[352]: [INFO] [WebSocket] Client disconnected: FTlit_NclihnuQl9AAAD (reason: client namespace disconnect)
Jul 06 19:21:39 MeshMonitor npm[352]: [INFO] [WebSocket] Client connected: VOWm_cSfAF-nc3jIAAAF (user: admin)
Jul 06 19:21:50 MeshMonitor npm[352]: [INFO] [MeshCore] Logged into node 2160ed33...
Jul 06 19:21:53 MeshMonitor npm[352]: [INFO] [FirmwareUpdateService] Fetched 20 firmware releases
Jul 06 19:22:00 MeshMonitor npm[352]: [INFO] [MeshCorePoller:299c4365-ef82-4adb-b456-7804ab81be0d] get_stats(core) reported batteryMv=0 — not persisting (need a value > 0). Low-battery notifications for this companion will never fire until a positive voltage reading is observed.
Jul 06 19:22:09 MeshMonitor npm[352]: [INFO] [MeshCore:299c4365-ef82-4adb-b456-7804ab81be0d] Auto-pathfinding: running on 77 companions + 1 repeaters
Jul 06 19:22:09 MeshMonitor npm[352]: [INFO] [MeshCore] Path discovery sent for 401af27ebf3817cb…
Jul 06 19:22:25 MeshMonitor npm[352]: [ERROR] Failed to connect to Meshtastic node: Error: Connection timeout
Jul 06 19:22:25 MeshMonitor npm[352]: at Timeout._onTimeout (file:///opt/meshmonitor/dist/server/tcpTransport.js:186:28)
Jul 06 19:22:25 MeshMonitor npm[352]: at listOnTimeout (node:internal/timers:585:17)
Jul 06 19:22:25 MeshMonitor npm[352]: at process.processTimers (node:internal/timers:521:7)
Jul 06 19:22:25 MeshMonitor npm[352]: [ERROR] Failed to connect to Meshtastic node on startup: Error: Connection timeout
Jul 06 19:22:25 MeshMonitor npm[352]: at Timeout._onTimeout (file:///opt/meshmonitor/dist/server/tcpTransport.js:186:28)
Jul 06 19:22:25 MeshMonitor npm[352]: at listOnTimeout (node:internal/timers:585:17)
Jul 06 19:22:25 MeshMonitor npm[352]: at process.processTimers (node:internal/timers:521:7)
Jul 06 19:22:30 MeshMonitor npm[352]: [INFO] [MeshCore] contact_added for e31b137c15702536c478ffde33fce79ac1f99b4d6d335c7955a973fdaa3cc4b9 (WarpBeacon)
Jul 06 19:22:30 MeshMonitor npm[352]: [INFO] 📢 Broadcasting notifyOnNewNode notification to 0 subscriptions
Jul 06 19:22:30 MeshMonitor npm[352]: [INFO] 📢 Broadcasting notifyOnNewNode notification to 0 Apprise users
Jul 06 19:22:30 MeshMonitor npm[352]: [INFO] 📢 notifyOnNewNode broadcast complete: 0 sent, 0 failed, 0 filtered
Jul 06 19:22:30 MeshMonitor npm[352]: [INFO] 📢 notifyOnNewNode Apprise broadcast complete: 0 sent, 0 failed, 0 filtered
Jul 06 19:22:30 MeshMonitor npm[352]: [INFO] 📤 Sent new MeshCore node notification for WarpBeacon [e31b137c15702536…] on 299c4365-ef82-4adb-b456-7804ab81be0d
Jul 06 19:22:31 MeshMonitor npm[352]: [INFO] [MeshCoreRemoteTelem:299c4365-ef82-4adb-b456-7804ab81be0d] No telemetry from 2160ed33c8903b77… (status empty/timeout)
Jul 06 19:22:47 MeshMonitor npm[352]: [INFO] 📱 [MeshCore VN 299c4365-ef82-4adb-b456-7804ab81be0d] client disconnected: mcvn-1 (0 remaining)
Jul 06 19:22:49 MeshMonitor npm[352]: [INFO] 📱 [MeshCore VN 299c4365-ef82-4adb-b456-7804ab81be0d] client connected: mcvn-2 (1 total)
Jul 06 19:22:49 MeshMonitor npm[352]: [INFO] [MeshCore VN 299c4365-ef82-4adb-b456-7804ab81be0d] AppStart from mcvn-2 (app "mccli") → SelfInfo for "POTA Guy Term"
Jul 06 19:23:36 MeshMonitor npm[352]: [INFO] [MeshCore] contact_added for eb98b4b884269c03a6eee9d77df18b395410b649f4aae873f15c051b06a06d45 (Taucha🚂Bhf)
Jul 06 19:23:36 MeshMonitor npm[352]: [INFO] 📢 Broadcasting notifyOnNewNode notification to 0 subscriptions
Jul 06 19:23:36 MeshMonitor npm[352]: [INFO] 📢 Broadcasting notifyOnNewNode notification to 0 Apprise users
Jul 06 19:23:36 MeshMonitor npm[352]: [INFO] 📢 notifyOnNewNode broadcast complete: 0 sent, 0 failed, 0 filtered
Jul 06 19:23:36 MeshMonitor npm[352]: [INFO] 📢 notifyOnNewNode Apprise broadcast complete: 0 sent, 0 failed, 0 filtered
Jul 06 19:23:36 MeshMonitor npm[352]: [INFO] 📤 Sent new MeshCore node notification for Taucha🚂Bhf [eb98b4b884269c03…] on 299c4365-ef82-4adb-b456-7804ab81be0d
Jul 06 19:23:44 MeshMonitor npm[352]: [INFO] [MeshCore] contact_advertised for 7ed5a6db4608a7fa268e37782aba294b800614ab383c864b5f711a2f848514ea ()

Jul 06 19:23:44 i made a advert with another companion, MEshmonitor shows it, but Remote Term shows nothing
at 19:22.47 i disconnect remoteterm and reconnect it, witout any result
settings are
companion 192.168.6.73:5000 is finde
virtual node port 4406 with admin comands

Am I overlooking something?

whats this here?
Jul 06 19:22:25 MeshMonitor npm[352]: [ERROR] Failed to connect to Meshtastic node: Error: Connection timeout
Jul 06 19:22:25 MeshMonitor npm[352]: at Timeout._onTimeout (file:///opt/meshmonitor/dist/server/tcpTransport.js:186:28)
Jul 06 19:22:25 MeshMonitor npm[352]: at listOnTimeout (node:internal/timers:585:17)
Jul 06 19:22:25 MeshMonitor npm[352]: at process.processTimers (node:internal/timers:521:7)
Jul 06 19:22:25 MeshMonitor npm[352]: [ERROR] Failed to connect to Meshtastic node on startup: Error: Connection timeout
Jul 06 19:22:25 MeshMonitor npm[352]: at Timeout._onTimeout (file:///opt/meshmonitor/dist/server/tcpTransport.js:186:28)

greetings

[antonov124]

When i send a DM to my Companion both applications showing the DM to me. Meshmonitor AND RemoteTerm. Hope this info helps also

[Yeraze]

Thanks for the detailed logs — that was enough to pin it down. 🙏

Root cause: MeshMonitor's MeshCore Virtual Node completes the companion handshake (which is why RemoteTerm shows "connected to Radio"), but it was only forwarding two push types to connected apps — incoming text messages and DM-delivery acks. It never forwarded the raw received-packet feed that a real MeshCore node emits for every OTA packet (PUSH_CODE_LOG_RX_DATA, 0x88). Remote-Terminal's channel finder is driven entirely by that raw feed, so it sat connected but silent — exactly matching what you saw (adverts sent, but nothing showing up client-side).

Fix: PR #3964 (issue #3963) bridges that raw feed through the Virtual Node as the 0x88 push, so tools like Remote-Terminal will now see the full packet flow. The wire format was verified against the MeshCore firmware, meshcore.js, and the Remote-Terminal source, and it's covered by tests — but I haven't been able to test it end-to-end against real hardware + Remote-Terminal myself.

Once it lands in a release, would you be able to give it a try and confirm the channel finder lights up for you? That real-world confirmation would be hugely helpful. I'll follow up here when it ships.

[antonov124]

Sounds good. Sure i can Test

[antonov124]

4.12.5 fixed the Problem Now its working. Thx @Yeraze !!!!

[antonov124]

New Issue with the virtual Node:
When i start a mqtt in remote term, it ends with this error: Community MQTT needs the radio's private key to authenticate, but it isn't available. Your radio firmware may not support key export (ENABLE_PRIVATE_KEY_EXPORT=1), or you're connecting through a proxy that doesn't forward the key-export command. the author of remote term, means i can be added in meshmonitor maybe?

[Yeraze]

What is "Community MQTT" ?

[antonov124]

Data Forwarding: Push raw/decoded packets and repeater telemetry to MQTT brokers, Home Assistant, or mapping projects like LetsMesh and MeshRank. https://github.com/jkingsman/Remote-Terminal-for-MeshCore/issues/321 here my comment