-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Test build] Testers for new upcoming build (X-mas '24) #5174
Comments
@TD-er instead to use the latest GH Actions build, may I build by myself a Custom Build using the latest commit available now on Github? |
Sure |
OK, going to build and test! |
Test activated for from all.zip:
|
All OK here on ESP32 boards (connected on WiFi) using Custum Builds "ESP_Easy_mega_20241210_custom_ESP32_4M316k_LittleFS_ETH"!!! |
OTA update from ESP_Easy_mega_20230623_normal_ESP32s2_4M316k_CDC to ESP_Easy_mega_20241210_normal_ESP32s2_4M316k_CDC No issues so far. In the past I had often trouble setting up wifi settings with putty, now it seems working pretty good. |
No issues at all. |
ESP_Easy_mega_20240331_normal_ESP32c3_4M316k_CDC to ESP_Easy_mega_20241012_normal_ESP32c3_4M316k_CDC on ESP32-c3 super mini |
Check! |
Update from ESP_Easy_mega_20231223_climate_ESP32solo1_4M316k_LittleFS to ESP_Easy_mega_20241210_climate_ESP32solo1_4M316k_LittleFS_ETH gone wrong. A flash with ESP_Easy_mega_20241210_climate_ESP32solo1_4M316k_LittleFS_ETH.factory doesn't work ether. I will try it again tomorrow with normal build. |
Check! |
Ready to test specifically local AP restart after loss of main WiFi connection. ESP_Easy_mega_20241210_normal_ESP32c3_4M316k_LittleFS_CDC_ETH.factory.bin, doesn't restart so far |
@Dickesplumpel @chemmex |
Oh, I see, I mistakenly thought you are doing it incrementally |
and after the WiFi rewrite there will be a surprise/present made by @TD-er : the Bluetooth Low Energy support in ESPEasy :-) |
ESP_Easy_mega_20241210_collection_G_ESP8266_4M1M no issues. |
I will have a look at it later. Not sure which one of my Shelly devices is a single core though, so have to check. I know there have been issues with the recent solo1 platform builds, but I thought those were fixed by Jason2866. |
Fresh clean install with Bin-ESP32SOLO1-normal_ESP32solo1_4M316k_LittleFS_ETH-20241210_PR_5175_12260984392.factory.bin, serial says this block in a loop: rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) Same with CollectionG. |
Talked with Jason2866 and he pointed out the error I made. |
Is it only for the solo1 oder a globally change? |
I also updated to the same (newer) ESP-IDF code for other LittleFS builds, so stricktly speaking also other LittleFS builds will differ from the build I put on the web flasher page. |
No, ESP_Easy_mega_20240822_normal_ESP32solo1_4M316k_LittleFS_ETH works fine, upgrade to Bin-ESP32SOLO1-normal_ESP32solo1_4M316k_LittleFS_ETH-20241211_PR_5175_12273878227 or fresh install with factory.bin gets same result as earlier described. |
Jason also confirmed this build is failing on his Solo1. |
It looks like we have an issue with sending values with http eg. /usr/bin/curl http://esp/control?cmd=TaskValueSet,7,1,40 often results in this error. Also with IP without DNS name. |
Which build? |
ESP_Easy_mega_20241210_normal_ESP32_4M316k.bin |
Is it possible to test it on some (other) node using a LittleFS build? |
Back to ESP_Easy_mega_20240822_normal_ESP32_4M316k works fine. |
no running ESP with SPIFFS atm, but can you build one for this bin? |
Getting the json and the webinterface is also from disconnects affected. |
Also in the If you want to convert a node, you should first download a tar file via "Backup Files" on the Tools page. Then you can flash the LittleFS build, which will format the file system and should keep the WiFi credentials so it will show up connected to your network. |
The WIFI wasn't still there, but via AP I could restore the tar-file. But same issues with the unstable connection. How can I revert to the non SPIFFS from 240822? |
works with flash and AP restore. |
same with downloading backups: wget http://esp/download -P SAVE --user=xxx --password=xxx --content-disposition |
And this was working well on the August build? |
yes, when I revert it works. |
Can you disable the password to see if it makes a difference? |
It is something with the http-server, I don't think it is the password. If I use a browser the password is accepted after some tries and the download starts. |
The thing is that this will be an extra call. |
You're right, without password it works. |
Can you reproduce it ? |
OK, so there is something with multiple replies in a quick succession and that's exactly what I've also seen when fetching JS or CSS from the ESP in separate calls. |
It also affects the MQTT traffic with loss of values. |
I've just uploaded the latest GH Actions build to the web flasher
So I would like to summon the very appreciated testing crew :)
@fly74 @ghtester @chemmex @alex-kiev @iz8mbw @Wookbert @Dickesplumpel @thomastech
I had planned to also have the complete network/WiFi rewrite in this build, but it is taking quite a bit longer than expected.
This is also because of other reasons which prevent me from working on ESPEasy for hours at a time. Since the rewrite takes quite a lot of time to get 'into it' again each time I work on it, it doesn't make sense to do anything on it when I only have an hour to spare.
Anyway there have been quite a lot of fixes and other changes since the last build, so let's prepare for some X-mas build.
To make clear what the differences are between SPIFFS and LittleFS:
As can be seen, both do not differ a lot anymore and on the next build this difference might even be completely gone as I can hopefully then use pioarduino with the custom SDK flags made by Jason2866 and Staars, both from Tasmota.
Just as a reminder for those who want to upgrade from an April build:
Found issues so far:
The text was updated successfully, but these errors were encountered: