H3adcra5h

No, you are right, it's not implemented see: [https://maixpy.sipeed.com/maixpy/en/api_reference/standard/usocket.html](https://maixpy.sipeed.com/maixpy/en/api_reference/standard/usocket.html). Why not is a very good question. I think too much work to implement the whole at command set. The network...

No way yet. The only way is writing your own esp-at library, but it's a lot of work.

4 is the same as SPI.SPI_SOFT

The documentation isn't so clear on this side. You have 4 hw SPI devices. SPI2 can only work in slave mode, but I read somewhere. maybe in the documentation, that...

But then this example "@app.on_topic("hermes/+/{site_id}/playBytes/#")" would not work anymore. In some of my cases I need the payload as bytes. Maybe with a second parameter we can force decoding from...

Yes I do. That's why I implemented this. In my app(s) I do much more than intent handling. Some of my own sensors communicating over MQTT and I use this...

The intention for my implementation was the possibility to handle topics outside of the main scope "intent handling" in a flexible way. The decorator will definitely work with all topics....

This should be possible with: @app.on_topic("rhasspy/asr/{SITE_ID}/{SESSION_ID}/audioCaptured") but I not tested it yet.