adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-10-30 22:41:57 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

Integration MQTT is not connected #234

New Issue
Closed
opened 2026-10-05 02:05:12 +02:00 by adam · 8 comments
adam commented 2026-10-05 02:05:12 +02:00
Owner
Copy link
Copy source

ive tried Letsmesh and Meshrank
Meshrank i use my account details

but its not working it says "Disconnected"

The rest of Remoteterminal is working correct.
what can i do?

ive tried Letsmesh and Meshrank Meshrank i use my account details but its not working it says "Disconnected" The rest of Remoteterminal is working correct. what can i do? <!-- github-sync-id:4831189542 -->
adam closed this issue 2026-10-05 02:05:12 +02:00
adam commented 2026-10-05 02:05:13 +02:00
Author
Owner
Copy link
Copy source

Which integration exactly is this? Explicit letsmesh or manual community-mqtt extension? What configs are you using? Do you see any errors in the logs when you enable it? Is the module actually enabled (checkbox on the summary page)?

Which integration exactly is this? Explicit letsmesh or manual community-mqtt extension? What configs are you using? Do you see any errors in the logs when you enable it? Is the module actually enabled (checkbox on the summary page)? <!-- github-comment-id:4919175457 -->
adam commented 2026-10-05 02:05:13 +02:00
Author
Owner
Copy link
Copy source

booth letsmesh and meshrank

Image My config is: companion -> Meshmonitor -> Remoteterm ( all other things are working, but no "mqtt" ) i check when i connect remote term directly via companion mqtt works. so maybe an issue between meshmonitor and remote term need this mqtt any special data or other things so i can adress this to the developer of Meshmonitor?

FYI meshmonitor : https://github.com/Yeraze/meshmonitor/
greetings

booth letsmesh and meshrank <img width="471" height="336" alt="Image" src="https://github.com/user-attachments/assets/67493a92-f96d-4199-8c57-a3fea3677690" /> My config is: companion -> Meshmonitor -> Remoteterm ( all other things are working, but no "mqtt" ) i check when i connect remote term directly via companion mqtt works. so maybe an issue between meshmonitor and remote term need this mqtt any special data or other things so i can adress this to the developer of Meshmonitor? FYI meshmonitor : https://github.com/Yeraze/meshmonitor/ greetings <!-- github-comment-id:4923731562 -->
adam commented 2026-10-05 02:05:14 +02:00
Author
Owner
Copy link
Copy source

Right; I'm meaning what is the actual config you have set up if you click "Edit".

when i connect remote term directly via companion mqtt works

what do you mean by this? You mean remoteterm is connected to radio using meshmonitor as a proxy? But that the MQTT connections work when RemoteTerm is connected to the radio without Meshmonitor as a proxy? Generally I have a policy of not supporting proxies as they very rarely implement the fully correct radio spec; if remoteterm is not getting raw packets it cannot forward them via MQTT, but that shouldn't affect your ability to actually connect to your MQTT endpoint which is why I'm wondering if the settings are incorrect, but if it works when the radio is directly connected, that's a very odd issue.

Right; I'm meaning what is the actual config you have set up if you click "Edit". > when i connect remote term directly via companion mqtt works what do you mean by this? You mean remoteterm is connected to radio using meshmonitor as a proxy? But that the MQTT connections work when RemoteTerm is connected to the radio without Meshmonitor as a proxy? Generally I have a policy of not supporting proxies as they very rarely implement the fully correct radio spec; if remoteterm is not getting raw packets it cannot forward them via MQTT, but that shouldn't affect your ability to actually connect to your MQTT endpoint which is why I'm wondering if the settings are incorrect, but if it works when the radio is directly connected, that's a very odd issue. <!-- github-comment-id:4929379327 -->
adam commented 2026-10-05 02:05:15 +02:00
Author
Owner
Copy link
Copy source

Ah hah, I have a theory — we export the private key in order to sign our MQTT traffic. Does meshmonitor allow private key export? If not, that's certainly the issue.

Ah hah, I have a theory — we export the private key in order to sign our MQTT traffic. Does meshmonitor allow private key export? If not, that's certainly the issue. <!-- github-comment-id:4929463279 -->
adam commented 2026-10-05 02:05:15 +02:00
Author
Owner
Copy link
Copy source

I've added a clearer warning if the private key is the isue

I've added a clearer warning if the private key is the isue <!-- github-comment-id:4929765799 -->
adam commented 2026-10-05 02:05:16 +02:00
Author
Owner
Copy link
Copy source

Thx for the Info. At the Moment im Not at Home. I can Test this maybe next week and can give you the Infos you need

Thx for the Info. At the Moment im Not at Home. I can Test this maybe next week and can give you the Infos you need <!-- github-comment-id:4932415589 -->
adam commented 2026-10-05 02:05:17 +02:00
Author
Owner
Copy link
Copy source

I'm going to close this; if and when you have more info, feel free to reopen.

I'm going to close this; if and when you have more info, feel free to reopen. <!-- github-comment-id:5037047507 -->
adam commented 2026-10-05 02:05:18 +02:00
Author
Owner
Copy link
Copy source

Sorry im at vacation right now.

Sorry im at vacation right now. <!-- github-comment-id:5037076301 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#234