Hi, I'm starting to move all my ESP8266/WemosD1 to ESPEasy and I must admit it makes life easier than before as I can deal with all of them remotely.
Only one feature I used to have implemented I miss.
I used to have all my ESP listen to a global MQTT topic for general purpouses and one handy one was to lauch a new firmware update to all units using OTA.
As far as I understood with ESPEasy I need to manually upload a new firmware to each unit individually, and with dozens of them in multiple setup I do manage it makes this very time spending.
Any clue if this can be somehow implemented in current version or it shoudl be part of future release requests?
OTA deployment
Moderators: grovkillen, Stuntteam, TD-er
-
- Normal user
- Posts: 497
- Joined: 04 Oct 2016, 23:16
OTA deployment
My TINDIE Store where you can find all ESP8266 boards I manufacture --> https://www.tindie.com/stores/GiovanniCas/
My Wiki Project page with self-made PCB/devices --> https://www.letscontrolit.com/wiki/inde ... :Papperone
My Wiki Project page with self-made PCB/devices --> https://www.letscontrolit.com/wiki/inde ... :Papperone
-
- Normal user
- Posts: 161
- Joined: 31 Aug 2016, 06:33
- Location: Germany - NRW
Re: OTA deployment
Hi !
Since the devs wan´t to be able to support the old 512kb modules I think there is no room for such a feature.
Read here: http://www.esp8266.nu/forum/viewtopic.php?f=6&t=2107
But hey, take the sources from Github, add the OTA feature, compile and flash.
I think taht should not be so complicated
Since the devs wan´t to be able to support the old 512kb modules I think there is no room for such a feature.
Read here: http://www.esp8266.nu/forum/viewtopic.php?f=6&t=2107
But hey, take the sources from Github, add the OTA feature, compile and flash.
I think taht should not be so complicated

regards
Dominik
Dominik
-
- Normal user
- Posts: 497
- Joined: 04 Oct 2016, 23:16
Re: OTA deployment
of course it's not... My idea is to do it of course as I already have a similar function in my previous sketches!
As soon as I will have some free time I'll study how to proeprly implement it in EASPEasy; about old 512Kb module I believe it's really limiting to keep on supporting them (ESP01 with 2 GPIOs what benefits you can have with such a big featured firmware with dozens of devices supported as anyhow you are limited to handle a couple?).
I think it's more logical to freeze last release stable that supports 512Kb modules and move ahead for minimum 1Mb for all future releases. Does it make sense?
As soon as I will have some free time I'll study how to proeprly implement it in EASPEasy; about old 512Kb module I believe it's really limiting to keep on supporting them (ESP01 with 2 GPIOs what benefits you can have with such a big featured firmware with dozens of devices supported as anyhow you are limited to handle a couple?).
I think it's more logical to freeze last release stable that supports 512Kb modules and move ahead for minimum 1Mb for all future releases. Does it make sense?
My TINDIE Store where you can find all ESP8266 boards I manufacture --> https://www.tindie.com/stores/GiovanniCas/
My Wiki Project page with self-made PCB/devices --> https://www.letscontrolit.com/wiki/inde ... :Papperone
My Wiki Project page with self-made PCB/devices --> https://www.letscontrolit.com/wiki/inde ... :Papperone
Who is online
Users browsing this forum: Ahrefs [Bot], Bing [Bot] and 14 guests