Jakub 6249e63ec0 fix: remove isBLEConnected guard from discover response handling ...

The !isBLEConnected() check was too restrictive — if BLE happened to be
connected (app in background) the standalone discover would silently drop
all responses. Tag matching already provides correct isolation: responses
matching _pending_node_discover_tag are handled by the standalone UI and
not forwarded to the BLE app; responses with a different tag fall through
to the normal forward path.

Also show short type names (Rpt/Snsr/Room) in the discover results list
instead of generic "known"/"NEW", with a '*' prefix for nodes not yet
in contacts — matching the repeater/sensor distinction the app shows.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-05-21 08:37:17 +02:00

..

companion_radio

fix: remove isBLEConnected guard from discover response handling

2026-05-21 08:37:17 +02:00

kiss_modem

simplify kiss noise floor sampling

2026-02-07 07:42:52 -08:00

simple_repeater

* version 1.15.0

2026-04-19 11:27:55 +10:00

simple_room_server

* version 1.15.0

2026-04-19 11:27:55 +10:00

simple_secure_chat

Merge pull request #1297 from ViezeVingertjes/feature/duty-cycle-token-bucket

2026-03-08 23:54:32 +11:00

simple_sensor

Merge branch 'default-scope' into dev

2026-04-17 16:30:19 +10:00