Kiril Zyapkov

This is correct. The default http handler can be useful in other scenarios as well.

Yep, that'd be nice

`ESP32-PICO-D2` needs `CONFIG_FLASHMODE_DIO=y` appended to `ESP_IDF_SDKCONFIG_OPTS`, specifying the mode in `--esp-flash-params` isn't enough. This was not the case with IDF v3.2. Edit: appears to be a manifestation of https://github.com/espressif/esp-idf/issues/6191

After some hesitation between improving the python script for OpenGD77 and this, I've started work on this. Looks like the serial protocol for OpenGD77 differs significantly from the one already...

Indeed, this was me on the forum and after some further consideration I've decided to go the python way. Speed and efficiency are not key here, a functioning CPS tool...

I was able to use a [blackmagic probe on a cheap "Black Pill v2"](https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/blackpillv2) to flash a Zephyr-based firmare on the b-parasite. The BMP even supports [RTT](https://github.com/blackmagic-debug/blackmagic/blob/main/UsingRTT.md) which works as...

I don't own an original BMP either, they seem to be unobtainable. However, ports exist for many cheap boards, see the [supported platforms](https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms) in the code, each comes with instructions....

I am also against having this functionality in aioshelly. Albeit rare, devices may require specific upgrade paths for some older versions. If the wrong firmware is flashed on a device...

You could let devices fetch update info -- call [Shelly.CheckForUpdate](https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Shelly#shellycheckforupdate)

There is a commit in a fork https://github.com/cduck/necpp/commit/dc2682f84f1ddd0dfaf2ff86901a0280d67de1d1 which addresses the issue.