Skip to content
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

Updates fail with "Error binary size: Unknown error from ESP" #114

Open
rmaeder opened this issue Dec 21, 2024 · 1 comment
Open

Updates fail with "Error binary size: Unknown error from ESP" #114

rmaeder opened this issue Dec 21, 2024 · 1 comment

Comments

@rmaeder
Copy link

rmaeder commented Dec 21, 2024

ever since ESPHOME 2025.12.0, attempts to update my Athom smart Plugs V2 fail with these messages;

INFO ESPHome 2024.12.1
INFO Reading configuration /config/esphome/athom-smart-plug-v2-ecXXXX.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing athom-smart-plug-v2-ecXXXX (board: esp8285; framework: arduino; platform: platformio/[email protected])
--------------------------------------------------------------------------------
HARDWARE: ESP8266 80MHz, 80KB RAM, 1MB Flash
Dependency Graph
|-- ESPAsyncTCP-esphome @ 2.0.0
|-- ESPAsyncWebServer-esphome @ 3.2.2
|-- DNSServer @ 1.1.1
|-- ESP8266WiFi @ 1.0
|-- ESP8266mDNS @ 1.2
|-- noise-c @ 0.1.6
|-- ArduinoJson @ 6.18.5
RAM:   [=====     ]  46.5% (used 38056 bytes from 81920 bytes)
Flash: [======    ]  58.1% (used 595041 bytes from 1023984 bytes)
========================= [SUCCESS] Took 2.98 seconds =========================
INFO Successfully compiled program.
INFO Connecting to 192.168.XXX.YYY port 8266...
INFO Connected to 192.168.XXX.YYY
INFO Uploading /data/build/athom-smart-plug-v2-ecXXXX/.pioenvs/athom-smart-plug-v2-ecXXXX/firmware.bin (599200 bytes)
INFO Compressed to 408955 bytes
ERROR Error binary size: Unknown error from ESP
@rmaeder
Copy link
Author

rmaeder commented Dec 24, 2024

When I do a "Clean build files" first, the update works.
Immediately doing a second update without cleaning, fails as above.
So, perhaps this is a problem with the dependencies and there is some junk lying around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant