Enabling microdot to run other things while app.run()

[AppsByDavideV]

Hi,
great app!
I would like to run other tasks while the server is running and serving pages, but my knowledge about micropython is too low (just started, coming from c/c++ arduino). I tried to play with uasyncio (and even I had a look at the code into microdot_asyncio app.start_server) without lucky.

Is there a way to run other tasks while the server is running?
Thank you so much for answer ;)

[miguelgrinberg]

The most common way is to use asyncio, so you were in the right place. The app.start_server coroutine handles the server, you can start this task and others and they'll all share time under asyncio.

[jouellnyc]

You are both gentlemen and scholars!

[jouellnyc]

In case this is obvious, I am having trouble installing microdot_asyncio.

I can't find it - I've looked in the repo here.
I can't upip it as upip is not on my pico:
"MicroPython v1.22.1 on 2024-01-05; Raspberry Pi Pico W with RP2040 (installed via Thonny 4.1.2)"
I chased upip and upip_tar files manualy to get upip back, but was not successful after failing to find zlib.
I understand there is discussion re: mip but @AppsByDavideV , how did you install it?

[miguelgrinberg]

@jouellnyc this discussion started before the release of version 2 of Microdot. Back in version 1 there was a thing called microdot_asyncio. In version 2, Microdot is always asynchronous, so you get asyncio support without having to install any add-ons. As to how to install it, do not use upip, see the documentation to learn which files from this repository you need to copy to your device.

[AppsByDavideV]

Hi @jouellnyc , for readability you can create a folder called 'lib' into your device and copy the files inside it.
@miguelgrinberg already answered to your question, anyway the related files you need are in the repo, into 'src/microdot' folder, but this is a new version of the library.
Bye

[jouellnyc]

Aha. Yes. Thanks @miguelgrinberg! I had used microdot a year+ back with excellent results but fumbled w/the asyncio as I am getting back up to speed. It is developer's like you creating these create products that make working with micro controllers so much fun.

[Jarshvor]

Hi, and sorry to hijack this discussion, but I feel it might be related:

I am wondering if it is possible to run Microdot (have the server running) while at the same time retain access to rshell or some form of repl prompt. I would like to be able to keep interacting with the rshell after the server has started, either via app.server_start() or app.run().

I have read a bit on asyncio, and tried poking about with it, (also tried AppsByDavideV's code above).
I am quite new to micropython, microdot, rshell etc so I am not entirely sure if this is a limitation on the rshell/repl side and how that's started.

Any sort of guidance or assistance would be greatly appreciated (even if to say "nah, what you want isnt really possible").
And thank you for creating Microdot. =)

[miguelgrinberg]

I have not tested this myself, but I think the aiorepl package will allow you to do what you want: https://github.com/micropython/micropython-lib/tree/master/micropython/aiorepl

[Jarshvor]

Thanks for the super fast reply Miguel!
I was indeed able to get it working with the following code.
(sharing in case anyone finds themselves in a similar situation).

aiorepl_start.py
(or main.py or however you wanna start it)

import asyncio
import aiorepl
import webserver

async def demo():
    await asyncio.sleep_ms(1000)
    print("async demo")

state = 20

async def task1():
    while state:
        #print("task 1")
        await asyncio.sleep_ms(500)
    print("done")

async def main():
    print("Starting tasks...")

    # Start other program tasks.
    t1 = asyncio.create_task(task1())
    webtask = asyncio.create_task(webserver.start_server())

    # Start the aiorepl task.
    repl = asyncio.create_task(aiorepl.task())

    await asyncio.gather(t1, webtask, repl)

asyncio.run(main())

And then in webserver.py we make sure the start_server() function is asynchronous and to await the server start and sleep.

webserver.py

import uasyncio
from microdot_asyncio import Microdot
from led_module import led

# Setup out GPIO constants:
led = led(23)

# setup webserver
app = Microdot()

# Make a default 'root' route:
@app.route('/')
async def hello(request):
    return 'Hello world'

# LED toggle
@app.route('/led')
async def toggle_led(request):
    print("Receive Toggle Request!")
    led.toggle()
    return "OK"

# Start the webserver
async def start_server():
    print('Starting microdot webserver app')
    try:
#        await app.start_server(port=80)
        await app.run(port=80)
        await asyncio.sleep(3)
    except:
        app.shutdown()

[themeadery]

@Jarshvor Does this work with webrepl also?

[Jarshvor]

@Jarshvor Does this work with webrepl also?

I'm not sure @themeadery as I've never used the webrepl (yet).

I believe we might have to modify how the webrepl is started?
Maybe give the following line a try:

# Start the WEBREPL task.
    repl = asyncio.create_task(webrepl.start())

But I suspect the above won't work if webrepl is not coded to be asynchronous. (note the a in aiorepl)
So it very well might not work without adjustments to the webrepl code.

But I believe you can also access aiorepl over wifi(telnet) and not just serial if thats something you're after.

If you end up trying this out with webrepl do report back if possible. I'm curious. =)
Thanks!

[ned-pcs]

Yes, webrepl also works alongside aiorepl and microdot in async mode.

I'm starting it the usual (non-async) way:

        try:
            webrepl.start()
        except:
            log.info("webrepl not started")