Skip to content
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

Problem with OTA update of ESPHome #193

Open
nikolai2111 opened this issue Jun 20, 2024 · 3 comments
Open

Problem with OTA update of ESPHome #193

nikolai2111 opened this issue Jun 20, 2024 · 3 comments

Comments

@nikolai2111
Copy link

After the latest update to ESPhome (2024.6.1) we had a problem with the OTA update.

It says that the 'platform: esphome' should be added, but it's not clear where and in the .yaml specified here does not contain any of this.

INFO ESPHome 2024.6.1
INFO Reading configuration /config/esphome/tubeszb-cc2652-poe-2023.yaml...
WARNING GPIO12 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
Failed config

At least one platform must be specified for 'ota'; add 'platform: esphome' for original OTA functionality
@nikolai2111
Copy link
Author

Solution:
Add platform: esphome under the ota: option.

ota:
  platform: esphome

@nikolai2111
Copy link
Author

Now the following message appeared:

11:31:33 | [W] | [api.connection:107] | : Reading failed: BAD_INDICATOR errno=11

@nikolai2111 nikolai2111 reopened this Jun 20, 2024
@tube0013
Copy link
Owner

ESPHome 2024.6.x has many changes I don't advise updating at this time until it can be tested fully. You can go back to older version by using the bin file available for your device.

The api error has to do with the connection to home assistant. Power cycle the device and see if that resolves that.

If the device shows it has an update just disable the update entity in the devices esphome configuration page.

There really is no reason to update the device for every ESPHome release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants