Okay, this isn’t a problem with that particular device (athom plug). I’ve just flashed a random esp8266 dev board with esphome and it behaves in the same way.
Did you try already with a lower log level? It’s easily possible to crash a esp8266 when for example a display is attached and setting the log level to very_verbose.
Maybe give the default (debug) log level a try or even just set it to info to see if it makes a difference
[1B][0;37m[V][sensor:043]: 'Test WiFi Signal': Received new state -69.000000[1B][0m
[1B][0;36m[D][sensor:093]: 'Test WiFi Signal': Sending state -69.00000 dBm with 0 decimals of accuracy[1B][0m
[1B][0;37m[V][sensor:043]: 'Test Uptime Sensor': Received new state 114.971001[1B][0m
[1B][0;36m[D][sensor:093]: 'Test Uptime Sensor': Sending state 114.97100 s with 0 decimals of accuracy[1B][0m
[1B][0;33m[W][api.connection:093]: ESPHome Logs 2023.7.0 (172.16.0.2): Connection reset[1B][0m
[1B][0;37m[V][api:114]: Removing connection to ESPHome Logs 2023.7.0 (172.16.0.2)[1B][0m
ip:172.16.0.205,mask:255.255.255.0,gw:172.16.0.1
[1B][0;37m[V][wifi_esp8266:507]: Event: Got IP static_ip=172.16.0.205 gateway=172.16.0.1 netmask=255.255.255.0[1B][0m
wifi evt: 3
[1B][0;36m[D][api:102]: Accepted 172.16.0.2[1B][0m
[1B][0;33m[W][component:204]: Component api took a long time for an operation (0.28 s).[1B][0m
[1B][0;33m[W][component:205]: Components should block for at most 20-30ms.[1B][0m
[1B][0;37m[V][api.connection:1012]: Hello from client: 'ESPHome Logs 2023.7.0 (172.16.0.2)' | API Version 1.9[1B][0m
[1B][0;36m[D][api.connection:1031]: ESPHome Logs 2023.7.0 (172.16.0.2): Connected successfully[1B][0m
[1B][0;37m[V][sensor:043]: 'Test WiFi Signal': Received new state -63.000000[1B][0m
[1B][0;36m[D][sensor:093]: 'Test WiFi Signal': Sending state -63.00000 dBm with 0 decimals of accuracy[1B][0m
[1B][0;37m[V][sensor:043]: 'Test Uptime Sensor': Received new state 174.970993[1B][0m
[1B][0;36m[D][sensor:093]: 'Test Uptime Sensor': Sending state 174.97099 s with 0 decimals of accuracy[1B][0m
No, it doesn’t restart, just reconnects.
I’ve found a lot of similar cases (about 8266) and different suggestions, but in my case, they do to fix the issue.
Very weird. You might want to try to erase the flash of your esp8266 dev board via serial (esptool) and after that flash/install esphome again to this board to be a 100% sure to don’t have any wifi or other configs left.
could try to decrease tx power - maybe that stabilizes your mileage
output_power (Optional, string): The amount of TX power for the WiFi interface from 8.5dB to 20.5dB. Default for ESP8266 is 20dB, 20.5dB might cause unexpected restarts.
orange-assistant, reduced to 8.5dB, disconnects with the same precise frequency.
NO disconnects after configuring manual_ip, so it’s DHCP that causes the issue.
Right after this, I remembered, that “Lease time” was changed by me during some experiments… and it was set to exactly 60 seconds. No disconnects after changing it to 12 hours.