I stupidly did deletelog=both and iotawatt became unavailable

Support
1

I was searching forum for a way to automate download of configuration etc from iotawatt and stupid me managed to blindly click on http://IoTaWatt.local/command?deletelog=both I found provided on one of the posts… well – the beast thought for awhile and then seems disappeared – can’t access it in the browser or ping.

  • is that expected ? (I thought from reading it should just wipe the logs but continue)
  • what is the best way to proceed/troubleshoot now? I have tried to power cycle already but seems didn’t come back up anyways.
  • any way to recover those historical files?

update 1: upon next reboot(s), it did red-green-green for awhile but then seems connecting on wifi, which had in logs

Mar 31 13:07:48 wlceventd: wlceventd_proc_event(685): wl0.3: Auth 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:0
Mar 31 13:07:48 wlceventd: wlceventd_proc_event(722): wl0.3: Assoc 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:-61
Mar 31 13:09:01 wlceventd: wlceventd_proc_event(645): wl0.3: Deauth_ind 8C:AA:B5:C1:DD:C1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 31 13:09:01 wlceventd: wlceventd_proc_event(662): wl0.3: Disassoc 8C:AA:B5:C1:DD:C1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-60
Mar 31 13:09:01 wlceventd: wlceventd_proc_event(685): wl0.3: Auth 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:-60
Mar 31 13:09:01 wlceventd: wlceventd_proc_event(722): wl0.3: Assoc 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:-60
Mar 31 13:09:04 wlceventd: wlceventd_proc_event(645): wl0.3: Deauth_ind 8C:AA:B5:C1:DD:C1, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 31 13:09:04 wlceventd: wlceventd_proc_event(662): wl0.3: Disassoc 8C:AA:B5:C1:DD:C1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-61
Mar 31 13:09:04 wlceventd: wlceventd_proc_event(685): wl0.3: Auth 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:-61
Mar 31 13:09:04 wlceventd: wlceventd_proc_event(722): wl0.3: Assoc 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:-61
Mar 31 13:11:08 wlceventd: wlceventd_proc_event(645): wl0.3: Deauth_ind 8C:AA:B5:C1:DD:C1, status: 0, reason: Disassociated due to inactivity (4), rssi:-60
Mar 31 13:12:06 wlceventd: wlceventd_proc_event(685): wl0.3: Auth 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:0
Mar 31 13:12:06 wlceventd: wlceventd_proc_event(722): wl0.3: Assoc 8C:AA:B5:C1:DD:C1, status: Successful (0), rssi:-64

but then going into rapid ‘red-red-red’ frenzy (more like rapidly pulsing red, not clear code; like it was with rapid green pulsating reported elsewhere whenever giving up on trying to connect to wifi I believe). Am I doomed to take it apart to take sd card out to see more in messages or is there a better way? feasible to pull out sdcard without disconnecting CTs?

update 2: rapid reds go into rapid greens eventually. In router logs just those last two messages as above and no other at all. Iotawatt IP (I staticly bind it in router to mac) isn’t pingable

2

ok – I think “resolved” and it was again just inability to connect to wifi. Eventually after router restart and few more reboots iotawatt finally seems has connected. But indeed all history is gone :frowning: oh well – I’ve got what I “asked for” , heh heh - not sure how I managed to blindly click on it.

3

That’s why there is no button for it. You have to deliberately type in the URL command.