-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Strapping GPIO15 prevents OTA flashing from working #212
Comments
When assembling the Ulanzi firmware, I have this warning, but everything works, including the buzzer. |
With esphome 2024.2.0 I experience the same! |
Buzzer didn't clean up. |
It’s strange, on 2024.2.0 and 2024.2.1 the firmware via OTA went through without problems for me (I didn’t remove the buzzer), I just checked Rainbow (I flashed it 10 times), but yesterday on 2024.2.2 I already received the same error when trying to OTA , just reboot Esp. |
Let me add that the OTA update from 2024.2.1 to 2024.2.2 was unsuccessful, I flashed it with a wire, then OTA works again, yesterday I updated the firmware several times via OTA on ESPHome 2024.2.2, without problems. Buzzer didn't clean up. |
With the default easy_ulanzi.yaml I can't do OTA updates. They usually go through and the clock reboots but it doesn't actually change anything.
I have a fairly new Ulanzi smart clock (might be a newer hardware revision? maybe that's why it hasn't come up yet) and I've struggled to configure anything until I realized that the warning about GPIO15 being a boot selector pin was actually correct, removing the pin definition made OTA updates work again.
I'd propose just removing anything buzzer-related from the default config or at least adding a warning. I don't think not having the buzzer connected is a big loss to anyone since it's pretty quiet and sounds awful.
Important
If the buzzer config is removed, when rebooting the clock through the left+right button combo the buzzer never stops. This can be remedied without negative effect by using the following config:
The text was updated successfully, but these errors were encountered: