Skip to content

Explain why a repeater may not answer a scope request #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MrAlders0n merged 1 commit into from
Sep 27, 2026
Merged

Explain why a repeater may not answer a scope request #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion docs/app_settings_reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,7 +178,7 @@ Defers auto pings in squares that already have recent coverage, so your airtime

#### Scope Discovery

Asks repeaters which channels or contacts they pass as you discover them, to help build a network topology map.
After each discovery, asks the repeaters it found which scopes they carry (the named regions that decide which flood traffic a repeater forwards), so the map can show which repeater carries which scope. Up to 3 of the strongest repeaters are asked, one at a time, and each request is a short direct message to a repeater in range. Pings keep their normal schedule. Every request shows in the log tab under **SCP**.

- **Disabled by default**
- Tap the **(i)** beside the switch for details inside the app
Expand All @@ -187,6 +187,14 @@ Asks repeaters which channels or contacts they pass as you discover them, to hel
- Requires companion firmware **1.16.0 or newer**
- Cannot be changed during auto-ping

**Why a repeater may not answer.** "No response from repeater" in the log is normal and does not mean the repeater is broken or out of date:

- **Each repeater answers at most 4 anonymous requests every 3 minutes.** That limit is built into the repeater firmware and is shared by everyone asking it anything anonymously (scope, owner and clock requests, from any app). Once it is used up, the repeater stays silent until the 3 minutes pass. Busy repeaters on high sites, heard by many radios, reach this limit most often.
- **The answer can be lost on the way back.** An answer is longer than a discovery reply, so a repeater at the edge of range, or on a busy channel, can answer discovery and still miss this one.
- **Older repeater firmware ignores the request.** Repeaters need firmware **1.12.0 or newer** to answer.

A repeater that does not answer is not marked as checked, so the app asks it again on a later discovery. Nothing is uploaded for a request that goes unanswered.

#### Auto-Stop After Idle

- Automatically stops auto-ping after **30 minutes without GPS movement**
Expand Down
Loading