MarekWo b516d4e370 docs: clarify DM contact issue — device table vs DB mismatch ...

Root cause is device firmware contact table being empty (after reflash
or reset), not the v1→v2 migration itself. DB retains hundreds of
contacts from advert history but device only has those explicitly added.

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

2026-03-07 12:50:01 +01:00

..

architecture.md

docs: Update docs/architecture.md with Console feature

2026-01-09 21:51:26 +01:00

docker-install.md

docs: Reorganize and simplify documentation structure

2026-01-07 10:21:55 +01:00

meshcore-faq.md

refactor(dm): Show all contacts in DM dropdown selector

2025-12-28 15:15:50 +01:00

MIGRATION-v1-to-v2.md

docs: clarify DM contact issue — device table vs DB mismatch

2026-03-07 12:50:01 +01:00

rpt-mgmt.md

docs: Add Repeater management manual

2026-01-12 09:38:36 +01:00

troubleshooting.md

docs: Add troubleshooting section for unresponsive device (firmware corruption)

2026-02-09 10:33:32 +01:00

user-guide.md

feat: Add unknown delivery status indicator + update docs

2026-02-19 08:14:58 +01:00

watchdog.md

feat(watchdog): Hardware USB bus reset for stuck LoRa devices

2026-02-22 20:15:27 +00:00