@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.

@daniel I understand Telstra connectivity issue should be resolved. I don't see how to test it myself, Sequans firmware being unavailable at the moment. Did you get positive feedback in this forum?

@paddy Any new info on this topic? I cannot get my FiPy to keep uploading for more than a few hours - sometimes 20 minutes - without returning endless EAGAIN or EHOSTUNREACH errors on HTTP calls. This a huge problem for my remote weather station design. I am going to have to have a fully parallel Raspberry Pi zero to run reliably 24/7 and sample the sensors (defeating low power requirement), since I currently have to shut down and reboot my FiPy in code everytime I start getting the HTTP request errors. American Verizon Wireless SIM card through Nimbelink and updated Sequans firmware. Dear Pycom: I want to love your product. Please help.

@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?

@ioag Any chance you could share your Telstra connect code? I must be doing something wrong... Does anyone have an update on the stability issues?

@sat said in LTE CAT-M1 on Telstra using FiPy: I can confirm that certification is NOT required for connection to the network. I have tested various uncertified modules to connect to Telstra's network. @jmarcelino @IOAg @Sat I spoke with an IoT engineer at Telstra today and you are correct @Sat , Telstra do not block devices. However, the engineer was aware of the Pycom devices and stated without prompting that they have a "firmware" issue and that's why they won't connect, it is nothing Telstra side. I tried to dig deeper but he could not give any specific details other than a firmware issue with the current Pycom LTE devices. **EDIT**: I spoke again with Telstra and they believe the issue is with the firmware on the Sequans modem. Looking through the forums here I saw that the APN name "internet" is hardcoded in? According to my sim supplier the APN for Telstra's IoT network should be telstra.m2m (or alternatively telstra.internet). The Telstra engineer confirm this needs to be set correctly and could be causing issues. I am good working with python but my ability to easily update and recompile the firmware for a FiPy is lacking... Is there someone out there that could do a quick check to see if this fixes the issue? Or at least give the option to specify the APN on the LTE.init() function?

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