Can you replicate this easily? The timestamp is added at the server end, which implies the data was buffered. What were the LEDs on the card doing at the time?
Hugo, I can’t get this to repeat but some observations
I was doing some wifi range testing seeing how imp fared though 2ft of Cornish Granite
Move imp out of wifi range (27+ ft from MIFI)
- server.log stops but imp Green LED still flashes
- IDE & Planner think imp is still connected
- after a period imp LED flashed Red
- imp LED extinguishes
Move imp in to wifi range
- after aprox 8 mins IDE & Planner agree imp is Offline
- after aprox 10 mins imp reconnects & server.log begins
Difference today is imp does a full restart but yesterday it didn’t!
Any chance of getting signal strength reading on the mobile App’s?
Dropped wifi will indicate offline on the device more quickly in the future; the work for the server to notice imps being offline is in progress now but won’t be instant (there’s no way to tell unless data flows).
The LED goes out after a minute of attempted connection to preserve battery. It sleeps for 9 minutes then tries for another minute, cycling until it gets reconnected. This 1/9 minute cycle is currently preset but will be settable from imp code.
Note also mifi’s are fairly weak as AP’s. you’ll get much better range with a decent MIMO base station!
Please help understand where and what interface can be used to change the 1/ minute preset cycle. I am looking through the documentation but could not locate that. Any help/pointer on that front will be deeply appreciated.
There’s no way to change the 1/9 minute cycle right now. We’re currently working on the “running with wifi disabled” implementation which will give you much better control over what happens when wifi goes away.