-
Notifications
You must be signed in to change notification settings - Fork 34
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
OTA stops working after upgrade to 2024.5.0 #5804
Comments
Same here for version 2024.5.1. In this case a Athom Smartplug v1.
|
Same here for Athom Presence sensor
|
I have both the Athom smart plug x5 and the Athom presence sensor x10 - ALL fail with this issue. Never used to happen before 2024.5.0. Maybe the size of the compiled file has increased? I wish there was a way to EXCLUDE devices from updates - I see NO reason at all to update them. It takes ages to compile for each device, despite them being the same. There has got to be a better way. |
Same here. I'll have to skip the update for the Athom devices I have. It's been a pain to try to figure out how I can update, even plugging in via USB isn't working. |
You don't NEED to update. For now, I rolled back to 2024.4.x and restarted/re-flashed all of my devices. I skipped the 2024.5 release. |
Try the following - this has worked for me:
|
Pretty annoyingly, though, I have to do this workaround every single time I want to upgrade my sensor. |
2024.5.4 fixes this problem for me on the 6 devices that had the issue :) |
Yes, there was an accidental size increase that is now fixed. |
The problem
Since the upgrade to the latest ESPHome I suddenly cannot flash one of my Shelly devices OTA anymore. It has a 8266 chip with 1MB of flash. I see
Which version of ESPHome has the issue?
2024.5.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
latest
What platform are you using?
ESP8266
Board
shelly
Component causing the issue
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: