Hello,
Notice my iotawatt was no longer sending sending to influxdb and populating my grafana graphs. I went to web into the device and it just hangs. I can ping it. Tried unplugging the device and plugging back in and it still responds the same way. Is there any other way to troubleshoot the device remotely?
Regards,
Dan
Unfortunately I am remote from the device and currently don’t have physical access. Is there any other avenues to troubleshoot? This has been working fine for 11 months. Had issue with influxdb on previous firmware, but didn’t cause web interface not to load.
There is no remotediagnostic capability beyond the ability to connect to the web-server through port forwarding.
That stinks. I wish there was some kind of remote way to get in if http server is failing
Seems like it is rebooting alot. I managed to get some logs via curl between reboots.
** Restart **
SD initialized.
1/22/19 17:22:07z Real Time Clock is running. Unix time 1548177727
1/22/19 17:22:08z Version 02_03_18
1/22/19 17:22:08z Reset reason: Software Watchdog
1/22/19 17:22:09z Trace: 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19], 1:6, 1:1[5], 1:2[6], 9:0[6], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[14], 14:0, 14:1, 14:2
1/22/19 17:22:11z ESP8266 ChipID: 191732
1/22/19 17:22:12z SPIFFS mounted.
1/22/19 12:22:13 EmonService: Invalid configuration.
1/22/19 12:22:14 Local time zone: -5
1/22/19 12:22:15 device name: MyIota, version: 3
1/22/19 12:22:15 MDNS responder started for hostname MyIota
1/22/19 12:22:16 LLMNR responder started for hostname MyIota
1/22/19 12:22:17 HTTP server started
1/22/19 12:22:18 timeSync: service started.
1/22/19 12:22:19 statService: started.
1/22/19 12:22:19 WiFi connected. SSID=MySSIF, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 12:22:21 Updater: service started. Auto-update class is MINOR
1/22/19 12:22:22 dataLog: service started.
1/22/19 12:22:22 dataLog: Last log entry 12/29/18 09:21:35
1/22/19 12:22:24 historyLog: service started.
** Restart **
SD initialized.
1/22/19 17:22:28z Real Time Clock is running. Unix time 1548177748
1/22/19 17:22:29z Version 02_03_18
1/22/19 17:22:29z Reset reason: Software Watchdog
1/22/19 17:22:30z Trace: 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19], 1:6, 1:1[5], 1:2[6], 9:0[6], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[14], 14:0, 14:1, 14:2
1/22/19 17:22:32z ESP8266 ChipID: 191732
1/22/19 17:22:33z SPIFFS mounted.
1/22/19 12:22:34 EmonService: Invalid configuration.
1/22/19 12:22:35 Local time zone: -5
1/22/19 12:22:36 device name: MyIota, version: 3
1/22/19 12:22:36 MDNS responder started for hostname MyIota
1/22/19 12:22:37 LLMNR responder started for hostname MyIota
1/22/19 12:22:38 HTTP server started
1/22/19 12:22:39 timeSync: service started.
1/22/19 12:22:40 statService: started.
1/22/19 12:22:40 WiFi connected. SSID=MySSIF, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 12:22:41 Updater: service started. Auto-update class is MINOR
1/22/19 12:22:43 dataLog: service started.
1/22/19 12:22:43 dataLog: Last log entry 12/29/18 09:21:35
1/22/19 12:22:44 historyLog: service started.
** Restart **
SD initialized.
1/22/19 17:22:49z Real Time Clock is running. Unix time 1548177769
1/22/19 17:22:50z Version 02_03_18
1/22/19 17:22:50z Reset reason: Software Watchdog
1/22/19 17:22:51z Trace: 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19], 1:6, 1:1[5], 1:2[6], 9:0[6], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[14], 14:0, 14:1, 14:2
1/22/19 17:22:53z ESP8266 ChipID: 191732
1/22/19 17:22:54z SPIFFS mounted.
1/22/19 12:22:55 EmonService: Invalid configuration.
1/22/19 12:22:56 Local time zone: -5
1/22/19 12:22:57 device name: MyIota, version: 3
1/22/19 12:22:57 MDNS responder started for hostname MyIota
1/22/19 12:22:58 LLMNR responder started for hostname MyIota
1/22/19 12:22:59 HTTP server started
1/22/19 12:23:00 timeSync: service started.
1/22/19 12:23:01 statService: started.
1/22/19 12:23:01 WiFi connected. SSID=MySSIF, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 12:23:02 Updater: service started. Auto-update class is MINOR
1/22/19 12:23:04 dataLog: service started.
1/22/19 12:23:04 dataLog: Last log entry 12/29/18 09:21:35
1/22/19 12:23:06 historyLog: service started.
** Restart **
SD initialized.
1/22/19 17:23:10z Real Time Clock is running. Unix time 1548177790
1/22/19 17:23:11z Version 02_03_18
1/22/19 17:23:11z Reset reason: Software Watchdog
1/22/19 17:23:12z Trace: 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19], 1:6, 1:1[5], 1:2[6], 9:0[6], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[14], 14:0, 14:1, 14:2
1/22/19 17:23:14z ESP8266 ChipID: 191732
1/22/19 17:23:15z SPIFFS mounted.
1/22/19 12:23:16 EmonService: Invalid configuration.
1/22/19 12:23:17 Local time zone: -5
1/22/19 12:23:18 device name: MyIota, version: 3
1/22/19 12:23:18 MDNS responder started for hostname MyIota
1/22/19 12:23:19 LLMNR responder started for hostname MyIota
1/22/19 12:23:20 HTTP server started
Apparently the HTTP server is actually working because it served up this log. The problem is that it keeps restarting. From the trace and other clues it appears to be getting stuck in a loop while opening the history log. Most likely, the history log is damaged. This restarting has been going on since Dec 29 at 09:21 local time (UTC-5).
It’s a long shot, but if you can get a log reset command in via curl the way you read the log, you might get it going again:
http://iotawatt.local/command?deletelog=both
Obviously you will need to change the iotawatt.local to the remote IP:port. If you get this in, the IoTaWatt will delete the logs, restart, and create new logs. You will need to wait up to a minute after each try before attempting to access to see if it worked. The new history log will not be created until the current log has a few minutes of data.
Thank you for the suggestion. Well I got an ok with deleting the logs, but it continues to reboot. Is there any documents around other commands that can be run? I have found using curl to hit the different endpoints has been reliable (between reboots).
Do you think pushing an upgrade would help?
Dan
There’s no viable way to do that.
Can you get another log?
user$ curl http://192.168.10.10/iotawatt/iotamsgs.txt?textpos=-10000
1/22/19 16:32:07 WiFi connected. SSID=****, IP=192.168.10.10, channel=6, RSSI -40db
1/22/19 16:32:08 Updater: service started. Auto-update class is MINOR
1/22/19 16:32:09 dataLog: service started.
1/22/19 16:32:10 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:32:15z Real Time Clock is running. Unix time 1548192735
1/22/19 21:32:16z Version 02_03_18
1/22/19 21:32:16z Reset reason: Software Watchdog
1/22/19 21:32:17z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:32:19z ESP8266 ChipID: 191732
1/22/19 21:32:20z SPIFFS mounted.
1/22/19 16:32:22 EmonService: Invalid configuration.
1/22/19 16:32:22 Local time zone: -5
1/22/19 16:32:23 device name: , version: 3
1/22/19 16:32:24 MDNS responder started for hostname ****
1/22/19 16:32:25 LLMNR responder started for hostname ****
1/22/19 16:32:26 HTTP server started
1/22/19 16:32:27 timeSync: service started.
1/22/19 16:32:27 statService: started.
1/22/19 16:32:28 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -42db
1/22/19 16:32:29 Updater: service started. Auto-update class is MINOR
1/22/19 16:32:30 dataLog: service started.
1/22/19 16:32:31 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:32:36z Real Time Clock is running. Unix time 1548192756
1/22/19 21:32:37z Version 02_03_18
1/22/19 21:32:37z Reset reason: Software Watchdog
1/22/19 21:32:38z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:32:40z ESP8266 ChipID: 191732
1/22/19 21:32:41z SPIFFS mounted.
1/22/19 16:32:43 EmonService: Invalid configuration.
1/22/19 16:32:43 Local time zone: -5
1/22/19 16:32:44 device name: , version: 3
1/22/19 16:32:45 MDNS responder started for hostname ****
1/22/19 16:32:46 LLMNR responder started for hostname ****
1/22/19 16:32:47 HTTP server started
1/22/19 16:32:48 timeSync: service started.
1/22/19 16:32:48 statService: started.
1/22/19 16:32:49 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -40db
1/22/19 16:32:50 Updater: service started. Auto-update class is MINOR
1/22/19 16:32:51 dataLog: service started.
1/22/19 16:32:52 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:32:57z Real Time Clock is running. Unix time 1548192777
1/22/19 21:32:58z Version 02_03_18
1/22/19 21:32:58z Reset reason: Software Watchdog
1/22/19 21:32:59z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:33:01z ESP8266 ChipID: 191732
1/22/19 21:33:02z SPIFFS mounted.
1/22/19 16:33:04 EmonService: Invalid configuration.
1/22/19 16:33:04 Local time zone: -5
1/22/19 16:33:05 device name: , version: 3
1/22/19 16:33:06 MDNS responder started for hostname ****
1/22/19 16:33:07 LLMNR responder started for hostname ****
1/22/19 16:33:08 HTTP server started
1/22/19 16:33:09 timeSync: service started.
1/22/19 16:33:12 statService: started.
1/22/19 16:33:13 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 16:33:14 Updater: service started. Auto-update class is MINOR
1/22/19 16:33:15 dataLog: service started.
1/22/19 16:33:16 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:33:22z Real Time Clock is running. Unix time 1548192802
1/22/19 21:33:23z Version 02_03_18
1/22/19 21:33:23z Reset reason: Software Watchdog
1/22/19 21:33:24z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:33:26z ESP8266 ChipID: 191732
1/22/19 21:33:27z SPIFFS mounted.
1/22/19 16:33:29 EmonService: Invalid configuration.
1/22/19 16:33:29 Local time zone: -5
1/22/19 16:33:30 device name: , version: 3
1/22/19 16:33:31 MDNS responder started for hostname ****
1/22/19 16:33:32 LLMNR responder started for hostname ****
1/22/19 16:33:33 HTTP server started
1/22/19 16:33:34 timeSync: service started.
1/22/19 16:33:34 statService: started.
1/22/19 16:33:35 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -40db
1/22/19 16:33:36 Updater: service started. Auto-update class is MINOR
1/22/19 16:33:37 dataLog: service started.
1/22/19 16:33:38 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:33:43z Real Time Clock is running. Unix time 1548192823
1/22/19 21:33:44z Version 02_03_18
1/22/19 21:33:44z Reset reason: Software Watchdog
1/22/19 21:33:45z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:33:47z ESP8266 ChipID: 191732
1/22/19 21:33:48z SPIFFS mounted.
1/22/19 16:33:50 EmonService: Invalid configuration.
1/22/19 16:33:50 Local time zone: -5
1/22/19 16:33:51 device name: , version: 3
1/22/19 16:33:52 MDNS responder started for hostname ****
1/22/19 16:33:53 LLMNR responder started for hostname ****
1/22/19 16:33:54 HTTP server started
1/22/19 16:33:55 timeSync: service started.
1/22/19 16:33:55 statService: started.
1/22/19 16:33:56 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 16:33:57 Updater: service started. Auto-update class is MINOR
1/22/19 16:33:58 dataLog: service started.
1/22/19 16:33:59 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:34:04z Real Time Clock is running. Unix time 1548192844
1/22/19 21:34:05z Version 02_03_18
1/22/19 21:34:05z Reset reason: Software Watchdog
1/22/19 21:34:06z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:34:08z ESP8266 ChipID: 191732
1/22/19 21:34:09z SPIFFS mounted.
1/22/19 16:34:11 EmonService: Invalid configuration.
1/22/19 16:34:11 Local time zone: -5
1/22/19 16:34:12 device name: , version: 3
1/22/19 16:34:13 MDNS responder started for hostname ****
1/22/19 16:34:14 LLMNR responder started for hostname ****
1/22/19 16:34:15 HTTP server started
1/22/19 16:34:16 timeSync: service started.
1/22/19 16:34:16 statService: started.
1/22/19 16:34:17 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 16:34:18 Updater: service started. Auto-update class is MINOR
1/22/19 16:34:19 dataLog: service started.
1/22/19 16:34:20 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:34:25z Real Time Clock is running. Unix time 1548192865
1/22/19 21:34:26z Version 02_03_18
1/22/19 21:34:26z Reset reason: Software Watchdog
1/22/19 21:34:27z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:34:29z ESP8266 ChipID: 191732
1/22/19 21:34:30z SPIFFS mounted.
1/22/19 16:34:32 EmonService: Invalid configuration.
1/22/19 16:34:32 Local time zone: -5
1/22/19 16:34:33 device name: , version: 3
1/22/19 16:34:34 MDNS responder started for hostname ****
1/22/19 16:34:35 LLMNR responder started for hostname ****
1/22/19 16:34:36 HTTP server started
1/22/19 16:34:41 timeSync: service started.
1/22/19 16:34:42 statService: started.
1/22/19 16:34:43 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 16:34:44 Updater: service started. Auto-update class is MINOR
1/22/19 16:34:50 dataLog: service started.
1/22/19 16:34:50 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:34:55z Real Time Clock is running. Unix time 1548192895
1/22/19 21:34:56z Version 02_03_18
1/22/19 21:34:56z Reset reason: Software Watchdog
1/22/19 21:34:57z Trace: 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[5], 1:2[6], 9:0[6], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 10:13, 1:4, 1:5[19]
1/22/19 21:34:59z ESP8266 ChipID: 191732
1/22/19 21:35:00z SPIFFS mounted.
1/22/19 16:35:02 EmonService: Invalid configuration.
1/22/19 16:35:02 Local time zone: -5
1/22/19 16:35:03 device name: , version: 3
1/22/19 16:35:04 MDNS responder started for hostname ****
1/22/19 16:35:05 LLMNR responder started for hostname ****
1/22/19 16:35:06 HTTP server started
1/22/19 16:35:07 timeSync: service started.
1/22/19 16:35:07 statService: started.
1/22/19 16:35:08 WiFi connected. SSID=, IP=192.168.10.10, channel=6, RSSI -41db
1/22/19 16:35:09 Updater: service started. Auto-update class is MINOR
1/22/19 16:35:10 dataLog: service started.
1/22/19 16:35:11 dataLog: New current log created.
** Restart **
SD initialized.
1/22/19 21:35:17z Real Time Clock is running. Unix time 1548192917
1/22/19 21:35:18z Version 02_03_18
1/22/19 21:35:18z Reset reason: Software Watchdog
1/22/19 21:35:19z Trace: 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[5], 1:6, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[19]
1/22/19 21:35:21z ESP8266 ChipID: 191732
1/22/19 21:35:22z SPIFFS mounted.
1/22/19 16:35:24 EmonService: Invalid configuration.
1/22/19 16:35:24 Local time zone: -5
1/22/19 16:35:25 device name: ****, version: 3
1/22/19 16:35:26 MDNS responder started for hostname ****
1/22/19 16:35:27 LLMNR responder started for hostname ****
1/22/19 16:35:28 HTTP server started
It still appears that there is a log problem, but I’m growing concerned that there is a problem with the SDcard. I think that when you finally get access to it, you should have a new SDcard ready to swap in. If you PM me your address, I’ll send you one formatted and loaded with the 02_03_18 files.
I am somewhat intrigued by the capability to send limited commands. If you wouldn’t mind PMing me the IP and port, I’d like to try a few things that are difficult to explain. I wouldn’t hold out much promise, but it may help me better understand how to improve remote diagnosis.