MicroPython Forum

In V3 you can always clear down an event immediately after setting it: I think this is normally the best way to use the class as it keeps the set/clear logic in one place. This avoids risks of an event being set and not cleared. I would highly recommend not to do that. It's not a matter of how V3 w...

Don't clear the event in the reading method, let the main loop do that. As for the 2 seconds delay, you can change that by turning your main loop around a bit: async def update_display(display): # if needed wait a few ms on startup while True: print('Update display') display.fill(0) display.text('Te...

You can poll all events like: a=[event1,event2,event3] for event in a: if event.is_set(): # process LCD event.clear() await asyncio.sleep_ms(20) The downside is obviously that it checks all the events every 20ms and is therefore less efficient than awaiting a single event directly. Also it might tak...

ds.scan() is unlikely to throw an exception. In my application I catch oneWire errors on conversion and any type of error on reading: https://github.com/kevinkk525/pysmartnode/blob/0cd27d9aecdac334abbd70d939d03d68832e164b/pysmartnode/components/sensors/ds18.py#L148 https://github.com/kevinkk525/pysm...

oh, then my chain might have pulled that version before it got removed. Thanks for reporting the needed change.

You might need to catch "onewire.OneWireError"

Ubuntu 20.04 installs:
Note, selecting 'libexpat1-dev' instead of 'libexpat-dev'
libexpat1-dev is already the newest version (2.2.9-1build1)

So where do you pull 2.1 from?

or build micropython-dev for the unix port which includes uasyncio. (And complain on github so uasyncio gets finally merged in the non-dev unix port...)

See how I'm doing that in my project using __import__(): https://github.com/kevinkk525/pysmartno ... nts.py#L66