mirror of
https://github.com/dabeani/meshcoreterm.git
synced 2026-11-03 03:12:19 +01:00
Repeater clock resetting when logging in from tdeck #160
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/meshcore#160
Reference in new issue
Block a user
Describe the bug
Since the 1.14.1 update every time i try to view the clock on the repeater via the t deck the time resets back to a past time.
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
0.9.11
To Reproduce
log into repeater admin clock usually shows the date and time to be miles out,
Additional context
when the t deck changes the repeater time i have to use the meshcore app to reset the time back to current again.
i know my repeater had an update via the meshcore app in 14.1 and wonder if that could be a contributing factor to these weird behaviours.
After logging into the repeaters back end with the tdeck and mc term this is how it changes the time to the past viewing via the meshcore app
I then have to re sync the clock via the meshcore app as most times the time doesnt reshow in the admin pannel> clock button?
Will mc term be upgraded to 1.14.1 in the next update?
Oh. maybe that's why my repeater's clock is strangely off?
Anyway, all those differerent strange issues we see here, I am wondering if they are side-effect of LLM coding, and I am actually thinking of switching back to Ripple firmware for now :-( and coming back here in some month, only thing making me not doing this is that Ripple firmware supports only 11 characters in hastag channel names.
Really weird ! there are other underlying issues when connecting into the solar repeater after the last update varying from not being able to log in to the repeater 5 times tonight losing time when you log into the clock screen. Also ive noticed that the resend doesnt seem to work either, maybe thats down to the increase in traffic but over the last few weeks since the latest update on the router im seeing messages dropped not sent ? well see what is changed in the next update
you are right, this was a bug in the login of the repeater which caused the repeater (in some cases) to get a update with a wrong timestamp! i fixed this - i will test it a bit more to be sure that there is no other issue upcoming.
Sorry for that.
Fix v0.9.12
Thank you so much for your update. fingers crossed the bugs will get ironed out in the coming weeks
i am already working on updated since the last update. Nevertheless, i agree to user Dreirund to test more - but that consumes a lot of time - as you can "feel" now due to no updates in sort periods. I really want to take it seriously to bring you not too many bugs with new releases. Additionally i implemented a nice WebUI in WiFi mode (not mandatory to enable it) which is very nice :). Another stuff like NTP corrections, Save Messages to SDCard,... are already implemented and in testing :). As you can see, stuff will happen - thank you all for your support even when its bothering you sometimes.
appreciate your support!!
Thank you for the continued hard work you all put into the project mc term has a wonderful future with meshcore and the tdeck fror me especially! as an end user its always nice not only to be able to report back with potential issues (bugs) but promote the application as ive done since i swapped from mesh os. Whilst it can be challenging at times your passion and want to improve far outweighs the issues i have as an end user. keep up the great work and rest assured im on this journey with you guys