yes please, you can re-open the issue and we’ll go from there.
But can you first install the latest 1.5.1 or 1.5.2 version? The fix may already be available.
I don’t seem to have permission to reopen the 10th ticket. But added a comment.
The new version does have a different behavior.
Nice, just installed 2026.4.2, and all devices got updated just fine. Turned the automatic option back on! really good, thanks! Nice integration!!!
1 Like
Thanks, really appreciate it! Glad it’s useful.
Hi @Krivatri,
I was on a holiday and just now found the time to check it again. My problem ist, that I have ESPs that mostly sleep, and that are under development, and I do want to push new features with new firmware, where ESP is not updated in the meantime.
So this is what I see when I did the Update on my S03 manually:
Before is also had the older 2026.1.3 → 2026.4.4 like kpro1 in the line above. When it came up, I got the checkbox for updating, which I checked and than klicked on the “UPDATE” all button above.
But after 5 minutes, there was no update shown. I pressed cancel, it “did” something, but the end was, that I had to reboot HomeAssistant. As I seemed the ESP was not having a working firmware version, I than did the update with ESPHome and it worked as expected.
After this, I cannot update the ESP any more with ESPHome Update Manager, as I cannot klick the checkbox any more.
So her emy problem.
I need a way to tell an ESP even if it sleeps, that I do want to force an Update next time, when it awakes. But if my ESP sleeps, I cannot check the box (which is needed, because in my case it is hard to catch the timing, when the ESP goes online, and even if it is online only for a very short time. So checking a box is nearly im possible. But I cannot do this, as there is no “force update” checkbox to check if the ESP is offline
and even if I get the timing, I cannot “just” update a new firmware feature, if the S03 is up to date with the newst ESPHome firmware:
My question: I ESPHome the wrong tool for my updates, as it solves a different problem? Or am I doing anything wrong?
many thanks for any help
Juergen
P.S.: ESPHome Update Manager can savely assume, that if I check “force” update, that this is tested and will work, so no extra tests needed there. Just like rm -rf ./* as root 
where you also know what you do.
Hi, I’m not sure if you’ve checked the README, but there are several ways to install or update firmware, even when no ESPHome firmware update is available, and even for devices that are rarely online.
There is also an important difference between updating and installing:
- Updating means installing a new ESPHome firmware version when an update is available.
- Installing means uploading a change made in the YAML file to the device.
If there’s no ESPHome firmware update available, there will be no checkbox, since there is no update to install.
If you want to install a modified YAML to your device when no update is available, you’ll need to use the “force install” option. Then the checkboxes will be available for all online devices, this way you can install the new code to your device.
Then the part for your case:
If you want to install a modified YAML to an offline device, you’ll need to use the project component in your YAML. When you bump the project version, the new YAML will be uploaded to your device automatically once it comes online again. Depending on the machine you’re compiling on and the size of your YAML, it can take some time to compile and upload, so make sure to leave the device online long enough — this can take 10 minutes or more.
(When using the project component for the first time on your device, you’ll need to upload it manually for the integration to register it)
Another way to force-install to an offline device is by using the service provided by the integration. This service can then be run through an automation.
For now, the panel does not show the project version, but I’m planning on adding this option in the next release.
(You can also check the logs for more details on the update/force install, there you’ll find the firmware and project versions)
Hi @Krivatri,
I can confirm it works now for me. Except my general problem ist, that most of the time, my ESP are in deepsleep, so offline. The marked buttons are not listet than:
So what I would need is to have the change to select and force force update even if all ESPs are asleep.
So I can test manually the final version, and than check all other ESPs that should get this version.
So my problem ist, that I cannot tell “upfront” that things should happen, but I have to wait for each and every ESP when it is online and than do the update.
I hoped that I could mark them all for “Install”, press “force update”; and than the ESP Update Manager “waits” until they are not asleep any more, and than updates them when they go online once in a while.
When the ESPs awake, I can send them the minutes how long they should be awake as they get an update, so this problem is solved. But it is relatively unpredictable when they go online.
Many thanks for all you help.
Juergen
ok, if I understand correctly, you need to be able to select offline devices in the panel so when they come online, they get a force install?
Yes, exactly. Checkmark devices if they are offline (or online) that than get a force install. I could even use, if I could call a service in your esphome update, that I can call within an automation. The service would get the ESP I want to update, and I call it, if the ESP goes online, if this makes things more useful.
I think what you need is in release 1.7.0
Please check Pending force install for offline devices and Deep sleep devices
There is also an automation that goes with it to command the devices to deep sleep after a force install
Hi @Krivatri,
I now got it to work, thanks a lot for your effords. I assume there is one issue: I noticed the following behaviour: If there is an ESPHome Update coming in, while I have a forced Update due to a new feature in the Yaml and the ESPHome Update comes in while the ESP is sleeping, than it seems the ESPHome Update is done instead of the "Forced feature" update. It is not a real issue, if you know this. And again, I am not 100% sure, as I at the moment have no clue how to go one version back in ESPHome, to test it again.
IMHO if this is the case, the Update Manager should basically do nothing, inform the user with a warning, and tell, that this is a two folded step. Reason: it might be the case, that the new ESP Version needs a "clean files" before it compiles again with the YAML, ot it does not compile at all.
many thanks for everything
Juergen
Can you give some more details? you selected the offline device for pending force install and then there was an esphome firmware update available, did the integration tried to update the device while offline or when it came online?
Anyway, when doing a yaml install if the builder was updated to a newer version, the new firmware will automatically be installed also, when doing a firmware update, the modified yaml will also be installed automatically, that's native behavior of ESPHome, nothing I can do about that.
But I think I understand what you're asking, when both (force install and update) are true, do nothing?
in the meantime, I had the chance to test your case: the offline device does not try to update to a newer version when offline. When the device comes online, the force install has priority over the firmware update and a force install is started automatically as this is the main goal of the integration. For me everything is working as expected.
Hi @Krivatri,
Can you give me a hint, how I can go back one ESPHome Version, so I can test again. I know there was "something", but I could not reproduce it. So "don't worry".
On another thing.
Is there a way to support you?
thank you
all the best
Juergen
The way I test the integration is by installing an ESPHome builder on my desktop (via cmd) with the version of choice, this way you can easily downgrade/upgrade the builder version and compile firmware bin files accordingly. you can then upload the bin file via the (test)device web server.
There is no need to support me, this is my way to give back to the community.
1 Like
Hi,
One thing I forgot: At the beginning, I was really confused, that the greep Button for "Force Install" and "Update" where switching. I checked the ESP for Install click the button and nothing happened. Maybe a dropdown would be better as a UI.
thank you
Juergen
I see what you mean, that's why I've used different colors, but maybe it's not enough.
But I already have a solution in my head.
Was really a bummer the first time, I used it, but maybe I am dumb 
End even now I sometimes klick on the green button. I think one is triggered for klicking buttons
Nothing to do immediately. Your System really saved me a lot of headache, as I do have to do remote Updates on ESPs that are only updatable OTA, and are "mostly" sleeping. Thank you for all the time you put into my suggestions.
Juergen
no problem, the "fix" is almost ready for release 
I appreciate pointing these little things out, it's not always easy to see things clearly when you're right in the middle of it...
1 Like
release v1.7.2 is available, please check it out, hope it makes more sense now.
I like it. Esspecially also that there is now ESPHome and YALM version shown. Mabe a space befpre the (YAML)
1 Like