I noticed that it stopped to update yesterday at 22:05, I looked on the log and probably it is related to the firmware update problem:
** Restart **
SD initialized.
6/22/18 06:22:25z Real Time Clock is running. Unix time 1529648545
6/22/18 06:22:25z Version 02_03_07
6/22/18 06:22:25z Reset reason: Software/System restart
6/22/18 06:22:25z Trace: 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:1, 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:4, 9:5, 9:9, 1:2, 1:3, 10:2, 10:3
6/22/18 06:22:25z ESP8266 ChipID: 6910350
6/22/18 08:22:25 Local time zone: 2
6/22/18 08:22:25 device name: pinguITW, version: 3
6/22/18 08:22:28 MDNS responder started
6/22/18 08:22:28 You can now connect to http://pinguITW.local
6/22/18 08:22:28 HTTP server started
6/22/18 08:22:28 dataLog: service started.
6/22/18 08:24:11 dataLog: Last log entry: 1529611745
6/22/18 08:24:11 statService: started.
6/22/18 08:24:11 timeSync: service started.
6/22/18 08:24:11 WiFi connected. SSID: pingu, IP: 192.168.18.73
6/22/18 08:24:11 Updater: started.
6/22/18 08:24:12 Updater: Update from 02_03_07 to 02_03_08
6/22/18 08:24:12 Updater: download 02_03_08
6/22/18 08:24:25 Updater: Download failed HTTPcode
and there the view of the status (snapshot of 22.06.2018 at 08:29):
I could “solve” the log issue by deleting the log and ndx files (in case you are interested I made a copy before).
But the firmware update issue is still present.
I do not know if you changed something but now he got the update.
Haven’t changed anything. The update is a big binary file. It doesn’t always download successfully, and sometimes fails to verify, but it will persist and retry every hour until it gets done.
Looking at your problem report, the message log segment that you posted is after whatever damage was done. The last entry in the datalog is 21/6/2018 22:09:05. That the first entry shows as zero suggests to me that there was damage at the end of the file (I know, it’s counterintuitive). The newer release has some code to try to repair these kinds of errors, which are rare.
In the above status display, your history log has not been opened because the Current Log is inconsistent. When the current Log is repaired or deleted and recreated, the history should come back through 21/6/18 22:09:00.
Could you post your message log going back a few restarts before this happened? I’m curious what has been going on?
I see something interesting at this point:
6/21/18 21:09:04 influxDB: Start posting from 6/21/18 21:08:40
6/21/18 22:09:04 Updater: Update from 02_03_07 to 02_03_08
6/21/18 22:09:04 Updater: download 02_03_08
6/21/18 22:09:34 Updater: Download failed HTTPcode
** Restart **
SD initialized.
6/21/18 20:37:52z Real Time Clock is running. Unix time 1529613472
6/21/18 20:37:52z Version 02_03_07
6/21/18 20:37:52z Reset reason: Software Watchdog
iotamsgs_short.txt (11.0 KB)