Time change on app and repeater without being prrompted #245

New Issue

2026-10-27T15:45:37+01:00

adam commented

2026-10-27 15:45:37 +01:00

Describe the bug
Yesterday i was using the t deck and after setting the date and time in the morning i found that the t decks time and date had reset to the default of may 24 and a spurious time! also during the session i logged into the repeater to find even though i had not logged into the clock section of the repeaters back end that too reset to a default time and date. so had to reset by logging in vvia the ios app and setting the time and date from the iphone app.

Whilst its not life or death its becoming problematicc using mcterm which i have advocated for when people have asked for a good tdeck client but now feel im going to stop using it until some of the many bugs have been sorted.

Which device are you using
LilyGO T-Deck Plus

Which Firmware are you using
0.9.12

To Reproduce
Steps to reproduce the behavior:
These behaviours seem very spurious

Additional context

no point having to keep logging into my repeater to change back what mccterm has changed so will put it on the sideline for now. i have a mesh os licence but loathe the thought of using the app.

i will keep my eyes on this github to see where we are in a few days wont be using mcterm until i see another update

**Describe the bug** Yesterday i was using the t deck and after setting the date and time in the morning i found that the t decks time and date had reset to the default of may 24 and a spurious time! also during the session i logged into the repeater to find even though i had not logged into the clock section of the repeaters back end that too reset to a default time and date. so had to reset by logging in vvia the ios app and setting the time and date from the iphone app. Whilst its not life or death its becoming problematicc using mcterm which i have advocated for when people have asked for a good tdeck client but now feel im going to stop using it until some of the many bugs have been sorted. **Which device are you using** LilyGO T-Deck Plus **Which Firmware are you using** 0.9.12 **To Reproduce** Steps to reproduce the behavior: These behaviours seem very spurious **Additional context** no point having to keep logging into my repeater to change back what mccterm has changed so will put it on the sideline for now. i have a mesh os licence but loathe the thought of using the app. i will keep my eyes on this github to see where we are in a few days wont be using mcterm until i see another update

adam closed this issue

2026-10-27 15:45:37 +01:00

adam commented

2026-10-27 15:45:38 +01:00

Could it be that this is a duplicate of #213, and you received a packet from another node with the wrong timestamp and MC Term just updated it's clock to the time of the received message?

Could it be that this is a duplicate of #213, and you received a packet from another node with the wrong timestamp and MC Term just updated it's clock to the time of the received message?

adam commented

2026-10-27 15:45:39 +01:00

Could it be that this is a duplicate of #213, and you received a packet from another node with the wrong timestamp and MC Term just updated it's clock to the time of the received message?

no as its nothing to do with outside influence ! you state its to do with a time stamp and messages my bug has nothing to do with messages or time stamps on messages!

This happened whilst i wasnt near the tdeck whilst switched on! And there is now so many bugs and issues reported there is no way im going to search through the numerous conetations of each bug i will leave that to admin!

hopefully we can clear up some of the numerous bugs until then its on the back burner for me!

> Could it be that this is a duplicate of [#213](https://github.com/dabeani/meshcoreterm/issues/213), and you received a packet from another node with the wrong timestamp and MC Term just updated it's clock to the time of the received message? no as its nothing to do with outside influence ! you state its to do with a time stamp and messages my bug has nothing to do with messages or time stamps on messages! This happened whilst i wasnt near the tdeck whilst switched on! And there is now so many bugs and issues reported there is no way im going to search through the numerous conetations of each bug i will leave that to admin! hopefully we can clear up some of the numerous bugs until then its on the back burner for me!

adam commented

2026-10-27 15:45:39 +01:00

On Sun, 03 May 2026 08:36:36 -0700, BUDDHADECK2
@.***> wrote:

BUDDHADECK2 left a comment (dabeani/meshcoreterm#245)

Could it be that this is a duplicate of
#213, and you
received a packet from another node with the wrong timestamp and MC
Term just updated it's clock to the time of the received message?

no as its nothing to do with outside influence ! you state its to do
with a time stamp and messages my bug has nothing to do with messages
or time stamps on messages!

This happened whilst i wasnt near the tdeck whilst switched on!

So you are sure that you did not receive any message?

On Sun, 03 May 2026 08:36:36 -0700, BUDDHADECK2 ***@***.***> wrote: > BUDDHADECK2 left a comment (dabeani/meshcoreterm#245) > > > Could it be that this is a duplicate of > > [#213](https://github.com/dabeani/meshcoreterm/issues/213), and you > > received a packet from another node with the wrong timestamp and MC > > Term just updated it's clock to the time of the received message? > > no as its nothing to do with outside influence ! you state its to do > with a time stamp and messages my bug has nothing to do with messages > or time stamps on messages! > > This happened whilst i wasnt near the tdeck whilst switched on! So you are sure that you did not receive any message?

adam commented

2026-10-27 15:45:40 +01:00

On Sun, 03 May 2026 08:36:36 -0700, @BUDDHADECK2 wrote:

And there is now so many bugs and issues reported there is no way im
going to search through the numerous conetations of each bug i will
leave that to admin!

I didn't wanted to blame you in any way, I just wanted to point to
something which might be helpful additional information.

I do not see that you are oblidged to understand the existing issues
before you report a new one. (When I do, I sometimes use the search
function in the issue tracker if something pops up, but not reading all
issues. Since most of current reports are by myself, I remember quite a
lot of issues.)

On Sun, 03 May 2026 08:36:36 -0700, @BUDDHADECK2 wrote: > And there is now so many bugs and issues reported there is no way im > going to search through the numerous conetations of each bug i will > leave that to admin! I didn't wanted to blame you in any way, I just wanted to point to something which _might_ be helpful additional information. I do not see that you are oblidged to understand the existing issues before you report a new one. (When I do, I sometimes use the search function in the issue tracker if something pops up, but not reading all issues. Since most of current reports are by myself, I remember quite a lot of issues.)

adam commented

2026-10-27 15:45:41 +01:00

On Sun, 03 May 2026 08:36:36 -0700, @BUDDHADECK2 wrote:
And there is now so many bugs and issues reported there is no way im
going to search through the numerous conetations of each bug i will
leave that to admin!
I didn't wanted to blame you in any way, I just wanted to point to
something which might be helpful additional information.

I do not see that you are oblidged to understand the existing issues
before you report a new one. (When I do, I sometimes use the search
function in the issue tracker if something pops up, but not reading all
issues. Since most of current reports are by myself, I remember quite a
lot of issues.)

You seem to enjoy highlighting what you think is and isnt relevant as to what is reported! i report what i see and hope that bernhard the dev can see it was sent in good faith ! you can feel free to request the removal of anything i highlight as a bug. The frustration has now over taken the pleasure of using mc term. so for a while or until bernhard works through the dozens of bugs you seem to highlight im going back to ripple.

> On Sun, 03 May 2026 08:36:36 -0700, [@BUDDHADECK2](https://github.com/BUDDHADECK2) wrote: > And there is now so many bugs and issues reported there is no way im > going to search through the numerous conetations of each bug i will > leave that to admin! > I didn't wanted to blame you in any way, I just wanted to point to > something which _might_ be helpful additional information. > > I do not see that you are oblidged to understand the existing issues > before you report a new one. (When I do, I sometimes use the search > function in the issue tracker if something pops up, but not reading all > issues. Since most of current reports are by myself, I remember quite a > lot of issues.) You seem to enjoy highlighting what you think is and isnt relevant as to what is reported! i report what i see and hope that bernhard the dev can see it was sent in good faith ! you can feel free to request the removal of anything i highlight as a bug. The frustration has now over taken the pleasure of using mc term. so for a while or until bernhard works through the dozens of bugs you seem to highlight im going back to ripple.

adam commented

2026-10-27 15:45:41 +01:00

hey guys,
first of all, thank all of you to be part of it and help me with figuring out whats (not?) working anymore. Since the firmware is getting bigger, its quite a lot of work to keep it in the correct path. As you could see, the last update was not the best, sorry for that - nevertheless, i try my best to bring the v0.9.12.1 with a lot of bugfixes!

Such bugs as you mentioned here, and in the other Reports are nearly fixed. There are small issues which i want to fix before i will push another update. I fixed a long runner for Sensecap Indicator to make it useable again - so happy that i found a way to bring back this device on the list with all the (fixed :)) features.

Give me some more days, cant work all day for MC Term but, at least i try my best.
Felt like i need to give you a short update and keep you informed, even when its a lot of bug reports - it will help to bring MC Term back on the correct path again!

Thank you very much!
Bernhard

hey guys, first of all, thank all of you to be part of it and help me with figuring out whats (not?) working anymore. Since the firmware is getting bigger, its quite a lot of work to keep it in the correct path. As you could see, the last update was not the best, sorry for that - nevertheless, i try my best to bring the v0.9.12.1 with a lot of bugfixes! Such bugs as you mentioned here, and in the other Reports are nearly fixed. There are small issues which i want to fix before i will push another update. I fixed a long runner for Sensecap Indicator to make it useable again - so happy that i found a way to bring back this device on the list with all the (fixed :)) features. Give me some more days, cant work all day for MC Term but, at least i try my best. Felt like i need to give you a short update and keep you informed, even when its a lot of bug reports - it will help to bring MC Term back on the correct path again! Thank you very much! Bernhard

adam commented

2026-10-27 15:45:42 +01:00

hey guys,
first of all, thank all of you to be part of it and help me with figuring out whats (not?) working anymore. Since the firmware is getting bigger, its quite a lot of work to keep it in the correct path. As you could see, the last update was not the best, sorry for that - nevertheless, i try my best to bring the v0.9.12.1 with a lot of bugfixes!

Such bugs as you mentioned here, and in the other Reports are nearly fixed. There are small issues which i want to fix before i will push another update. I fixed a long runner for Sensecap Indicator to make it useable again - so happy that i found a way to bring back this device on the list with all the (fixed :)) features.

Give me some more days, cant work all day for MC Term but, at least i try my best.
Felt like i need to give you a short update and keep you informed, even when its a lot of bug reports - it will help to bring MC Term back on the correct path again!

Thank you very much!
Bernhard

What an absolute gentlemen ! Thanks for the update Bernhard and look forward to the much needed update

> hey guys, > first of all, thank all of you to be part of it and help me with figuring out whats (not?) working anymore. Since the firmware is getting bigger, its quite a lot of work to keep it in the correct path. As you could see, the last update was not the best, sorry for that - nevertheless, i try my best to bring the v0.9.12.1 with a lot of bugfixes! > > Such bugs as you mentioned here, and in the other Reports are nearly fixed. There are small issues which i want to fix before i will push another update. I fixed a long runner for Sensecap Indicator to make it useable again - so happy that i found a way to bring back this device on the list with all the (fixed :)) features. > > Give me some more days, cant work all day for MC Term but, at least i try my best. > Felt like i need to give you a short update and keep you informed, even when its a lot of bug reports - it will help to bring MC Term back on the correct path again! > > Thank you very much! > Bernhard What an absolute gentlemen ! Thanks for the update Bernhard and look forward to the much needed update

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshcore#245