[Bug]: Rak WisMesh Tag time set to 21 May 2019

[pelgraine]

Category

Other

Hardware

Other

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

• Meshtastic UI aka MUI colorTFT
• InkHUD ePaper
• OLED slide UI on any display

Firmware Version

2.7.5.ddd1499; 2.7.4c1f4f70; 2.7.3.cf574c7

Description

All new nodes seen in the Rak Wishmesh Tag node list display with the time of 21 May 2019, and also displays node first/last seen as six years ago.

This time error also seems to be the cause of the Position Exchange Failed error that occurs when trying the Exchange Positions function in IOS, even with GPS enabled on the Tag and iPS Location Permissions set correctly.

I have reflashed with firmware-rak4631-2.6.11.60ec05e in the meantime without issue, other than it being the wrong hardware.

Relevant log output

[pelgraine]

Just to add to it, the Tag would display the 2019 date before it had even found other nodes.

I have five other nodes on hand, including a Seeed T1000e and Heltec Meshpocket on 2.7.5 alpha firmware, that don't have this issue. Only seems to occur with the Tag.

[Xaositek]

so this is more of a GPS issue with the L76K giving us the wrong information; here is my "fix" that I have to do if you powered it up inside.

1. Set GPS to disabled either through the screen or an app (iOS or Android)
2. Reboot the device and verify it now gets the proper time
3. Wait about 20 minutes
4. Take the device outside and then enable GPS again
5. Verify the clock does not revert and year is now preserved

[pelgraine]

so this is more of a GPS issue with the L76K giving us the wrong information; here is my "fix" that I have to do if you powered it up inside.

1. Set GPS to disabled either through the screen or an app (iOS or Android)
2. Reboot the device and verify it now gets the proper time
3. Wait about 20 minutes
4. Take the device outside and then enable GPS again
5. Verify the clock does not revert and year is now preserved

You're amazing! Thank you so much! I was going a bit mad trying to figure out why this was happening and trying to fix it, hoping I wouldn't have to give up on GPS on the Tag. Your solution has solved my problem!

[fifieldt]

Going to reopen this to provide a slight fix, or at least a log line.