meshtastic / firmware

Meshtastic device firmware
https://meshtastic.org
GNU General Public License v3.0
3.58k stars 891 forks source link

[Bug]: Firmware Notification - Position can only be sent once every 5 seconds #4874

Closed akrabu closed 1 month ago

akrabu commented 1 month ago

Category

Other

Hardware

Rak4631, Seeed Card Tracker T1000-E

Firmware Version

2.5.2.771cb52

Description

I loaded 2.5.2 on my MuziWorks R1 (RAK4531) and Seeed T1000-E this morning. Took both to work today to see if the Seeed could replace my R1 as an EDC node. Both worked fine until an hour before I left for work. Suddenly I started getting a message about "position can only be sent once every 5 seconds" repeatedly, which was weird. I was using smart location, with stationary set to 3 hours, and on the move set to 15 minutes - minutes, not seconds.

It started hammering my notifications though, so I turned off smart position in case it was wonky GPS readings causing the issue. Even with it set to every hour and smart location off, I was still getting the message every 5 seconds so I powered off the node. Then I switched to my R1 (Wisblock), and it, too, was doing the exact same thing. I powered it off, and powered my Seeed node on again. It also seems to happen whether I use the internal GPS or the phone GPS with the Seeed node.

I checked the node metrics out of curiosity, and was shocked to see the battery was dead. Both nodes are Client Mute, and tuned mostly for battery life. But something had happened and the voltage very quickly dropped. Also, temperature readings seemed to start... going back in time, around the same time? Very odd output. See attached screenshots.

I tried doing the "wipe" firmware, and re-updating to 2.5.2 - it immediately started spamming me with notifications again. Going to downgrade to 2.5.0, though I know that's got issues with the T1000-E. We'll see. May have to go down to 2.4.3.

What I don't get is... how did I make it through most of the day without any issue at all? I wonder what triggered the sudden location spamming, huge power drain, and weird temp/time readings? I was up on Marquam Hill and couldn't reach my other node. There's no way it was picking up time from other nodes - because there really aren't any where I was haha

image0

IMG_4851

IMG_4852

IMG_4850

IMG_4854

Relevant log output

No response