[schwim]

It just happened again. Unfortunately a hard restart (power cycle) does not recover it. Same behavior as above. It’s online for about 6 seconds then reboots itself.

Any suggestions before I send someone over to poke it? It would be neat to recover it somehow.

[schwim]

I managed to get someone to head over and reset it for me. All is working now.

Interesting that it got in that state. I power cycled it about 30 times and only managed to get the UI up 3-4 times. Is this something that may have been identified and fixed in the later firmware versions?

[schwim]

Interesting find – the OG is still trying to report status to Blynk. I can see the TCP handshake and a small bit of data going out. Unfortunately I deleted that profile from my Blynk account long ago because I didn’t need it at the time. Guess I kept the key in the OG though.

Any chance this can be exploited locally to take control of it? I can spoof the blynk IP and run a flask server to issue commands. No idea what command it to do though.

[schwim]

In the course of troubleshooting I noticed the OG keeps asking for a DHCP address every 15 seconds or so. Not sure if this is indicative of a boot loop.

Jan 11 11:37:27 observatory dnsmasq-dhcp[5406]: DHCPDISCOVER(ap01) 5c:cf:7f:d6:1c:af
Jan 11 11:37:27 observatory dnsmasq-dhcp[5406]: DHCPOFFER(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:37:27 observatory dnsmasq-dhcp[5406]: DHCPREQUEST(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:37:27 observatory dnsmasq-dhcp[5406]: DHCPACK(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af ESP_D61CAF
Jan 11 11:37:41 observatory dnsmasq-dhcp[5406]: DHCPDISCOVER(ap01) 5c:cf:7f:d6:1c:af
Jan 11 11:37:41 observatory dnsmasq-dhcp[5406]: DHCPOFFER(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:37:41 observatory dnsmasq-dhcp[5406]: DHCPREQUEST(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:37:41 observatory dnsmasq-dhcp[5406]: DHCPACK(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af ESP_D61CAF
Jan 11 11:37:56 observatory dnsmasq-dhcp[5406]: DHCPDISCOVER(ap01) 5c:cf:7f:d6:1c:af
Jan 11 11:37:56 observatory dnsmasq-dhcp[5406]: DHCPOFFER(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:37:56 observatory dnsmasq-dhcp[5406]: DHCPREQUEST(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:37:56 observatory dnsmasq-dhcp[5406]: DHCPACK(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af ESP_D61CAF
Jan 11 11:38:11 observatory dnsmasq-dhcp[5406]: DHCPDISCOVER(ap01) 5c:cf:7f:d6:1c:af
Jan 11 11:38:11 observatory dnsmasq-dhcp[5406]: DHCPOFFER(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:38:11 observatory dnsmasq-dhcp[5406]: DHCPREQUEST(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:38:11 observatory dnsmasq-dhcp[5406]: DHCPACK(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af ESP_D61CAF
Jan 11 11:38:25 observatory dnsmasq-dhcp[5406]: DHCPDISCOVER(ap01) 5c:cf:7f:d6:1c:af
Jan 11 11:38:25 observatory dnsmasq-dhcp[5406]: DHCPOFFER(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:38:25 observatory dnsmasq-dhcp[5406]: DHCPREQUEST(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af
Jan 11 11:38:25 observatory dnsmasq-dhcp[5406]: DHCPACK(ap01) 172.16.255.1 5c:cf:7f:d6:1c:af ESP_D61CAF

• This reply was modified 6 years ago by schwim.

[schwim]

Thanks for checking into it!

By the way, I’m using the OG to control an astronomical observatory roof. It’s very comforting to know that the roof is open or closed without having to check a camera! Good stuff!

[schwim]

Looks like this happened to me today. The OG was online for several weeks then dropped offline today. The light was blinking slowly, not reconnecting. A power cycle cause it to re-connect.

[Author]

Posts