Mirrors/MeshCore-Solo
1
0
Fork 0
mirror of https://github.com/MarekZegare4/MeshCore-Solo.git synced 2026-07-26 23:08:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: 52e65b960f

Browse Source
This commit is contained in:
MarekZegare4
2026-06-21 20:34:52 +00:00
parent 2a46b65f0d
commit ffef056825
4 changed files with 23 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
search/search_index.json
View File

File diff suppressed because one or more lines are too long

42
sitemap.xml
View File

@@ -2,86 +2,86 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://meshcore-dev.github.io/meshcore/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/cli_commands/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/companion_protocol/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/docs/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/faq/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/kiss_modem_protocol/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/nrf52_power_management/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/number_allocations/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/packet_format/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/payloads/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/qr_codes/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/stats_binary_frames/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/terminal_chat_cli/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/design/nearby_redesign/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/design/trail_redesign/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/solo_features/clock_screen/clock_screen/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/solo_features/favourites_dial/favourites_dial/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/solo_features/message_screen/message_screen/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/solo_features/screen_lock/screen_lock/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/solo_features/settings_screen/settings_screen/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
<url>
<loc>https://meshcore-dev.github.io/meshcore/solo_features/tools_screen/tools_screen/</loc>
<lastmod>2026-06-20</lastmod>
<lastmod>2026-06-21</lastmod>
</url>
</urlset>

BIN
sitemap.xml.gz
View File

Binary file not shown.

3
solo_features/tools_screen/tools_screen/index.html
View File

@@ -2378,8 +2378,7 @@ If the companion app is connected via <strong>BLE</strong>, the export is safe
<p>The five flood filters are <strong>opt-in</strong> (default OFF, so a plain repeater is unaffected) and act on <strong>flood</strong> traffic only — on a direct route this node is the named next hop, so it never drops those.</p>
<p><strong>Same network vs. separate network.</strong> With <strong>Network = Current</strong> (or a Custom profile set equal to your companion settings) the repeater stays on your own network — you keep messaging while relaying. With a <em>different</em> Custom profile the device moves entirely onto that network while relaying (a single radio can't be on two at once) and returns to your companion network when the repeater is switched off. The profile also re-applies after a reboot if the repeater was left on.</p>
<p>While the repeater is on, a <strong>»</strong> indicator appears in the status bar (same blink convention as the auto-advert and trail markers) so you can tell it's relaying at a glance. Two radio settings are also overridden while relaying and restored afterwards: <strong>Settings › Radio › Pwr save</strong> is forced off (a repeater must listen continuously) and <strong>Auto pwr</strong> is forced off (a repeater holds full TX power for consistent relay reach). Both show <code>--</code> in Settings while the repeater is on.</p>
<p>Live forwarding stats — <strong>Forwarded</strong>, <strong>Pool free</strong>, <strong>Queue</strong> — are shown on <strong>Tools › Diagnostics</strong>.</p>
<p>While the repeater is ON, the bottom of the screen shows live stats: <strong>Forwarded</strong> (packets actually re-transmitted — reflects Suppress dup), <strong>Pool free</strong>, and <strong>Queue</strong>. The same numbers appear, alongside the full device picture, in <strong>Tools › Diagnostics</strong>.</p>
<p>Live forwarding stats — <strong>Forwarded</strong>, <strong>Pool free</strong>, <strong>Queue</strong> — are shown on <strong>Tools › Diagnostics</strong> (this screen is config-only).</p>