mirror of
https://github.com/dabeani/meshcoreterm.git
synced 2026-10-31 10:11:57 +01:00
When receiving message from room or reply from repeater CLI: Contacts list looses last heard timestamps, then they reappear and for some contacts they are wrong (but correctly sorted). #141
Reference in new issue
Block a user
OK, the issues get strange:
Describe the bug
The device's uptime is at 6 days already.
I had the "Contacts" list sorted by last heard.
I found a new room server there.
I tried to login, with password
hello(it did even advertise this in it's name).Login timed out (no ACK received), but it seemed to have worked since I got a red new message symbol.
Tried to login again with
hello, then empty password, thenhelloagain (all timed out).Went back to the contacts screen.
Issue I observed: Now all contacts I saw did not have a "last heard" relative timestamp anymore, except the room server I tried to login.
Photograph:
Shortly after another contact came up also with a recent relative timestamp ("now", i.e. 1 minute), so there were two contacts with timestamp again.
I did read the message, I did some other stuff, and at some point I came back to the contacts screen.
Then I observed:
Timestamps were back, but the two contacts which shortly before were the only contacts with relative timestamps now have a relative timestamp 14 days in the past. But they are nevertheless sorted at the top of the "last heard" list (almost at the top, there are two contacts before which actually really were the last ones heard by that time): The sorting seems to be correct, the displayed relative timestamps not.
Photograph:
Which device are you using
LilyGO T-Deck Plus
Which Firmware are you using
v0.9.10 (Update: Also in v0.9.11), detailed system information see photographs from the "Mgmt" → "Global" screen:
I see that the uptime is not much more than 6 days.
Regards!
OK, it does not seem to have to do with the uptime.
Just had ~3h uptime, and after logging in to a room (and also writing some stuff there), coming back to the contacts list, the "last heard" timestamps were gone.
Still present in firmware version 0.9.11.
And: Now I saw how the timestamps reappeared, and they reappered completely wrong (far too old; before they disapperead they were recent. In
Mgmt->Date/Timetime was correct.)This seems reproducible every time I log in or "log in" (= get a timeout, but still receive messages) to a room server and receive messages from that room. (Does not happen when there are no messages.)
Firmware version 0.9.11.
Also reproducible if I log in to a repeater as admin, go to the CLI, issue a command and receive a reply. If I do not receive a reply, the issue does not occur.
Firmware version 0.9.11.
will be fixed with #203!
Yes, it was related to clock set by received messages.
Seems fixed.