@jmarcelino wow, thanks a lot for that find. explains the headaches I've been having :)

Issue solved by doing a complete download of all sources then re-doing all steps again.

Why would you want to run your device directly from a solar cell? You will need a much larger panel/ device and it will be extremely weather dependant. Stop torturing yourself and get a tiny solar charger and a lipo battery, and Plug this into the battery port of the board, and you are done!

@jubbs I see. With that information, it shouldn't be too hard to write a "directory sync" script :)

@sthomson No. i have played videos over wifi. I will try to stream video over wifi from one wipy to another and will let you know.

@caseyrodgers Yes me too .. Cloudflare Error 502 Ray ID: 37e6d8073a2d6a37 • 2017-07-14 19:21:14 UTC Bad gateway .. software.pycom.io Host error It's the right tool, just not working ! :(

@ahaw021 @bnjroos Thanks for the information, I really appreciate it. I'd like to give a go for option A as it seems more straightforward. :)

@jmarcelino Ok, I'll try with ABP as well and let you know. If this is the reason, then if i remove and re-set the channels after the join operation, wouldn't be "fixed"? UPDATE: With ABP all seem fine. I also tried again with OTAA. I noticed that in the github code the non-default channels were actually removed after join, whereas in my code this did not happen. So, when I added this code after join OTAA did work fine as well. Another remark: how do we know if we work with 3 or 8 channels? Many thanks @jmarcelino for your help!

I found sipy very power hungry when starting around 460 mA if i put my Fluke to measure amps on the 400ma Fuse the sipy will not start...

Could someone explain what consequences it brings in the operation of the device when these errors come out?

@jmarcelino got that ;) i prefer the sparkfun then because I can plug a standard cat5e cable which is widely available. Thanks for your help!

@livius I am using the official library taken from here https://github.com/pycom/pycom-libraries/blob/master/shields/lib/LTR329ALS01.py which indeed as you noticed does not contain the ALS_STATUS status register reading logic. According to the datasheet https://www.mouser.com/datasheet/2/239/Lite-On_LTR-329ALS-01 DS_ver1.1-348647.pdf Page 22 the Device operation flow chard shows indeed kind of a loop until that status register indicate a new data is available. on Page 24 it shows a pseudo code mentioning what you are suggesting (which is checking the data readiness before performing the actual read). Page 21 it describe how to perform the check of the validity of the read. I can try to patch the lib according to such information and push a PR to the official repo if this is solving the problem :-). Keep You posted and thanks for your help! Stef

@dbrgn Thanks for the notification, I can confirm that it works!

I have tried this before with LoRa and it didn't work. I expect the same result with Wi-Fi as the clock and other network delays are the biggest problems. To get accurate results you would need a very reliable clock, which isn't available. Also ntp servers will only let you sync up to a certain accuracy which is not good enough by far. Fingerprinting, multilateration etc. are maybe alternatives you could check out.

@jcaron said in First steps with LoPy & PySense and feedback: The cases (probably) fit the expansion board, but not the PySense. Wouldn't hurt being a bit more explicit about it on the site. Are there any cases that would fit the PySense? +1 for the cases issue. I bought a PySense and a PyTrack and a case for each. Pretty frustrating that there aren't the appropriate mounting points in the case for those boards.

See the following post on how to manually flash the firmware: https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users