Describe the bug
When a message is received, it sets the clock (date and time) to the timestamp of the received message.
This happens also when receiving a room server message or some reply from a repeater (admin login).
Clocks of nodes are sometimes, of room servers and repeaters often, wrong -- leading to a wrong clock setting on the device running MC Term!
Furthermore, in "Mgmt" -> "Date/Time", "NTP Status" stays showing "Synced" even if time has been changed by the mechanics described above, or manual. It should show "not synced" if the last NTP sync was changed by any other means.
Proposed solution
While setting the time and date from a received message is a nice feature, it should be optional and not mandatory.
There should be a new setting unter "Mgmt" -> "Date/Time" saying "sync time from received message", which can be set to "Enabled" or "Disabled".
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12
Regards!
Describe the bug
When a message is received, it sets the clock (date and time) to the timestamp of the received message.
This happens also when receiving a room server message or some reply from a repeater (admin login).
Clocks of nodes are sometimes, of room servers and repeaters often, wrong -- leading to a wrong clock setting on the device running MC Term!
Furthermore, in "Mgmt" -> "Date/Time", "NTP Status" stays showing "Synced" even if time has been changed by the mechanics described above, or manual. It should show "not synced" if the last NTP sync was changed by any other means.
Proposed solution
While setting the time and date from a received message is a nice feature, it should be optional and not mandatory.
There should be a new setting unter "Mgmt" -> "Date/Time" saying "sync time from received message", which can be set to "Enabled" or "Disabled".
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.12
Regards!