Skip to content

ESP Rx WiFi Update#386

Open
jlpoltrack wants to merge 3 commits intoolliw42:mainfrom
jlpoltrack:esp8266-rx-ota
Open

ESP Rx WiFi Update#386
jlpoltrack wants to merge 3 commits intoolliw42:mainfrom
jlpoltrack:esp8266-rx-ota

Conversation

@jlpoltrack
Copy link
Collaborator

'Simple' WiFi updater for ESP receivers. Starts after 60 seconds or CLI command.

Screenshot 2026-01-04 at 2 17 01 PM

@tmcadam
Copy link
Collaborator

tmcadam commented Jan 5, 2026

This is awesome!

@olliw42
Copy link
Owner

olliw42 commented Jan 25, 2026

I guess it is high time to - at some point - discuss what firmware update modes we eventually want to support. Currently it feels like that just implement every single possible, even if only remotely used, update method.
IMHO this is not user friendliness but the opposite of that. The average user wants to just do a simple thing, upgrading the firmware, but has first to do a substantial research session to even only understand which of the methods they like. IMHO the typical appearance of OS projects. And I don't like that ;)

Having said this: I'm not against Wifi OTA update for the ESP receivers.
BUT: I think we should only EITHER offer wifi ota OR fc passthrough, certainly not both.
Wifi OTA would have some advantages (if it would be fully supported by the web flasher) over the fc passthrough, since it is admittedly just easier and moreover we currently see also bloating of these passthru procedures (given the increase of fc platforms).

Anyway. This code is a very good first attempt, but IMHO needs to be structured way better. E.g., it needs to be triggerable by "all sorts" of means, CLI, Lua, possibly OLed. MSP? I'm not sure one also would need some trigger methods on Rx side.

That is, I think:

  • we first want to decide what we really want firmware upgrade wise.
  • if then still relevant, we then want to write down the possible triggers we want/need. Doing then the code based on this PR should be not so difficult.

I guess the discussion parts we rather want to do in the discord channel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants