@claesg - brilliant that worked. Texting to all now and device says Mode 3. All devices now have a gps fix and seen stable too. Thanks a lot.
I have tried powering them on/off and they are getting a gps fix very quickly now. So 1.1.2 looks good.
1 Like
I unfortunately havenāt been able to get a gps lock on 1.1.2 so far - ran it overnight and restarted several times. It could be because my window has a screen, I havenāt been outside recently.
Edit: Also I noticed that the time shown in the list of nodes updates for offline nodes. I have 2 and the one I havenāt plugged in since yesterday is showing the current time in that list.
1 Like
Yes. I improved how nodes treat time. Now if a node hears a packet that contains the global time and it doesnāt yet have time from its local gps, it will assume that network time should be used for now.
Iām running firmware 1.1.2 and android app 1.1.02 and am also having issues waking up my tbeams and heltecs from sleep.
I find that once they go to sleep, I canāt seem to wake them from the android app by attempting to send a new message. I find I have to either reboot them or push the middle button on the tbeam to wake them up(top button on the heltec).
Iām not sure I understand - if my second node was offline, how would it have updated its time?
Edit: Also I noticed that the gps location got lost after a while, does it clear the location if itās old? It seems Iām unable to get a gps lock indoors so I have to repeatedly walk outside for a while to get it back.
Maybe the device has sent the nodeInfo (2nd offline device) from its memory, the app donāt know if it is old or new position because the time is wrong
See the wrong timestamp from my tbeam
2 Likes
My second offline node didnāt have a location, it only shows up in the node list and even though I donāt plug it in for days the time keeps updating. My first node which I leave online a lot is the one that sometimes has a location and sometimes doesnāt. It probably clears the location if it doesnāt get a new location after a while, thatās a separate issue. I just hate having to go outside all the time to get my location on the map.
The device has the nodeInfo of all devices kept in the memory and time is updated because it contains a position, i wanted to update only if the position is newer than the current one, but I canāt use the timestamp. It is a bug that needs to be fixed first on the device, or simply ignore position from nodeInfo
1 Like
Hopefully that will fix the issue. As it is right now, every node in my list has approximately the current time next to it regardless of whether that node has been offline or not. It would make more sense to me if the timestamp showed the last time that that node was seen, but itās not 100% clear what itās supposed to mean.
Oh thanks. Iāll look at this today. Iāve been meaning to f get to it.
1 Like
@geeksville I tried my tbeams again today and I have seen the same behaviour as yesterday - they get a gps fix, then within minutes lose the fix and then regain it. I am not moving them. Finally they all seem to get a stable fix.
1 Like
Tbeam here, same issue I see with firmware 1.1.1. This way the battery usage is great thouā¦Looks like I can run close to 5 days on 3300mha. The communication between the nodes is still active (running a 1.0.0 board at the other end and see its online and talking) but looks like bluetooth stays off.
Just tested, mine also disconnects when running from usb power.
Will update to 1.1.2 tomorrow and see if any change.
Thing is in disconnect state I can not enter messages, otherwise Iām not unhappy with the extreme low battery use.
I finally found some time to flash my device with the latest 1.1.2. Everything seems fine and feels very quick.
One issue which i think wasnāt already mentioned here is, that my tbeam sx1262 neo8 both say NoGPS on the screen, instead of no sats. when the get a GPS fix, everything is correct.
ooh thanks - will fix the no sats thing!
1 Like
Hmm - that problem sounds very interesting. Would you mind helping debug it in this bug? (ie capturing some info)
@feh123 never mind - I figured it out. Fix coming in 1.1.3 
Thanks for the report - it helped a lot!
2 Likes
Iāve been having troubles waking sleeping tbeams 1.1.2 through the app as well.
How is waking the tbeam supposed to work? Last I checked when I tried to send a message, the tbeam didnāt do anything until I woke it by pressing the middle button.
re: ble sleep behavior on esp32s
every few minutes (2 - 5? I donāt remember - but it defaults to that) the esp32 wakes and checks with the phone to see if it has anything to send, if it does it then sends it. It does this āsleep wakeā pattern because it saves lots of power.
Ok. It sounds like this is an intentional change in behaviour then. I think it might be good to indicate somehow that messages are queued in the Android app. Iād prefer if the timeout was a user visible radio setting. Also be nice if there was a way for the app to display the expected number of minutes/seconds until the queue is flushed.