mirror of
https://github.com/pe1hvh/meshcore-gui.git
synced 2026-10-31 01:42:04 +01:00
WHAT Add MSG_POLL_INTERVAL (config.py, default 30s) and SerialWorker._poll_pending_messages(), which drains the device message queue via get_msg() until NO_MORE_MSGS, independently of the messages_waiting event. WHY meshcore 2.3.9.1 fetches messages only in response to messages_waiting. When that event is missed the radio ACKs the packet but no message event ever reaches the application, so the message is neither archived nor displayed. Node resets do not help: the trigger goes missing, not the queue. NOTES start_auto_message_fetching() stays active; the poll only picks up what the event path leaves behind. Fetched messages dispatch as ordinary message events, so dedup and archiving are unchanged. Room Server history timestamps remain a separate open issue.