@nagarjuna-reddy same here

You don't need ulp for pin wakeup. You can do much less than 150ua if you sleep inside ulp program.

Hi @lebucur, The only difference between the LoPy and the WiPy 3.0 is the LoRa stack only. All of the underlying firmware is identical!

@livius That is funny, because I had this work for 2 months before having issues. Now they seem sporadic. I am worried a sensitivity is now showing itself. But we will see after more testing. thanks

@redimo Good luck. Thanks for the update. We scan BLE for 10 seconds then delete/restart the ble object. I'm noting there are maybe 3 updates we've not tried yet for BLE reliability. Maybe they are better? Very interested in how it works for you.

@YazIdo I think this may be an error associated with an accumulating number of open sockets. I got the same OSerror: 23 after running the MQTT example for the 8th time and beyond. A soft reset does not clear this, but powering on/off does clear it - and it works again, at least for the first 7 times. I fixed this problem by adding one line at the very end of the MQTT example. client.disconnect()

Hi @amartinez, There's a really good explanation about GATT (Generic Attribute Profile) here - https://learn.adafruit.com/introduction-to-bluetooth-low-energy/gatt Currently BLE is the protocol available but classic Bluetooth will be coming in the future! Thanks!

@jmarcelino Because we want preserve the Pycom WiPy firmware ad edit it with some frozen files and custom API C (like SSL and BT that have some problems).

@robert-hh Hi, thank you for the answer, I think I missed something during the procedure because I tried again from scratch and it works perfectly. I think I forgot an environment variable as you propose.

@jmarcelino '1.6.12.b1'

@bucknall just posted about sending images over MQTT, perhaps one for another Corner?

@robmarkcole I use a lot of TL-WN722N adapters, especially because they are cheap and reliable (and support some other features such as monitor mode). What Alex suggested is also a good option, but unfortunately not always possible when you are not at home (e.g. I need special permission to use any device on the educational network).

As you need to connect using wireless to modify 'boot.py' in the first place this makes disabling the wireless interface by default an 'interesting' challenge to a new user! Hopefully the wireless, bluetooth, etc are only started (if not already active) after 'boot.py' is executed.

@michalt38 OK. Then you'll need two steps: First, you have to connect the WiPy to the network. That's done with wlan.connect, as given in my sample scripts. Second: you have to write a little program for you WiPy and your PC that connects through sockets and sends the data. The IP adresses used are those of the WiPy and the PC, not the one of the router. You have to define which entity connects (socket.connect() ) and which entity accepts (socket.accept()). For initial testing, you can use for the PC side netcat (nc), which is a simple raw socket send/receive program. Examples for the WIPy side are here: https://docs.python.org/3/howto/sockets.html or here: https://www.tutorialspoint.com/python3/python_networking.htm

@robert-hh Since that was the problem in another discussion: Verify the the jumper is between GND and G23. G23 IS NOT P23. Internally, this is GPIO0, also tagged as P2. If the heartbeat LED is still flash after setting the jumper, you're not at the right port.