J. Nick Koston
J. Nick Koston
clang-tidy failure will be fixed in https://github.com/esphome/esphome/pull/12362
How about something like ### Single pin (works on both ESP32 and BK72xx) ```yaml deep_sleep: wakeup_pin: GPIO25 wakeup_pin_mode: KEEP_AWAKE ``` ### Multiple pins (BK72xx only) ```yaml deep_sleep: wakeup_pin: - pin:...
for the nested I think `mode` makes sense over `wakup_pin_mode` to avoid the verbosity since its already under `wakeup_pin` ```yaml deep_sleep: wakeup_pin: - pin: GPIO25 mode: KEEP_AWAKE - pin: GPIO26...
I did some tweaks to cleanup the validators. Please double check that it still works as expected
Docs PR needs a quick update as well
We will need serial logs to know what's going on.
Streaming over the network won't work to catch network failures or crashes because it can't send the log over the network once its failed. You have to use a usb/serial...
Syslog also has the same issue as the native API. On a significant failure only the serial console will get the failure logs and trace back
Can you try powering it via USB ?
I'm not aware of any ethernet / POE change that would explain this