RemoteTerm radio connected via TCP doesn't see confirmations #116

New Issue

2026-10-27T09:33:59+01:00

adam commented

2026-10-27 09:33:59 +01:00

Versions

Repeater: v1.1.2
Dev Build: 1
Core: v1.1.1

Hardware - PiMesh v2

Setup

Create companion bind address 0.0.0.0 port 5050
Link companion with RemoteTerm, verify connection established
Send message to private or public room. Verify via separate radio that message is sending successfully (heard directly, no repeater paths - concerning that repeater paths do not show)
Note that confirmation of message is not received in Remote Term, with default settings, message is sent twice via retry.

Expected Outcome

I expect to see confirmation of message sent via RemoteTerm and expect repeaters to repeat messages.

Actual Outcome

Messages do not appear to be accepted by repeaters, only heard direct. Do not see confirmation of messages received.

# Versions Repeater: v1.1.2 Dev Build: 1 Core: v1.1.1 Hardware - PiMesh v2 # Setup 1. Create companion bind address 0.0.0.0 port 5050 2. Link companion with RemoteTerm, verify connection established 3. Send message to private or public room. Verify via separate radio that message is sending successfully (heard directly, no repeater paths - concerning that repeater paths do not show) 4. Note that confirmation of message is not received in Remote Term, with default settings, message is sent twice via retry. # Expected Outcome I expect to see confirmation of message sent via RemoteTerm and expect repeaters to repeat messages. # Actual Outcome Messages do not appear to be accepted by repeaters, only heard direct. Do not see confirmation of messages received.

adam closed this issue

2026-10-27 09:34:00 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/pyMC_Repeater#116