search

peterhinch / micropython-mqtt

A 'resilient' asynchronous MQTT driver. Recovers from WiFi and broker outages.
MIT License
550 stars 117 forks source link

Contact you? trying Your code on ESP32 #2

Closed Wessix closed 6 years ago

Wessix commented 6 years ago

Hi sorry to contact you that way. I'm trying out your umqtt asyncio code on esp32 and would like to contact you. If you are in any IRC Chat oder Skype or something else, could you let me know? I'm not a python professional but with some trial and error i got a dht22 sensor and Oled Display to run and make the esp32 report to Home Assistant with mqtt simple.
After some tests i figured out, that if the broker goes down for some reason, the mqtt simple fails. With your code this works. But when i simulated a wlan shutdown, my esp32 froze at reconnecting. On Skype you could find me as w-e-s-s-i-x-1 (without the "-").

peterhinch commented 6 years ago

The ESP32 MicroPython port is still somewhat experimental. You'll see some of the difficulties I encountered here. So my code includes a number of arbitrary hacks to make it run on ESP32. It rather sounds as if a firmware change may have actually made it worse: I did test with sudden and gradual failures of WiFi connectivity.

I am currently busy and am unlikely to be able to look at this until early in the new year. But I do plan to review its operation on ESP32 with a view to removing the hacks and re-testing.

The best way to contact me is via a personal message in the forum where my username is pythoncoder.

Wessix commented 6 years ago

Ok thx for the quick reply, ok so I'll open a user account there. I wrote cause i read in one thread that you would appreciate if somone can test your code on esp32. Well before Christmas its busy for all of us, so no Problem. I would dig further into the problem if i had an error code, but the console throws no error, just freezes.

So see you there.

peterhinch commented 6 years ago

I trust you read the link I gave you - it sounds very much like your problem which @dpgeorge has confirmed still exists. Until the underlying firmware is fixed I think we're stuck.