MicroPython Forum

Thanks for the suggestion, fangus. I'll have to give it a try. It finally crashed again but it now gave me a different error:
It's referring to the last line in my function in my OP.

Murphy's law seems to strike again for me. My current project is simply sending some temperature data to my Pi with my Wemos D1 mini. I finally got everything working smoothly, or so I thought. After an hour or two of running a loop that reads the temp sensors and sends the readings to the webserver...

Thanks for the explanation, I'm seeing it now, WebREPL is formatting those numbers as asii characters, got it.

Been learning how to use i2c under Micropython. I've figured most of it out, but I have a frustrating issue with reliably receiving the second temperature data byte from my temperature sensor. I've even lowered the i2c frequency down to 1KHz and I'm still not receiving the second data byte occasiona...

Sorry for the late reply, had an urgent matter to attend to. I took another shot at it a few minutes ago, and now everything works fine; it must have been something stupid on my part (guessing that I didn't tab over correctly for a line of code, or something similar.) I was trying out the first exam...

I've been trying to call a function from a file, having no luck I tried the example from the page: http://wiki.micropython.org/Importing-Modules But even with the example this is what I get: Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: 'module' object has no...

SUCCESS! After reading the reply on richarddavison's thread (https://forum.micropython.org/viewtopic.php?f=16&t=3665) , suggesting that the one that I have may have an ESP8285 chip. I tried the instructions provided in the linked thread(adding --flash_mode=dout) and success, I now get the REPL promp...

Nope, never found a solution. I did get a refund and ordered a replacement. Will see if that one will work.

I tried setting the UART speed to 74880 (and several over baud rates) to see if what I was getting at reset was actually something else other than garbage, but so far have had no luck. Balu, what firmware version worked for you?

I've been using the --verify option, and I've been getting verify OK every time.