@robert-hh I was thinking about that however I am not aware of a straightforward way how individual parameters could be updated by the application. The script would be frozen anyway. I was also thinking to move all parameters to NVS however the config also contains few strings which are not directly supported by the NVS right now. I think that the best solution will be to put default parameter values into Python script which will be frozen during build process. After boot it will be tested if NVS contains "init" flag and if not an initialization method will be called. Within this method individual parameters will be loaded from Python script to a dictionary which will then be dumped into json file stored in the internal file system. This will happen only during first boot after last firmware flashing.

@charly86 For OTA you just need appimg.bin, if the other two files are already loaded. The esptool.py command line for that would look like: esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 460800 write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x10000 appimg.bin

Issue solved by doing a complete download of all sources then re-doing all steps again.

@Arkaik In the list of commits, you have to go back to an entry with the title "Bump to version 1.4.0.b1". There you find the fingerprint. It's not a long way. In you first port you mentioned 1.4.0b1. But now you mention 1.0.4b1. About esp-idf. Do use the version indicated by the pycom web site.Try to checkout the most recent version before the date of the wipy firmwar you are using. That might get a little bit of a trial & error game.