@dan An empty string is returned in cases, when the LTE modem takes longer than 10 seconds to respond. Sending an empty AT command (lte.send_at_command('')) may show such a late resonse.

thanks @tuftec your code works great! @jmarcelino I still would like Pycom to advise if they have a preferred approach for the LoPy to (restrict) the frequency channels in AU915 region? thanks, Phil

@timh @IOAg I am not sure how you guys have been going with the LTE stuff but after 2 days of testing I am still finding it very flaky. I tried your earfcn settings and find that the unit finds a cell tower much quicker and consistently but still would not attach. I then updated to the latest FiPy firmware and then updated the Sequans firmware as per (https://forum.pycom.io/topic/2902/cellular-radio-firmware-release-sqn3330-for-both-cat-m1-and-nb-iot). I then found I started to be able to attach and connect. However, saying that, it is still inconsistent. I have had my device in the same spot for two days and I will get periods where it will connect almost every time, then hours where I get nothing. I also still have the modem crash when it is connected after a short period of time and then have times when it won't recover (lte.reset fails and machine.reset does not work either) with the only solution to perform a complete power cycle of the FiPy unit. Also it does not always attach/connect first go and I need to reset/attempt to attach in a cycle a few times. So while, when it does work, it connects more often there is no way I can consider my FiPy/The LTE modem as a reliable device. Pretty much at my wits end with this and looking at moving to a new platform. Would be interested to see if your results are similar or you feel you have a complete stable solution you would use as a commercial product?

Thks jmar, have just save me burning hours.. Cheers dude, pizza's & beers on me!