@yongyuan-wang I would be surprised if you didn't have any other devices sending out BLE advertisements at hand. Nearly any phone would, for instance. Most if not all Macs, many PCs, tablets, TV boxes... In an urban environment it's actually difficult to not see BLE advertisements all over the place, probably even more than Wi-Fi.

Well, if you're running the nano gateway alongside pinging it, that could introduce some additional delays, as the nanogateway is quite socket-intensive, though I would not expect 3-5 seconds of delay there.. Just to confirm, did you erase the device fully (clear NVS and CONFIG partitions as well as erase the flash) before starting?

@tuftec Okay..thanks... Switched to LFS now....let's see if it is more stable... But still it can't connect to the things network...

@yongyuan-wang You should be right, so its between 32 and 64 msec

@rcolistete Thank you but for this thesis' project i have only this type of sensor. I'll remember it!

@rcolistete Yes it works, Thanks. By the way the following is the correct link to the LHT65 documentation: http://www.dragino.com/downloads/downloads/LHT65/UserManual/LHT65_Temperature_Humidity_Sensor_UserManual_v1.3.pdf The single channel instructions are on page 36

@davorin The version is slightly different, as it contains a few bug fixes. And there is no pybytes in it. Waiting for ntp.org sometimes happens.

Let us know. Im not familiar with the NewChannelReq and how it works, but I've been diving deep in the Loramac stack for the adaptive datarate over the past few days, so i'll take a look here as well.

@Laurent-Toutain Smart provisioning is the pybytes stuff, which indeed mangles with the communication interfaces. If you do not use pybytes, switch it off. import pycom pycom.pybytes_on_boot(False). If that does not work, create a file on your device called pybytes_config.json and the content: {"pybytes_autostart": false}

Have you solved this problem?

@M-m I've found the LOPY4s more sensitive to power cable length than GPYs. I can run GPYs on a dev board powered from a cheapie (minimum copper)1m long usb cable no problems, but with a LOPY4 I need to have a lipo plugged into the dev board to prevent random resets. It's maybe something to do with the different radios?

I want to make an Android application to implement some simple functions, such as changing the LED lights, or obtaining data from its own sensors. But I need to pair first, then launch an application that lists all paired devices, and then I can select the device to read/write data.

@robert-hh of course

@Sirajuddin-Asjad apparently in recent releases you need to add PyMesh support via PyBytes before you can use it. See https://docs.pycom.io/pybytes/pymeshintegration/provisioning/ for details.

Hello @jcaron , Sorry for the inconvenience caused. As a a new user it is not letting me edit it and then submit it again. I have tried multiple times now. I will keep on trying until it lets me do that but in the meantime do you have any idea as in what might stopping me from getting the BLE device connected. Regards Subham

@berni You can use any digital bidirectional (i.e. non analogue input only) pin which is not allocated to another functionality. This means you should avoid: P13-P18 since they are input-only pins, P12 which is used for antenna selection, P5-P7 which are used for LoRa radio, and P0-P1 used for UART.

@Alex-Ray said in Inverted IO Logic: Am I just not understanding something? Am I looking at this wrong? The answer is yes. It depends on how LED and/or button are connected. pin(1) puts ~3.3 V at the output pin, pin(0) outputs 0V. Similar pin() reads 1 if the input level is ~3.3V, and reads 0 is the input level is low. If your LED is connected the common way between output and 3.3V, it will light on if the output level is low, and go off if the output level is high. If the button is connected the common way between input and GND, pin() will read 1 if the button is NOT pressed, and 0 if the button is pressed.

Hi Guys, I seemed to have solved this by moving the time.sleep(1) of code into the if statement. This also solved the EAGAIN error that I was receiving. Thank you for the time you all took to reply.

Thank you Gijs I missed the significance of the script John