Which Bin for flashing ESP32-C3 ETH01 evo

[Ath]

H Ton,
There was no need for that action. The release seems oke to me. The board is running for over 3 days and serves the needed info from the modbus meter over mqtt to Domoticz and Node-Red.

That was a change that was on the TODO list anyway, so no better time to start it when someone can make good use of it

I had some trouble with the right syntax in the script of the rule. But that was my mistake. I missed the square bracket at the end in this sentence..

Code: Select all

Let,1,([SDM120_Goodwe#W])

Took some time to figure that out...

You don't need the round braces there, I think they where the attribute of confusion

This part of the project is oké. Next step is rearrange the flow in Node-Red.

But I will upgrade and let you know the results.

Great

[PieterS]

Thnx Gijs for the reminder. Glad I did that before uploading the this release.. Because after uploading I waited over 5 minutes for a restart... At last a disconnected the power and there (s)he goes...

But a bit disappointed about the colors in the editor of the rules



Builddate is really uptodate. So a bit confused.

Bytheway: I was a bit worrying about the name of the download. It has the term "Climate" in the name: (Bin-ESP32-climate_ESP32_4M316k-20240520_PR_5057_9160400873) But when I uploaded there was "Custom" in the name. And I need the Energypack. But I took the risk..

[Ath]

You're still on the original build, you should have a binary dated today, and downloaded from the link I shared above, there is now also an Energy LittleFS build for the ESP32-C3, this download: https://github.com/letscontrolit/ESPEas ... 1519579985

Edit: As said, the Custom build doesn't include Easy Color Code, the Energy (or Climate, but that won't work for you) build does.

[PieterS]

Now I am sure I have the right version of the build you offer to me.

Send you this screenshot before I press on Update Firmware.



I waited for 15 minutes but the browser does not refresh.. After a cold reset I still remain in the old version...

So I guess I have to reset to factorysettings and try a clean install?

[Ath]

Now I am sure I have the right version of the build you offer to me.

Send you this screenshot before I press on Update Firmware.



I waited for 15 minutes but the browser does not refresh.. After a cold reset I still remain in the old version...

Strange, maybe it has to do with the Ethernet connection.
Can you connect via WiFi to the unit, and retry the update?

So I guess I have to reset to factorysettings and try a clean install?

Better not, there seems to be an issue with initializing a fresh file system with the currently active framework package. We're looking into that.
Upgrading an existing install seems to work just fine.

[TD-er]

Hmm yesterday I also had issues performing OTA update on some nodes here to test.
I finally managed to do the update after I switched the node to another access point.
Absolutely no idea why the OTA update was stalling exactly like how you described; takes ages, only after a power cycle the unit boots the previous build.

As Ton mentioned, today we found out there might be some issue regarding bootloops and we're not yet sure what really might cause this so better leave it running the current build for now.

[PieterS]

Thnx gentlemen. I leave this build for now.
I updatrd through ethernet lan cable. So no accesspoint could be a cause.

Lot of success with troubleshooting your issues.

[PieterS]

Consider to buy another ESP32-C3 with ethernet and the AC energyplugin to replace a ESP8266 which has a very unstable connection.
Would it be possible to flash that new device according to the problems that were mentioned a few weeks ago about updating?

[TD-er]

Yep, those are now dealt with.
Later this weekend, I will upload the latest build to https://td-er.nl/ESPEasy/latest/
However, I think the build already present there is working fine too.

[PieterS]

Ok, thnx for confirmation. So I can order another EVO

[PieterS]

Hallo,

Back again. Still very satisfied with this software for reading already 5 Eastron meters through modbus.. But since a week there were troubles with the 8266-board. High load (99.86), slow, sometimes no ping.
Long story short: decided to replace the 8266 to an ESP32-C3 which I had as a spare.
Board was flashed with Build: ESP_Easy_mega_20240419_custom_ESP32c3_4M316k_LittleFS_CDC_ETH Apr 19 2024 and worked out of the box...

Now my question(s):

I tried to update by OTA to the latest build ESP_Easy_mega_20241222_energy_ESP32c3_4M316k_LittleFS_CDC_ETH.bin but I did not succeed. The update did not end with any failure or error... After waiting for at least 10 minutes I do an cold reboot and than I read the same version in the bottom of the screen...

That makes it maybe difficult for the next step:
I want to swap from the ethernet to WIFI, because of lack of ports on the switch in that area.. For now I pulled a plug out to get the ESP working. But the wireless router is 2 feet away..

So the next quistion:
Is this version oké for a change in configuration to WIFI? In menu Hardware I can chose as Preferred network medium: WIFI and there is need for a reboot. But what is next?? Does it pick up the settings from menu Config straight away? I cannot find info how to configure in https://espeasy.readthedocs.io/en/lates ... l#esp32-s3
Lots of doublts because there is another build: ESP_Easy_mega_20241222_energy_ESP32c3_4M316k_CDC.bin too. Maybe I need that version for my needs? What is the difference between those versions?

Any advice or help appreciated.
Thnx in advance.

[Ath]

What is the difference between those versions?

This page shows what's included in each build: https://espeasy.readthedocs.io/en/lates ... lugin.html (Custom is not listed there, though there is a 'default' set but that may change over time, it's actually a user-defined set of plugins and features)

[TD-er]

OTA update may sometimes fail.
What I do myself is to disable temporarily the ESPEasy p2p.
On the Tools->Advanced page, you can change the UDP port for p2p to 0.
Then update the firmware and when done, set it back to the port you're now using (likely port 8266)

You can also look into the latest build here: https://td-er.nl/ESPEasy/latest/

N.B. when WiFi is very unstable, you may also want to enter this command to wipe the current RF calibration:

Code: Select all

EraseSDKwifi

[PieterS]

Thnx Gijs for your advice. I changed P2P-port and tried to update through OTA again. But did not succeed. I leave the update for now.

The good news: change the setting from Ethernet to Wifi went flawless. So no need to upgrade to another switch for now. I do not expect unstable connection as the ESP is located in the same cabinet als the router. The Draytek says RSSI: -33 dBm. But keep that option in mind.

[TD-er]

Keep in mind that RSSI is not the only value that determines a good WiFi connection.
For example, if the signal is too strong, it may show a similar effect like "distortion" in audio.
Sounds great for an electric guitar, but for signal processing it isn't that nice to have.

[PieterS]

I let you know if I have troubles.. No other options than back to Ethernet..

[TD-er]

Well you can reduce WiFi TX power, if needed.
But as long as it is working, let it work