Situation Map only show trusted, ignore configuration

[brothercorvo]

I am currently working on the Reticulum Telemetry Hub project
https://github.com/FreeTAKTeam/Reticulum-Telemetry-Hub, a situational awareness server for Sideband with TAK and meshtastic bridges.

I encountered the following issue in Sideband’s telemetry handling logic.
When in telemetry options “Only display trusted on map” is disabled, Sideband still fails to show untrusted peers’ telemetry markers on the map. The UI toggle moves correctly, but the map continues to filter out all untrusted telemetry.

The behavior seems to indicate that:

• the configuration value is not being applied to the map layer,
  -- the value may remain truthy internally, or
• the telemetry trust filter is desynchronized between UI and the display engine.

Source locations involved:

• Trust-filtering logic in map update loop at sbapp/main.py:6578
• UI toggle code writes to config at sbapp/ui/telemetry.py:82–85 and 260–283
• Even with telemetry_display_trusted_only = False, the map continues to drop untrusted markers.
• This is reproducible, and appears to be a genuine defect in the trust-filter handling.

To Reproduce

• Open Settings → Telemetry.
• Disable “Only display trusted on map”.
• configure a Telemetry collector & restart sideband
• Start Sideband with a Reticulum network containing both trusted and untrusted peers connected to the same collector
• Receive telemetry from telemetry collector with both trusted and untrusted peers (stream or beacon).
• go to to the Situation map view.
• below are the nodes in the collector

Result:

• Only trusted peers appear on the map; untrusted telemetry markers never show.

This occurs regardless of whether the collector mode is active.

Expected Behavior

• When “Only display trusted on map” is disabled:
• all telemetry sources (trusted + untrusted) should appear as markers on the map,
• telemetry filtering should rely solely on the toggle state,
• the map should re-render with untrusted markers visible immediately.

Logs & Screenshots

UI state showing the toggle disabled, but untrusted telemetry not displayed:

Code locations related to the bug:

• Trust-field read during map rendering:

• sbapp/main.py:6578

• UI toggle writes to configuration:

• sbapp/ui/telemetry.py:82–85, 260–283

Telemetry-related configuration from sideband_config decompiled:

{
  "enable_telemetry": true,
  "enable_telemetry_beacon": false,
  "enable_telemetry_beacon_throttling": true,
  "enable_telemetry_collector": false,
  "enable_telemetry_forward": false,
  "enable_telemetry_map": true,
  "enable_telemetry_stream": true,
  "enable_telemetry_system": true,
  "enable_telemetry_trust_filter": true
}

System Information

• OS: (tested with several Android and a Windows 11 sideband
• Program Version: Sideband release 1.8.0

Additional Context

This issue occurs consistently on both mobile and desktop builds.
Even when untrusted telemetry is confirmed in peer_telemetry() and visible in the DB, the map renderer does not display it unless the peer is in the trust list. The UI toggle does not override this as intended.
The problem likely involves the trust-filter boolean remaining truthy or a stale cached value being used during map redraw.

[markqvist]

Thanks for the detailed report @brothercorvo. This looks like a bug in the display or handling logic. Should have it fixed shortly.

[markqvist]

Hmm, I can't reproduce this. I just set up a new Sideband instance with a fresh identity, configured it to send to an existing telemetry collector, and sent some telemetry to it.

Downloading telemetry from another client that does not have this new destination marked as trusted displays it correctly on the map:

Are you sure you don't have the collector set to only receive from trusted?

Can you see all the expected telemetry on the collector node?

[markqvist]

Also, toggling "Only display trusted on map" on and off results in the expected behaviour, both for trusted and non-trusted nodes.

I did however find one logic inconsistency in the appearance (icon / color) updates when receiving bulk telemetry transfers, which I'm fixing now, but that should not at all affect whether objects are displayed or not.

[markqvist]

@brothercorvo, could you enable debug logging on the receiving clients where the non-trusted nodes don't appear. Then:

• Make sure to send a new piece of telemetry from the sending nodes, so we are sure the collector will send something new when the client requests a download
• Request a download on the client(s) where the nodes don't show up on the map
• Check the logs for any errors / warnings / strange stuff. Or just post the logs here or send them to me.

[brothercorvo]

I can reproduce the issue with the following configuration:
Node 1 is sideband on Android. Sent to the collector
Node 2 is sideband on Windows and does not know 1
Node 2 request telemetry from collector.
Nothing shows on the map
Node 2 manually creates the address of 1 and set to trusted
1 shows on the map
If I open the config of 2 display only trusted is true. Even when is set to false in the UI

[brothercorvo]

There is no error in the communication with the collector because in fact the telemetry has arrived