MQTT corruption? #186

Closed
opened 2026-10-05 02:02:28 +02:00 by adam · 3 comments
Owner

sometimes remoteterm receives packet and cannot decrypt it. but at the same time this packet is sent to mqtt causing some strange behavior.

Image

remoteterm-1 | 2026-05-12 15:11:13 - app.packet_processor - WARNING - Failed to parse 137-byte packet (id=1214846); stored undecrypted
remoteterm-1 | 2026-05-12 15:16:01 - app.packet_processor - WARNING - Failed to parse 146-byte packet (id=1215039); stored undecrypted
remoteterm-1 | 2026-05-12 15:22:49 - app.packet_processor - WARNING - Failed to parse 153-byte packet (id=1215453); stored undecrypted
remoteterm-1 | 2026-05-12 15:25:43 - app.packet_processor - WARNING - Failed to parse 93-byte packet (id=1215667); stored undecrypted

sometimes remoteterm receives packet and cannot decrypt it. but at the same time this packet is sent to mqtt causing some strange behavior. <img width="2780" height="1207" alt="Image" src="https://github.com/user-attachments/assets/1c0f5dfa-c029-4a14-9dcc-7de2107e20f9" /> remoteterm-1 | 2026-05-12 15:11:13 - app.packet_processor - WARNING - Failed to parse 137-byte packet (id=1214846); stored undecrypted remoteterm-1 | 2026-05-12 15:16:01 - app.packet_processor - WARNING - Failed to parse 146-byte packet (id=1215039); stored undecrypted remoteterm-1 | 2026-05-12 15:22:49 - app.packet_processor - WARNING - Failed to parse 153-byte packet (id=1215453); stored undecrypted remoteterm-1 | 2026-05-12 15:25:43 - app.packet_processor - WARNING - Failed to parse 93-byte packet (id=1215667); stored undecrypted <!-- github-sync-id:4430495323 -->
adam closed this issue 2026-10-05 02:02:28 +02:00
Author
Owner

i'm not sure what to do with this but probably you can check it's expected behavior or not

i'm not sure what to do with this but probably you can check it's expected behavior or not <!-- github-comment-id:4432226528 -->
Author
Owner

to spicy up this problem a bit — these kinds of packets only came from remoteterm, mqtt-enabled observers do not produce these

to spicy up this problem a bit — these kinds of packets only came from remoteterm, mqtt-enabled observers do not produce these <!-- github-comment-id:4444740870 -->
Author
Owner

Whoops yeah, we shouldn't be forwarding garbage.

Whoops yeah, we shouldn't be forwarding garbage. <!-- github-comment-id:4446068058 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#186