@protean Hi, when you click on "get location button", Device scans the wifi networks around and sends the result to Pybytes. Pybytes is using Google location API to figure out and the location.

@rcolistete thank you for the pointer I have tried and no problems so far I'll give it a couple of days before sending it to the wild :)

@robert-hh Can you give an example how to send data using 1nce sim card?

Hello, in this link they answer quickly to all the doubts. Sigfox Ask Regards,

@wghirakawa Related to a different question (https://forum.pycom.io/topic/4118/gpy-or-fipy-using-lte-in-the-us), could I please ask you to check the result of 'AT+SQNHPLMN?'. I am trying to find out if Sequans supports 6-digit PLMNs in the US.

@Paul-Thornton What is the answer to his question though? I too am very confused by the documentation for the Fipy and expansion boards. There is conflicting or outdated information regarding the expansion board v2.0 and v3.0. Often I don't know which is being referred to, and worse, Pycom's channel resellers like Mouser, Digikey, etc. often mix them up.

@wghirakawa The code seems to be ok. I don't have access to Cat M1 network (only NB-IoT available here) so I cannot test with the same Sequans firmware. Are you able to perform communication on the same APN and with the same SIM using different hardware? @iwahdan could you please take a look?

@mraj That's the way: Either it is called main.py, or main.py contains a line import mycode or boot.py contains a statement machine.main("mycode.py"), which causes mycode.py to be executed instead of main.py

@combaindeft Hej! I have just started to play with he Telia IoT using fipy. But I guess I am having similar problem with the socket creation as you experienced. I got such an error OSError: [Errno 113] EHOSTUNREACH while connecting to sockets. So how is it working for you now? Thanks.

@nada-ali talk to each other over what network? The answers may be very different depending on context...

@robert-hh I thought so. Thanks.

@mraj By hardware or by software? By Software: if you have a communication defined, you can define a command which leads the Lopy to do execute machine.reset(). By Hardware: You need extra hardware, which depending on what you need either toggle the reset pin or power off/on the device. A separate small micro could do that, maybe even the PIC which now resides on the various expansion/ensor boards. There a subtle (unintended I guess) differences between machine.reset(), pulling the reset pin and power cycling the device.

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

@nickb This is a standard AT command. the response tells: "scanning with unsolicited response enabled" (first 2), and "not registered, but MT is currently trying to attach or searching an operator to register to" (second 2) https://www.etsi.org/deliver/etsi_ts/127000_127099/127007/12.07.00_60/ts_127007v120700p.pdf or https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIL0iGdl11z7Jos_jpX%2F-LKN7scqKKkb6TqB3uYO%2F-LKN82sqi_sHewyinxC5%2Fmonarch_4g-ez_lr5110_atcommands_referencemanual_rev3_noconfidential (2).pdf?generation=1534782114581269&alt=media

@dommei That's means: "not registered, MT is not currently searching an operator to register to". At my device, it toggles between 2,0 and 2,2. The response you need is 2,1 or 2,5. The AT command set document is here: https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-LIL0iGdl11z7Jos_jpX%2F-LKN7scqKKkb6TqB3uYO%2F-LKN866sBhZY7wCqpQPA%2Fmonarch_4g-ez_lr5110_atcommands_referencemanual_rev3_noconfidential.pdf?generation=1534782117167775&alt=media

@robert-hh Many thanks. :)

@tfgm Not directly with the FiPy. You can use a chip like INA219 to monitor the current & voltage at the wire getting in to the device, and then you can determine the mAh that have been consumed, and in combinations with the voltage also the energy. The timing resolution is not very good, mostly limited by the time you allow your code to measure. So you will miss small spikes & drops. For convenience, there are modules with that chip available. There are Python drivers from Adafruit and one here, tested on ESP32 and ESP8266: https://github.com/chrisb2/pyb_ina219 Both should be close to Pycom's python. The gap, if at all, should be in the I2C section.