Open Ba22a opened 1 month ago
Which update are you running?
I'm almost certain this is a user issue (in the nicest way possible 😀), I'm guessing you have enabled the hidden entity that is "Everything Presence Lite Firmware"? The reason it's hidden by default is because if you have done extra steps of adding it to the ESPHome addon, then it will cause this issue because the ESPHome addon automatically adds an encryption key, where the pre-built firmwares do not have one. So updating through this entity removes the key and HA can't communicate anymore. There have been a few issues raised on this in the past, it's not a firmware issue
Makes sense, so how do I upgrade? clearing the build files and hitting install isn’t upgrading either.
On Tuesday, October 22, 2024, 10:40 pm, Everything Smart Home @.***> wrote:
Which update are you running?
I'm almost certain this is a user issue (in the nicest way possible 😀), I'm guessing you have enabled the hidden entity that is "Everything Presence Lite Firmware"? The reason it's hidden by default is because if you have done extra steps of adding it to the ESPHome addon, then it will cause this issue because the ESPHome addon automatically adds an encryption key, where the pre-built firmwares do not have one. So updating through this entity removes the key and HA can't communicate anymore. There have been a few issues raised on this in the past, it's not a firmware issue
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Going from information here any external packages only update once every 24 hours.
If you're more technically minded you can delete the appropriate subfolder from esphome manually (stored in .esphome/packages
). Of course, this is done at your own risk...
Perfect, thanks. Everyday is a school day. 24hr pointer is very useful. Thanks again. All sorted.
On Wednesday, October 23, 2024, 8:55 am, scotttimmins @.***> wrote:
Going from information here any external packages only update once every 24 hours.
If you're more technically minded you can delete the appropriate subfolder from esphome manually (stored in .esphome/packages). Of course, this is done at your own risk...
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
@scotttimmins that's good to know, as finally I was able to update mine - I just wish I knew where the .esphome/packages folder was as I cannot find it anywhere via SSH on my OVA based HA server.
@scotttimmins that's good to know, as finally I was able to update mine - I just wish I knew where the .esphome/packages folder was as I cannot find it anywhere via SSH on my OVA based HA server.
ApolloAutomation.AIR-1:
url: https://github.com/ApolloAutomation/AIR-1
ref: main
files: [Integrations/ESPHome/AIR-1.yaml]
refresh: 1min```
you can do something like this and get it down to 1min.
I run a docker esphome image and .esphome
is in the config folder for me.
The .
prefix can hide it in default listings but an ls - a
shows it.
I run a docker esphome image and
.esphome
is in the config folder for me. The.
prefix can hide it in default listings but anls - a
shows it.
Nope
That's your Home Assistant config folder - I run ESPHome as a separate container.
Maybe someone who runs it as an addon could give some guidance on where to look?
That's your Home Assistant config folder - I run ESPHome as a separate container.
Maybe someone who runs it as an addon could give some guidance on where to look?
I have ESPHome installed as an HA integration and as an HA add-on
I ran the update but the device becomes unresponsive after the update finishes.
it is still available in ESPHome but no readings from the device.
if I choose to install from ESPHome it springs back to live but is running 1.1.1.
I am using everything-presence-lite-ha-co2.yaml@main as I have the co2 sensor.
thanks Barry