ESPHOME 2023.10.5(and now 10.6) update fail for Bulb #44
Comments
|
It's working fine for me. Can you run the update from the dashboard and let me know what error is showing up in the logs? |
|
"run the update from teh dashboard" - which dashboard are you referring to? Click on 'visit' shows that only 10.4 is available: The latest on Github is still only 1.92 (2023.9.1) ! When I try to do the upgrade from HAOS notification area, I get the same message as in opening comment. |
|
ESPHOME 10.6 was just realeased this morning - same issue. |
bert269
changed the title
|
This is the log from HAOS: [546621103552] Error updating kitchen-lamp.yaml via OTA; Try again in ESPHome dashboard for more information. Also, during the update process, when I 'visit' the bulb from ESPHOME, I do see the following on the web page: But the firmware does not get updated to the device. It is still stuck on 10.4. |
|
Were these previously updated fine through HA or the dashboard? If the devices aren't showing up as online in the dashboard then that is probably the issues. Since the ESPHome dashboard thinks the devices are up to date it is not showing the update option in that view. If you press the three dots you can click "install" and its the same thing. You might need to point the yaml configs to the devices' IP addresses using use_address or set a manual IP. |
|
Yes. All updated through HA - that's how I got it to 10.4.
None of my working ESP devices ever shows up as online in ESPHOME, but the
work just fine. Thats not the problem.
Pressing the three dots, install, wirelessly has the same effect - does not
update this bulb.
My devices have static ips in my router table. I will try to add it into
the yaml code for this bulb
Thanks.
…On Fri, Nov 3, 2023, 16:18 Brian Kaufman ***@***.***> wrote:
Were these previously updated fine through HA or the dashboard? If the
devices aren't showing up as online in the dashboard then that is probably
the issues. Since the ESPHome dashboard thinks the devices are up to date
it is not showing the update option in that view. If you press the three
dots you can click "install" and its the same thing.
You might need to point the yaml configs to the devices' IP addresses
using use_address or set a manual IP.
—
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEN5KACBPOQPCSNBLWQEH4TYCVUTVAVCNFSM6AAAAAA6Z3HK3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGE3TGOJXG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This bulb already had manual IP address assigned in yaml code.
Now I get this memory error trying to compile and install the code.
…On Fri, Nov 3, 2023, 16:18 Brian Kaufman ***@***.***> wrote:
Were these previously updated fine through HA or the dashboard? If the
devices aren't showing up as online in the dashboard then that is probably
the issues. Since the ESPHome dashboard thinks the devices are up to date
it is not showing the update option in that view. If you press the three
dots you can click "install" and its the same thing.
You might need to point the yaml configs to the devices' IP addresses
using use_address or set a manual IP.
—
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEN5KACBPOQPCSNBLWQEH4TYCVUTVAVCNFSM6AAAAAA6Z3HK3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGE3TGOJXG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
When you try to update through the dashboard, what error do you get there? |
|
Sorry. I threw the bulb out. Tired of battling with it.
…On Mon, Nov 6, 2023 at 11:06 AM Brian Kaufman ***@***.***> wrote:
When you try to update through the dashboard, what error do you get there?
—
Reply to this email directly, view it on GitHub
<#44 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEN5KADWFYUEBCQLFPZXQWTYDERJ5AVCNFSM6AAAAAA6Z3HK3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJVG42TSMRTGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
A few releases ago, it was the same problem. Then it work for about two releases and now updates fails again:
This is runing from within HAOS dashboard/UI.
The text was updated successfully, but these errors were encountered: