@crankshaft i am in the same position as you OSError: [Errno 113] EHOSTUNREACH but only in current firmware other wipy with 1.5.0 work ok many days.. but with 1.5.1 above error

@livius Both antennas were connected. Today I unpacked a brand new LopY ... and we did again the tests. Same results also with this new one. I send to Daniel the onewire.py script... you ca do it yourself and see the issue with your own eyes .

Ok, success. I didn't persist with the GUI installer, but I suspect the problem is that the Python install it brings with it is looking in some OpenSSL directory for the set of CA certs to trust. On OSX this is empty because MacOS keeps such things in its Keychain, and the normal OS tools (including the stock Python) are configured to look there instead: http://stackoverflow.com/a/24694579/326838 Major fail for just hanging the UI instead of reporting the error though. WTF? It's not as if calling out to a Web server is some infallible operation that will always succeed. Anyway, the CLI python updater that @jmarcelino pointed to above worked fine for me. OSX Sierra, 10.12.3 (16D32). I did install pyserial first (I assumed it was needed, didn't actually check what happened without it). The quickest way to do that was to grab the Rudix installer for pip and then do sudo pip install pyserial. Thanks for the pointer to the commandline updater and the firmware image; I hope this post helps others in the same boat. Pete

@Shaun Yes, I tried also this mode. I don't know if it reseted the boot.py because I still can't connect the WiPy's Wifi network and the WiPy don't connect also on the home network while it was working just one day ago. I'm sad because I was ready to daily and weekly FTP get (from a web server) datas saved on the WiPy's flash card, temperature curves, and render nice SVG graphics. It was the first important step of my project, it was ready to run, and now I have to redo lots of things, adapt the code to the WiPy 1.0 (no floats). I even tryed to connect the WiFy network of the WiPy 1.0 and it's not working also now ! I have 3 different stations at home, no one is able to connect the WiPy'w Wifi again. I don't Know what is breaking the WiPy's Wifi networks, but all my other Wifi devices are working well. Could it be a conflict between the two WiPy's ? Or something in the neighbourhood ?

Ok. So it's not bricked. But, I'm having troubles updating the firmware.

Hi, this when it is running as a server listening on a socket: Here's the log when it started responding again: I (570808) wifi: bcn_timout,ap_probe_send_start I (573309) wifi: ap_probe_send over, resett wifi status to disassoc I (573310) wifi: state: run -> init (1) I (573310) wifi: n:6 0, o:6 0, ap:255 255, sta:6 0, prof:6 I (573313) wifi: pm stop, total sleep time: 31991844/522829466 I (573590) wifi: n:1 0, o:6 0, ap:255 255, sta:1 0, prof:6 I (573591) wifi: state: init -> auth (b0) I (573710) wifi: state: auth -> assoc (0) I (573716) wifi: state: assoc -> run (10) I (573896) wifi: connected with wlan@xxx, channel 1 I (583716) wifi: pm start, type:1 I (1249950) wifi: state: run -> auth (7c0) I (1249951) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:6 I (1249951) wifi: pm stop, total sleep time: 20393547/645746648 I (1250075) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:6 I (1250076) wifi: state: auth -> auth (b0) I (1250158) wifi: state: auth -> assoc (0) I (1250162) wifi: state: assoc -> run (10) I (1250569) wifi: connected with wlan@xxx, channel 1 I (1260162) wifi: pm start, type:1 I don't know if I am reading this correctly but it looks like it put itself to sleep and disassociated itself from the wireless ??

@daniel WiPy 2.1 can't come too soon!

Many thanks! So I will wait for the next update..

@jmarcelino - thanks, I am now seeing crashes regularly pretty much when anything that involves interrupts or threads. I am starting to think that maybe threading is still work in progress ??

Got that, should have read a little further up in that document. Easily downloaded the boot.py and main.py. Now I just need to understand why pymakr disconnects and re-connects every 6 seconds. Regards George

@Knoahlr, thanks a lot for the feedback. Keep me posted in case of any change.

the IBM Bluemix IoT relies on MQTT. You have to send to the appropriate topic with the correct username+password. If you create a device in Bluemix, you will get a device id. This device ID is included in the topic. You may want to checkout the python reference implementation. I assume this applies also for the Watson IoT stuff

@sakis I'm not sure what was causing it, but I've since been able to find and connect to the network. Seems some combination of forgetting known networks and restarted resolved the issue.

It help looking up help(pycom)... there it was: heartbeat and rgbled....

@ubiq_01, you can connect to your device and perform: import os os.mkfs('/flash') That will format the internal storage to it's factory state. Hope it helps ;)

@jmarcelino Thanks! We have managed to flash the board and seems to work better now, but I think that we're still missing some data. The 32 for the queue... could be raised without problem or it would be risky?

@lcgeldenhuys said in How to configure BLE Advertisement Behaviour eg rate & TX_PWR?: So with adv_int_max at 40 milliseconds, it looks like I would have to do bluetooth.advertise() with enable / disable on a timer if I want a 500 millisecond interval? What I'm really after is a single advertisement at a configurable rate of say 1 to 4 per second. Would be nice if a future bluetooth.set_advertisement() could take a rate parameter. Same here, I look to do a beacon that could last 5-10 years with a single battery. Until we get the deep sleep, it is just a mere dream for now. Benoit Despatis, P.Eng.