adam/meshcore
1
0 Fork 0
mirror of https://github.com/dabeani/meshcoreterm.git synced 2026-11-02 02:55:46 +01:00
Code Issues 97 Packages Projects Releases Wiki Activity

Clock jumps drastically when receiving a message from a room or a reply from repeater admin CLI. #203

New Issue
Closed
opened 2026-10-27 15:43:47 +01:00 by adam · 1 comment
adam commented 2026-10-27 15:43:47 +01:00
Owner
Copy link
Copy source

Describe the bug

When I login to repeater admin, open the CLI, issue a command to the repeater and receive an answer from the repeater,
OR
When I receive a message from a room server,
the clock of the device jumps to a complete different value.

Currently I had:

  • Date/time at 2026-04-21, 23:5x, TZ: "UTC-2" (which in fact is UTC+2).

  • Received a message from a room,

  • clock was at 08:xx.

  • Date/time at 2026-04-22, 00:04, TZ: "UTC-2" (which in fact is UTC+2).

  • Logged in to repeater Admin, opened CLI, typed region, received reply,

  • clock changed to 2024-05-16, 12:25, TZ: "UTC-2" (which in fact is UTC+2).

Which device are you using

LilyGO T-Deck Plus

Which Firmware are you using

v0.9.12

To Reproduce

  1. Log in to repeater admin
  2. Click on "CLI"
  3. Issue region
  4. receive a reply,
  5. see a drastic clock jump.

Additional context

This could be related to or have the same root cause as #141.

**Describe the bug** When I login to repeater admin, open the CLI, issue a command to the repeater and receive an answer from the repeater, OR When I receive a message from a room server, the clock of the device jumps to a complete different value. Currently I had: * Date/time at 2026-04-21, 23:5x, TZ: "UTC-2" (which in fact is UTC+2). * Received a message from a room, * clock was at 08:xx. * Date/time at 2026-04-22, 00:04, TZ: "UTC-2" (which in fact is UTC+2). * Logged in to repeater Admin, opened CLI, typed `region`, received reply, * clock changed to 2024-05-16, 12:25, TZ: "UTC-2" (which in fact is UTC+2). **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** v0.9.12 **To Reproduce** 1. Log in to repeater admin 2. Click on "CLI" 3. Issue `region` 4. receive a reply, 5. see a drastic clock jump. **Additional context** This could be related to or have the same root cause as #141. <!-- github-sync-id:4305560669 -->
adam closed this issue 2026-10-27 15:43:47 +01:00
adam commented 2026-10-27 15:43:48 +01:00
Author
Owner
Copy link
Copy source

Closing, since it is in fact #213: "Time is set to time of received message. Always, unconditionally, also when received message has wrong time.".

Closing, since it is in fact #213: "[Time is set to time of received message. Always, unconditionally, also when received message has wrong time.](https://github.com/dabeani/meshcoreterm/issues/213)". <!-- github-comment-id:4319244755 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/meshcore#203