mirror of
https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git
synced 2026-11-03 08:02:19 +01:00
[BUG/SUPPORT] cannot login to my repeater #7
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/Remote-Terminal-for-MeshCore#7
Reference in new issue
Block a user
i am using RemoteTerminal as my major client. Unfortunately i need to unplug my client device to administer my nearby repeater.
if i want to login to the repeater via RemoteTerm i always get the error:
Command failed: Failed to add repeater contact: {'reason': 'no_event_received'}
even when logging into as guest. The distance between both devices antennas is about 2m plus a wall. So there should be no interference.
Any hints for digging into ?
Hmmm, interesting. "Failed to add contact" means that the app tried to add the repeater as a contact to the radio to address messages, and failed.
What's your device? Is it running a recent mainline firmware?
thats exactly what i want to find out without unplugging the repeater :-) i will check that.
Ah, and to be clear, your client radio, not the repeater. This is definitely an issue between RemoteTerm and the radio you're using via TemoteTerm; this is not an issue with your repeater or distance to repeater or password to the repeater.
Are you running off of docker or raw code? If raw code, I can push a quick fix attempt for you (if docker, it'll need to wait until tomorrow sorry). This isn't a good problem to plow past, but it might unblock comms.
I would also be interested to see the first dozen or so lines from the app after startup, about syncing/removing/adding contacts, if you have that handy. That may indicate if we've got a problem with radio comms or something else.
Okay, I've pushed up a commit (
65ecaa0f59) that should let the radio attempt to push past contact load failure. This MIGHT mean you still have the problem (if the contact is indeed failing to load) OR could mean that it fixes it (if the issue is in contact presence validation, and not actual loading).Feel free to pull latest main and see what that does (or wait for tomorrow night when I'm likely to cut a new Docker revision). I've got some massive overhaul for repeater operations coming out this weekend; hopefully we can fix your issue so you can enjoy them!
Sneak peek:
Hm, also, what do you mean by "I need to unplug my client device to administer my nearby repeater" -- you're not disconnecting the radio from your computer and then trying to continue using the app, right? That won't work.
Also, are you connecting via serial? Or BT/TCP?
both devices are heltec-v3
repeater FW is v1.12.0-e738a74 (Build: 29-Jan-2026)
client must be newer as i flashed it this weekend
Client runs on raw code after i encountered problems with my docker install (i am not the docker-guy ;-) )
Client is connected via serial into proxmox server. RemoteTerm runs in debian 13 VM.
Okay sick. Do a
git pulland see if the new commit solves your issue; if it doesn't, paste me the first startup log lines if you can please, and definitely any other errors you see during background operations. Thanks!login works, but no CLI commands...
Log
Feb 26 10:06:09 mesh systemd[1]: Stopped meshcore.service - Meshcore Uvicorn Service.
Feb 26 10:06:42 mesh systemd[1]: Started meshcore.service - Meshcore Uvicorn Service.
Feb 26 10:06:43 mesh uv[3022]: INFO:app.frontend_static:Serving frontend from /home/fds/Remote-Terminal-for-MeshCore/frontend/dist
Feb 26 10:06:43 mesh uv[3022]: INFO: Started server process [3022]
Feb 26 10:06:43 mesh uv[3022]: INFO: Waiting for application startup.
Feb 26 10:06:43 mesh uv[3022]: INFO:app.database:Connecting to database at data/meshcore.db
Feb 26 10:06:43 mesh uv[3022]: INFO:app.main:Database connected
Feb 26 10:06:43 mesh uv[3022]: INFO:meshcore:Serial Connection started
Feb 26 10:06:43 mesh uv[3022]: INFO:app.main:Connected to radio
Feb 26 10:06:43 mesh uv[3022]: INFO:app.event_handlers:Event handlers registered
Feb 26 10:06:43 mesh uv[3022]: INFO:app.keystore:Exporting private key from radio...
Feb 26 10:06:43 mesh uv[3022]: INFO:app.keystore:Private key stored in keystore (public key: 991318f9d8af...)
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio:Syncing and offloading radio data...
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio_sync:Starting full radio sync and offload
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio_sync:Found 1 contacts on radio
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio_sync:Synced 1 contacts, removed 1 from radio
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio_sync:Synced 1 channels, cleared 1 from radio
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio:Sync complete: {'contacts': {'synced': 1, 'removed': 1}, 'channels': {'synced': 1, 'cleared': 1}}
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio:Auto message fetching started
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio_sync:Started periodic radio sync (interval: 300s)
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio_sync:Started periodic advertisement task (interval configured in settings)
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio_sync:Started periodic message polling (interval: 10s)
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio:Post-connect setup complete
Feb 26 10:06:43 mesh uv[3022]: INFO:app.radio:Radio connection monitor started
Feb 26 10:06:43 mesh uv[3022]: INFO: Application startup complete.
Feb 26 10:06:43 mesh uv[3022]: INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43714 - "GET / HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43716 - "GET /assets/index-BH5l-dr5.css HTTP/1.1" 304 Not Modified
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43714 - "GET /assets/index-DSdWKiBO.js HTTP/1.1" 304 Not Modified
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43714 - "GET /api/radio/config HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43716 - "GET /api/settings HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43714 - "GET /api/packets/undecrypted/count HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43718 - "GET /api/channels HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43722 - "GET /api/contacts?limit=1000&offset=0 HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43756 - "GET /site.webmanifest HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43748 - "GET /api/read-state/unreads HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43762 - "WebSocket /api/ws" [accepted]
Feb 26 10:06:58 mesh uv[3022]: INFO:app.websocket:WebSocket client connected (1 total)
Feb 26 10:06:58 mesh uv[3022]: INFO: connection open
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43722 - "GET /favicon.ico HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43748 - "GET /api/messages?limit=200&type=CHAN&conversation_key=8B3387E9C5CDEA6AC9E5EDBAA115CD72 HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43718 - "POST /api/channels/8B3387E9C5CDEA6AC9E5EDBAA115CD72/mark-read HTTP/1.1" 200 OK
Feb 26 10:06:58 mesh uv[3022]: INFO: 192.168.2.105:43714 - "GET /api/read-state/unreads HTTP/1.1" 200 OK
Feb 26 10:07:29 mesh uv[3022]: INFO: 192.168.2.105:43734 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/mark-read HTTP/1.1" 200 OK
Feb 26 10:07:29 mesh uv[3022]: INFO: 192.168.2.105:54326 - "GET /api/messages?limit=200&type=PRIV&conversation_key=57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a HTTP/1.1" 200 OK
Feb 26 10:07:45 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio
Feb 26 10:07:45 mesh uv[3022]: INFO:app.routers.contacts:Sending login to repeater 57c141cfe5d3
Feb 26 10:07:47 mesh uv[3022]: INFO:app.routers.contacts:Requesting status from repeater 57c141cfe5d3
Feb 26 10:07:58 mesh uv[3022]: INFO:app.routers.contacts:Received telemetry from 57c141cfe5d3: {'pubkey_pre': '57c141cfe5d3', 'bat': 4034, 'tx_queue_len': 0, 'noise_floor': -105, 'last_rssi': -26, 'nb_recv': 132, 'nb_sent': 131, 'airtime': 75, 'uptime': 1915, 'sent_flood': 130, 'sent_direct': 1, 'recv_flood': 129, 'recv_direct': 3, 'full_evts': 0, 'last_snr': 12.25, 'direct_dups': 0, 'flood_dups': 0, 'rx_airtime': 73}
Feb 26 10:07:58 mesh uv[3022]: INFO:app.routers.contacts:Fetching neighbors from repeater 57c141cfe5d3
Feb 26 10:07:59 mesh uv[3022]: INFO:app.routers.contacts:Received 0 neighbors
Feb 26 10:07:59 mesh uv[3022]: INFO:app.routers.contacts:Fetching ACL from repeater 57c141cfe5d3
Feb 26 10:08:00 mesh uv[3022]: INFO:app.routers.contacts:Received 2 ACL entries
Feb 26 10:08:00 mesh uv[3022]: INFO:app.routers.contacts:Fetching clock from repeater 57c141cfe5d3
Feb 26 10:08:02 mesh uv[3022]: INFO:app.routers.contacts:Received clock output: 09:08 - 26/2/2026 UTC
Feb 26 10:08:02 mesh uv[3022]: INFO: 192.168.2.105:56632 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/telemetry HTTP/1.1" 200 OK
Feb 26 10:08:47 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio
Feb 26 10:08:47 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: ver
Feb 26 10:09:07 mesh uv[3022]: WARNING:app.routers.contacts:No CLI response from repeater 57c141cfe5d3 within 20.0s
Feb 26 10:09:07 mesh uv[3022]: WARNING:app.routers.contacts:No response from repeater 57c141cfe5d3 for command: ver
Feb 26 10:09:07 mesh uv[3022]: INFO: 192.168.2.105:47300 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 200 OK
Feb 26 10:11:43 mesh uv[3022]: INFO:app.radio_sync:Starting full radio sync and offload
Feb 26 10:11:43 mesh uv[3022]: INFO:app.radio_sync:Found 1 contacts on radio
Feb 26 10:11:48 mesh uv[3022]: WARNING:app.radio_sync:Failed to remove contact 57c141cfe5d3: {'reason': 'no_event_received'}
Feb 26 10:11:48 mesh uv[3022]: INFO:app.radio_sync:Synced 1 contacts, removed 0 from radio
Oh awesome, progress! If you can get any response of any kind from telemetry fetch, it means that all the core functionality is working. Causes of subsequent issues with the console are going to be due to interference from heavy traffic on the mesh that is obscuring your messages to the repeater or the repeater's responses, or just bad luck from something rlse. Try the command a few times; I not uncommonly have to submit a console command three or four times for it to go through, both on RemoteTerm and other clients.
The contact loading error happening at all is bizarre though. I'll dig a little more deeply tomorrow and see if I can spot any obvious probable issues.
remoteTerm output was like:
DO3FDS Repeater10:08
Telemetry
Battery Voltage: 4.034V
Uptime: 31m
Clock: 09:08 - 26/2/2026 UTC
TX Airtime: 1m
RX Airtime: 1m
Noise Floor: -105 dBm
Last RSSI: -26 dBm
Last SNR: 12.3 dB
Packets: 132 rx / 131 tx
Flood: 129 rx / 130 tx
Direct: 3 rx / 1 tx
Duplicates: 0 flood / 0 direct
TX Queue: 0
Debug Flags: 0
Neighbors
No neighbors reported10:08
ACL (2)
0defbc63edac: Admin
991318f9d8af: Admin10:08
DO3FDS Repeater10:09
(no response - command may have been processed)
Yeah, definitely good on the fundamentals. Just give it a few tries.
10 times tried. no success
first view tries were command "ver" then "region"
Log
Feb 26 10:21:02 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: region Feb 26 10:21:12 mesh uv[3022]: INFO: 192.168.2.105:58348 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 500 Internal Server Error Feb 26 10:21:24 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio Feb 26 10:21:29 mesh uv[3022]: WARNING:app.routers.contacts:Failed to add repeater 57c141cfe5d3 to radio: {'reason': 'no_event_received'} — continuing anyway Feb 26 10:21:29 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: region Feb 26 10:21:39 mesh uv[3022]: INFO: 192.168.2.105:44622 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 500 Internal Server Error Feb 26 10:21:40 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio Feb 26 10:21:45 mesh uv[3022]: WARNING:app.routers.contacts:Failed to add repeater 57c141cfe5d3 to radio: {'reason': 'no_event_received'} — continuing anyway Feb 26 10:21:45 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: region Feb 26 10:21:55 mesh uv[3022]: INFO: 192.168.2.105:44622 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 500 Internal Server Error Feb 26 10:22:11 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio Feb 26 10:22:16 mesh uv[3022]: WARNING:app.routers.contacts:Failed to add repeater 57c141cfe5d3 to radio: {'reason': 'no_event_received'} — continuing anyway Feb 26 10:22:16 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: region Feb 26 10:22:26 mesh uv[3022]: INFO: 192.168.2.105:57184 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 500 Internal Server Error Feb 26 10:22:27 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio Feb 26 10:22:32 mesh uv[3022]: WARNING:app.routers.contacts:Failed to add repeater 57c141cfe5d3 to radio: {'reason': 'no_event_received'} — continuing anyway Feb 26 10:22:32 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: region Feb 26 10:22:42 mesh uv[3022]: INFO: 192.168.2.105:57184 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 500 Internal Server Error Feb 26 10:22:44 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio Feb 26 10:22:49 mesh uv[3022]: WARNING:app.routers.contacts:Failed to add repeater 57c141cfe5d3 to radio: {'reason': 'no_event_received'} — continuing anyway Feb 26 10:22:49 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: region Feb 26 10:22:59 mesh uv[3022]: INFO: 192.168.2.105:57184 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 500 Internal Server Error Feb 26 10:23:08 mesh uv[3022]: INFO:app.routers.contacts:Adding repeater 57c141cfe5d3 to radio Feb 26 10:23:13 mesh uv[3022]: WARNING:app.routers.contacts:Failed to add repeater 57c141cfe5d3 to radio: {'reason': 'no_event_received'} — continuing anyway Feb 26 10:23:13 mesh uv[3022]: INFO:app.routers.contacts:Sending command to repeater 57c141cfe5d3: region Feb 26 10:23:23 mesh uv[3022]: INFO: 192.168.2.105:34366 - "POST /api/contacts/57c141cfe5d307703349258d2f490465429bc1db5dab8c56d0f6982d9a6bfe1a/command HTTP/1.1" 500 Internal Server Errorok, there seem to be something wrong in my client /remoteTerm config. cannot send anything anymore and cannot receive anything.
ok, after logging into the repeater it seems i get no more data from and to the device anymore. i restarted RemoteTerm and everything works well until i login to the repeater again.
Weird. things work fine and can you run commands using the official mobile client?
Wait, when you say
that your whole client radio stops working? even other things like sending/receiving messages in channels? That seems super weird, and makes me think of a radio issue (or I guess maybe a protocol issue with the library, but that would seem unlikely).
If the whole radio is locking up, I would start to suspect an issue with hardware or firmware. Seeing if you can run repeater commands with the official mobile app should be telling, but if that fails my next step would be to reflash your client (I assume you're on the mainline firmware/not running a custom build). If you CAN do all the operations, including CLI commands, from the official client, I agree that it points to an issue with my radio interface, but would be pretty uncertain about debugging that without access to the client.
I could maaaaayyybbeee see an issue with the repeater if it is somehow returning data that is so garbage it locks up the radio, but that seems highly, highly unlikely.
If you can get anything out of the repeater using RemoteTerm, as it appears you can, I would generally think more and more strongly that this is not a RemoteTerm issue, sorry 😕
i agree. i reflashed my client this morning, and rebooted the VM with remoteTerm. now i want to let it run for a couple of days without any fance repeater stuff.. ;-) i will just send periodically my weather information to my #wetter channel - lets see if that works. For now i will close this. maybe i add more if i can better find out whats going on. thanks a lot for your help ! i appreciate this and do not take this for granted.