Changes reverted

ESPHome
1

has anyone ever had the issue that the changes got reverted after a restart?

So I have a sonoff ns panel, esp32.
then I build, and publish wireless.

INFO Successfully compiled program.
INFO Resolving IP address of switch-kamer-achter.local
INFO  -> 192.168.180.134
INFO Uploading /data/build/switch-kamer-achter/.pioenvs/switch-kamer-achter/firmware.bin (1174656 bytes)
Uploading: [============================================================] 100% Done...


INFO Waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from switch-kamer-achter.local using esphome API
INFO Successfully connected to switch-kamer-achter.local
[23:24:39][I][app:102]: ESPHome version 2023.10.6 compiled on Nov 13 2023, 23:21:50
[23:24:39][C][wifi:546]: WiFi:
[23:24:39][C][wifi:382]:   Local MAC: 80:64:6F:C4:CE:10

or download file
Modern, says “Update Failed: Wrong Magic Byte”
Lagacy works
all settings are changed.
but after a restart
I suddenly have the old config back,

image
image691×47 2.32 KB

also esphome 2023.10.3 instead of esphome 2023.10.6

has anyone ever had this issue? Or do I need so serial flash?

2

I currently have the same problem. If I give the legacy or the new format in the web-UI, it fails with the message
Update Failed: Wrong Magic Byte

If I do it wirelessly, I get this error message:

Successfully created esp32 image.
esp32_create_combined_bin([".pioenvs/nspanel2/firmware.bin"], [".pioenvs/nspanel2/firmware.elf"])
Wrote 0xefd40 bytes to file /data/build/nspanel2/.pioenvs/nspanel2/firmware-factory.bin, ready to flash to offset 0x0
======================== [SUCCESS] Took 170.58 seconds ========================
INFO Successfully compiled program.
INFO Resolving IP address of nspanel2.local
INFO  -> 192.168.188.69
INFO Uploading /data/build/nspanel2/.pioenvs/nspanel2/firmware.bin (916800 bytes)
ERROR Error auth result: Error: Authentication invalid. Is the password correct?

I would like not to re-open the NSPanel in order to access the serial interface, does anybody have a -bin with the correct magic byte?

KR,
Ch.

3

I was able to fix my issue without opening the device.

My previous config was build based on the arduino framework and the new one which I couldn’t use was based on esp-idf for 2 other nspanels and 3 different esp32 devices this OTA migration to another framework as not an issue.

but for some reason it was(is) for this specific nspanel.

So I decided to create a new build based on arduino and the issue was gone.

Don’t know if I can migrate to esp-idf having the latest esphome firmware now, but moving back to arduino fixed the issue.

4

THX for the reply!

I am quite new to this esphome-ecosystem. Maybe you can give me a hint what you mean with “new build based on arduino”, do you have a kind of how-to?

KR,
Christof

5

the short answer is it’s in your config

arduino is default.
not sure if you use external components, but it can be that such a component overwrites your default.

while building you will see your framework

image
image850×187 6.04 KB

so I would suggest try the other flatform as you are using right now.

also check if your esphome is up to date(first line in my screenshot). At the moment of writing esphome doesn’t ask me for legacy or modern format anymore, not sure why but I noticed this change a couple of weeks ago.

6

As I understood it you cannot make that change wirelessly because the esp-idf framework uses different partitioning compared to arduino. So you can change from one to the other (I did), but you need to do so using a wired connection.

7

you should’t need to,
esp-idf works on arduino partioning and the other way around. as mentioned it failed only for one of my devices.
it’s better to serial flash, but not a must.