@rikkertmark Did you ever get an answer?

As Alex says it's an external library. The file needs to be present alongside your boot.py and main.py or in one of the folders in your search path. So when you don't have the mqtt.py file it gives that error.

@jmarcelino thanks for your response, hopefully they will implement the WDT in the LoPy soon. I might try and do something with the internal interrupts in the meantime.

@livius the reason why I wanted to use the Other function is having Control of the stop Bit. I know "your" function Works, but does it Send a stop Bit When it's done? Thank you for your help!

That code is only for use with a single channel gateway/LoPy as nano-gateaway. If you have a real - multichannel - gateway like the Multitech use the code from the documentation https://docs.pycom.io/pycom_esp32/pycom_esp32/tutorial/includes/lora-otaa.html

@robert-hh good solution, thanks.

@jmarcelino exactly if someone have acces to device it can break it in really simpler manner than do some supported by some device reset features ;-) @lawrence Think about as @jmarcelino show sample, hammer, drill i can add more e.g.: water, remove power source, electric shock, put into metal case...

@ssmith That's right. I recall that post. That is definitely an intentional behavior and looks like a Python bug. I have code for esp8266, which intensively modifies global variables, and that runs stable. I had once ISRs, which modified global variables and after a while flagged, that it could not find that variable any more. As far as I recall, that was viper code on esp8266. So there might be similar strange conditions happen here.

@Marco-den-Hartog Micropython itself implements Version 3.4, but the scripts used in the build procedures on PC are a mix of Python2/Python3 code. For some branches you need Python2, for others Python3. for instance esptool.py was only recently Ported to Python3.

@livius oh man, such a stupid mistake! thank you man!

@scg94 Even if a solar cell is mostly a current source, I would limit the voltage to about 5V, to be compliant with the regulators and the interface you are using. About the charge current look at the documentation here : https://docs.pycom.io/pycom_esp32/_downloads/exp_v03_pinout_v13.pdf It's 450 mA (with jumper) or 100 mA (without jumper).

@robert-hh said in Use photocell with GPIO: me could be longer, and must not be not shorter, since it discharges the capacitor. The sample code talks about a loop time of 1 ms. WiPy is faster. The loop time should be around 15 µs. Are you sure that you connected the photocell between 3.3v and P10? If you never have a '1' reading at P10 as input, then the wiring is wrong. I mad a quick crosscheck with G9 = P22, and sleep(0.1), and it worked. Nevertheless, you could do better using the analog ports of the esp32 with a resistor and the photocell. Hello, I just tried again and it is working now. Thanks

@robert-hh Thanks a lot Robert and Livius! I saw indeed the PWM example in the Micropython docs to dim a led.

@affoltep I have not done the pull request--the repository was modified and I haven't taken the time to sync this back up. I'll take a look in the next day or two to see if I can just clone the new repo and easily merge in the changes. It has been on my list to do the pull request for the SF change to make it easier to use my single channel gateway at home (while I patient wait for TTN to ship my full-fledged gateway).

Hello, The schematics for the deep sleep shield are now available here: https://docs.pycom.io/pycom_esp32/_downloads/Deep-Sleep-Shield_Schematic.pdf Thanks Fred

@PiAir It's by design, although admittedly confusing haha. I have an update to this where I'm connecting a LoPy up to a Raspberry Pi 3 which is running Node Red. The idea is to use this as an easy config Nano-Gateway. I'll update this when I get around to publishing this!