Upgrade experiences release 2.4.0

[avandorp]

A discussion to bundle feedback from users upgrading to 2.4.0.

[avandorp]

Upgrading my ESP32C3 via OTA didn't work (as sometimes with former releases), neither directly which pulls the image from GitHub, nor downloading the image locally and using the "Select firmware for upgrade" button. (Edit: Error -100, indicating not enough space). Flashing via USB with flash.sh upgrade /dev/ttyACM0 didn't work, the device didn't connect to the WiFi afterwards, flashing with flash.sh flash /dev/ttyACM0 worked after the second attempt. Configuration was still correct, thanks! Historic measures were lost (not a problem for me).

Thanks for the update. I will retry OTA again with the next release. With the new partitioning this might work again.

One thing (which might be specific to my device) that's always happening when flashing via USB: The serial usb interface comes up and then disconnects approximately one second later. So my way to upgrade is: Have a "dmesg --follow" console open, another one ready with the upgrade command, insert the USB cable, wait for "new USB device", hit enter key.

[avandorp]

The device was 19 hours offline, unfortunately it's difficult to figure out why. Auto reboots certainly aren't easy.

[avandorp]

Upgrade to 2.4.3 via link without issues. Update was automatically advertised in home assistant.

[ArnieO]

Sounds good - and that's what we expected to hear!

[avandorp]

With 2.4.2 and 2.4.3 I've had now four occurrences, where the amsreader didn't deliver any MQTT messages. Debugging via Telnet gives entries like

(D) NOT Ready to update (internal clock 11:21:19 UTC, meter clock: 00:00:00, list type 3, est: 0)
(W) MQTT connection not available, double blink
(E) Failed to connect to MQTT: -3

Disabling debugging rebooted the device and made MQTT available again. I'm not sure, whether something has changed with regards to MQTT. I use TLS and a host name (so both time and DNS resolution have to work), that might make my setup more prone to such errors.
EDIT: Ah, that could be #918

[ArnieO]

I confirm that this is indeed #918

[ElMyggo]

I just hit the button to upgrade on my ESP-WROOM-32 and i get same error code -100
I havent try anything else, maybe tomorrow

[ArnieO]

Thank you for your feedback!

[gskjold]

This is due to lack of space to perform the upgrade. You need to flash via USB this time, but should be able to continue to the next versions with OTA

[ElMyggo]

I flash to 2.4.0 with USB and lost some settings but cant remember excactly what... but yesterday i update to 2.4.1 and its working very nice with status and so on.

[dbeinder]

Here is a build for ESP32-C3 and classic ESP32 with HA/Domo/KMP removed to fit the old partition size.
You can use it to repartition before upgrading to the official 2.4.0:
repartition-build.zip (Diff: dbeinder@1adcaaf)

[torkelmj]

Howdy.

Just upgraded Pow-U+ from v. 2.3.9 to 2.4.0 (esp32s2). Effortless when following the published instructions.

However, I've run into an issue with the "future energy prices" presentation. Went to the ENTSO-E webside, generated a new access token. AMS reader immediately reported wrong API key (as expected). Upgraded API key in AMS reader, then back to "no data" as shown in the attachment. Any suggestions?

[torkelmj]

Whoops. Coincidence ...

From ENTSO-E:

"Dear Transparency Platform users,

Due to technical issues Energy Prices 12.1.D are not available for 20th January in most of the areas.
As soon as the issues are resolved Energy Prices for 20th January will be published on TP.

We apologize for the inconvenience.

Kind regards,
Transparency Platform team"

[ArnieO]

We have had frequent issues with direct API calls to ENTSO-E, which is why we have implemented an intermediate server that also has backup sources for price data.

The recommended setting is now to read from our intermediate server in stead of directly from ENTSO-E.
You do that by activating "Enable price fetch" with the API key field empty:

The price data source will be indicated in the upper right corner of the price graph. Right now, my indication is this (it was not Entso-E this morning, so proably now some other source for today and Entso-E for tomorrow):

[torkelmj]

Darn. As I already had an API key filled in, I didn't see the "optional" text. Removing the API-key --> perfect result. Thanks a lot. This thing just keeps getting better by each software release.

[Belaial]

Just wanted to add that I just now upgraded my ESP8266-model to 2.4.0, all worked just fine.

EDIT

Noticed now I lost my price configuration, but also upgraded to 2.4.1 right after so might be either 2.4.0 or 2.4.1 that caused that.

EDIT2

Price configuration was not restored via restoring config file so I just manually added it again, no big deal but reporting it anyway.

[ArnieO]

Ping @gskjold

[Belaial]

If it matters the 2.4.0 upgrade was done by uploading the file manually (since 2.4.1 was out and I wanted to upgrade the "re-partition" upgrade first)

I then upgraded to 2.4.1 via the notification in GUI.