Retest requested: network / MQTT / OTA refactor in 1.1.2-beta-4a1e694

[21cncstudio]

Please retest the latest beta firmware that includes the network/web runtime refactor originally introduced in commit 5f4e9d8 (Refactor network and web runtime architecture).

Recommended test build:
project_aura_1.1.2-beta-bd91df0_ota_firmware.bin

This refactor changed the internal architecture of networking, MQTT, web runtime handling, OTA flow, and cross-thread interaction between the web layer, UI layer, and network task.

What changed in this refactor, in short:

• Introduced a dedicated NetworkPlane to separate network-side processing from the main/UI flow.
• Added NetworkCommandQueue to route network actions through a single task boundary.
• Added structured runtime state layers such as ConnectivityRuntime, MqttRuntimeState, WebRuntimeState, and ChartsRuntimeState.
• Reworked NetworkManager and MqttManager to fit the new ownership and polling model.
• Introduced WebUiBridge and deferred-action state to support web-to-UI operations through an explicit bridge instead of direct coupling.
• Split the old monolithic web implementation into smaller focused modules:
  • transport
  • handlers
  • pages
  • API utilities
  • response/query/multipart helpers
  • stream policy/state/writer
• Added dedicated web modules for:
  • Wi-Fi
  • MQTT
  • OTA
  • settings
  • theme
  • DAC
  • dashboard
  • charts
  • diagnostics
  • system/state/events APIs
• Added dedicated OTA state/handler flow and deferred restart support.
• Added an esp_http_server transport integration layer for the web runtime.
• Updated application wiring in main, AppInit, UiController, and related runtime/controller code to use the new architecture.
• Expanded test coverage with new native tests for web utilities, handlers, stream logic, OTA state, Wi-Fi helpers, UI bridge adapters, and related modules.

This is a foundational refactor, so older network/MQTT/OTA/web issues should be retested against the latest beta instead of assuming previous behavior still applies.

Please retest:

• device boot with saved Wi-Fi credentials
• AP portal behavior
• Wi-Fi scan / connect / save flow
• MQTT connect / disconnect / reconnect flow
• dashboard and state updates in the web UI
• settings/theme/DAC changes from the web UI
• OTA upload and reboot flow
• restart actions triggered from the web UI

If you report an issue, please include:

• firmware version
• exact reproduction steps
• whether it is consistent or intermittent
• serial log, if available

Note:

• hardware-specific GT911 / I2C instability is tracked separately and is not the main target of this refactor retest.

[21cncstudio]

If you previously reported Wi-Fi, MQTT, OTA, portal, or web runtime issues, please retest on:

project_aura_1.1.2-beta-bd91df0_ota_firmware.bin

Older issues in this area may be closed and redirected here because the underlying architecture changed significantly in 5f4e9d8.

If you still reproduce a problem, please report:

• exact firmware version
• reproduction steps
• whether it is consistent or intermittent
• serial log, if available

[tijmenvn]

Hey there,

I've been trying this new version with a few OTA upgrade attempts, I have a few questions:

1. The 1.1.2 beta binary, does it actually show 1.1.2 in the Firmware version? I have been able to successfully update it once, but it still shows 1.1.1 and no git hash for me? What flags do I enable to always show the git hash again when building locally? Half the time I am not sure if it has uploaded successfully

I've been testing with: 21d7fec

Updating has been intermittent, although as stated above, it is still hard to see what version is running, due to the hash not being available currently

I will post logs soon as well. With the enclosure in place, the serial port is unfortunately not available anymore. So will have to do some disassembling

[tijmenvn]

So when running the project_aura_1.1.2-beta-4a1e694_ota_firmware.bin binary. I've had a few times that Aura has already returned to its default view on the phycial LCD, but the web UI still thinks its uploading?

This is tested with: 4a1e694

Logs:

[I][Main] Task WDT enabled (600000 ms)
[I][OTA] Task WDT extended to 600000 ms for upload
[I][OTA] upload started (slot=6553600, expected=3706784, known=YES, timeout=300996 ms, rssi=-58 dBm)
[I][OTA] first chunk received after 13 ms (size=1702 bytes)
[I][OTA] LVGL paused during OTA transfer
[W][OTA] upload aborted (written=2677288 slot=6553600 expected=3706784 known=YES total=73024 ms first_chunk_seen=YES first_chunk=13 ms last_chunk_age=4999 ms chunks=1614 chunk[min/avg/max]=4/1658/2048 bytes client_connected=YES wifi_status=3 start_rssi_valid=YES s
[I][OTA] WiFi power-save restored after OTA (mode=1)
[I][OTA] LVGL resumed after OTA window
[I][Main] Task WDT enabled (180000 ms)
[I][OTA] Task WDT restored to 180000 ms
[I][OTA] summary success=NO written=2677288 slot=6553600 expected=3706784 known=YES total=73058 ms first_chunk_seen=YES first_chunk=13 ms transfer=68012 ms finalize=0 ms chunks=1614 chunk[min/avg/max]=4/1658/2048 bytes

[21cncstudio]

Please update to the latest beta build and retest on this one instead:

project_aura_1.1.2-beta-bd91df0_ota_firmware.bin

For the OTA issue you reported:

• the log you posted is from the older 4a1e694 build
• please retest the same OTA flow on bd91df0
• if the upload still aborts or the web UI still gets stuck in uploading state, please post the new log and mention that it was reproduced on project_aura_1.1.2-beta-bd91df0_ota_firmware.bin

[netscout2001]

@21cncstudio looks good so far. directly after flashing the boot error screen skipped again while Sen66 was starting. But after power reset i cant reproduce.
looks good so far.

[21cncstudio]

@steph54fr please retest on the latest beta build:

project_aura_1.1.2-beta-bd91df0_ota_firmware.bin

[steph54fr]

Yes, tonight or tomorrow. Le ven. 20 mars 2026 à 16:31, 21CNCStudio ***@***.***> a écrit :

…

*21cncstudio* left a comment (21cncstudio/project_aura#57) <#57 (comment)> @steph54fr <https://github.com/steph54fr> please retest on the latest beta build: project_aura_1.1.2-beta-bd91df0_ota_firmware.bin — Reply to this email directly, view it on GitHub <#57?email_source=notifications&email_token=AA5G45SLLULX4UZRHPEYM734RVP5JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMBZHEYDQMJUGQ42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4099081449>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA5G45VAXK5AD2LXVXTDSU34RVP5JAVCNFSM6AAAAACWZEBUV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOJZGA4DCNBUHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[21cncstudio]

A note for everyone retesting this area:

This was not a small fix. The refactor behind this beta was a large internal change to the network, MQTT, web runtime, OTA, and task ownership model.

Scope of the change:

• 170 files changed
• +14361 / -3745 lines changed

So this is effectively a major architecture update, not just a few targeted patches.

The goal of this work is to improve behavior especially in unstable, noisy, or heavily loaded network conditions:

• intermittent Wi-Fi
• reconnect storms
• MQTT recovery after network changes
• OTA under marginal link quality
• web/UI consistency while background network activity is happening

I’m especially interested in concrete feedback from real-world testing on unstable or loaded networks.

If you still see problems, the most useful reports are:

• exact reproduction steps
• whether it is consistent or intermittent
• what kind of network conditions were present
• serial log, if available

That kind of feedback is much more useful now than comparing behavior to older pre-refactor builds, because the underlying architecture has changed substantially.

[tijmenvn]

Much more consistent with latest project_aura_1.1.2-beta-bd91df0_ota_firmware.bin

Already succeeding OTA update (3/3 times). I noticed previously it would struggle after the device had been powered on a while. So will test again tomorrow. Nice job on the rework!

[netscout2001]

@21cncstudio With 1.1.2-beta-bd91df0 directly after flashing the boot error screen skipped again while Sen66 was starting. But after power reset i cant reproduce.

[21cncstudio]

@21cncstudio With 1.1.2-beta-bd91df0 directly after flashing the boot error screen skipped again while Sen66 was starting. But after power reset i cant reproduce.

Thanks, that is useful.

This sounds like a post-flash / warm-restart path rather than a true power-on boot path, which matches what you described.

I added a follow-up fix on main in 57b335c so boot diagnostics now stays visible not only during the SEN66 retry window, but also while SEN66 is still busy starting/resyncing.