Closed jeroenleenarts closed 3 weeks ago
As you can see. I commented the 'hardware_watchdog' package, but that didn't help.
There was something in the change log about separating out the watchdog component so it wasn't linked only to the http_request component. I'll take a look at what needs to be done.
I experienced the same issue. It looks like the ID watchdog is now taken by some other ESPHome code Maybe you just need to rename your ID to a1_watchdog
As you can see. I commented the 'hardware_watchdog' package, but that didn't help.
I'm surprised that commenting out the watchdog package didn't resolve it.
I experienced the same issue. It looks like the ID watchdog is now taken by some other ESPHome code Maybe you just need to rename your ID to a1_watchdog
I just updated watchdog.yaml to the following which is letting me get past the previous hurdle. Doing some additional testing before pushing it up to the repo. If you wanted to also test, you could comment out the watchdog.yaml line and add this at the bottom of your file:
output:
- platform: gpio
# Pin to notify external watchdog that activity is present
id: external_watchdog
pin:
number: GPIO2
ignore_strapping_warning: true # Acknowledging that this is a strapping pin and should not have external pullup/down resistors https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
interval:
- interval: 2.5min
# Notify watchdog device it is still alive
then:
- output.turn_on: external_watchdog
- delay: 20ms
- output.turn_off: external_watchdog
Just pushed an update to the repo. If you have already tried to update today, ESPHome by default keeps a cache of packages for 24 hours, so you may not be able to pull it down until that expires, unless you can delete the config/.esphome/packages/
directory.
Got EspHome running as an add on. So I will take the 24h wait. 👍
Update Successful. No errors. The new firmware executing and reporting to Home Assistant Thanks
Fixed
My config: