This helped with showing online in esphome, but HA still sees it unavailable because it constantly flips between online and offline…
The device itself worked until the latest update and is still pingable on both mDNS and IP and I do use static IP on all my nodes
I can also still update it in esphome, but it refuses to get logs. Sometimes with just time out and other times socket errors.
Is there a way to downgrade esphome so I can revert back to a working version for this particular node? Because this is pretty frustrating and it is only this one that fails now after the update.
nevermind about the downgrade of ESPHome, I just restored the old version from the backup.
But it seems to have something to do with this latest particular version (2024.5.0) because after the rollback and flashing the device again, it straigh on came back online again.
I’ve had two devices that had problems after updating to 2024.5.0.
One of them was an assistant/smart speaker that refused to play mp3s until I changed the esp-idf framework it was using from recommended to 4.4.6 (undoing the change of recommended version to 4.4.7 that came olong with 2024.5.0)
The other seems more similar to what you’ve described… its a cb3s based IR ‘blaster’ that was refusing to stay connected to both wifi and API after udpating.
I found that some kind of yaml size limitation was reduced with the udpate, and it behaved just fine after I removed some of the IR remote buttons I had defined.
How easy it is’ll depend on the yaml you’re using, but is it possible to cut a chunk out of the devices yaml and see what it does? Just as a test, it might show something similar. Be sure to keep a copy of your original yaml somehow though, so you can put it all back.
it is a pretty big yaml file, but that is due to the fact it has both a ledstrip and a LD2410 connected, of which the latter really needs to ton of stuff configured, but I could indeed check what I can remove from the yaml and retry again. But it seems to me this is something they need to fix in ESPHome itself instead of us deleting stuff in order to make it work normally again
I don’t mean to suggest permanently removing functionality, just trying it as a quick test.
If you find similar, it would seem to be something thats changed for the worse and undoing/redoing whatever it is might make most sense.
It might be a way to narrow it down a little.
That is pretty nice! maybe I should look into how to do this too until it is solved. But wouldn’t some nodes keep saying it has updates ready to install? or can you specify which node uses which version?
What I do now is to turn off the firmware update entity. I will update the existing and working devices only as needed.
In the Updates section of Settings, click on the device icon.
Click on the gear icon:
From here, disable the firmware entity. Now you will never see the update notification.
yeah they pointed to another topic about this and did nothing in both mine or the other topic so far…
I do agree with many in here that it is concerning that so many people are talking about this issue and to see no response at all or any mentioning about it in the updates from the devs
I am having this issue with the latest ESP Home 2024.6.6 Any one else? I have 5 units all with the latest firmware. They all report to Home Assistant and I can see their logs. But 3 of them show as offline
Same issue, all of my ESP32 devices show offline in esphome but logs can be updated and OTA updates work fine. Sensor data is sent fine to home assistant as well.
On latest home assistant 2024.7.0 and ESP home 2024.6.6.
I am having this issue when i try to update to ESPHome 2024.6.6
HARDWARE: ESP8266 80MHz, 80KB RAM, 4MB Flash
Library Manager: Installing ShiftRegister74HC595 @ 1.2
Warning! Could not find the package with 'ShiftRegister74HC595 @ 1.2' requirements for your system 'linux_aarch64'
The only thing and you and the the thread starter in 2021 had in common was the use of the same hardware component (shift register). Maybe you even use a esp8266 too - we don’t know as you didn’t provide the basics (yaml etc.) needed to get a qualified answer (beside posting at the wrong location)
