History not shown after wifi change

After one month of data gathering at a certain location, I uninstalled the IotaWatt last week and took the device back home in order to make some data analyses. But unfortunately the graph does not show any historical data anymore after reconnecting the device to my own wifi?!
I downloaded the history log and data log and those files are >200MB, so probably do contain historical data.
How can I show the data in the graphs? And what might be the reason data is not shown anymore?

Can you post a screenshot of the message log and the Graph+ that is not work8ng as expected?

After downloads were complete, I reconnected to take the screenshot you requested, but now the Graph+ shows the data correctly… Strange… but now all data is back available for download!

So I guess this issue is obsolete, but no idea what I did to resolve it.
Thanks for your reply! (Might order some extra modules next week :star_struck: :ok_hand:)

** Restart **

SD initialized.
8/11/21 08:23:47z Real Time Clock is running. Unix time 1628670227
8/11/21 08:23:47z Reset reason: Software/System restart
8/11/21 08:23:47z Trace: 0:0, 0:0, 0:0, 0:0, 11:0, 11:4, 11:5, 11:5, 11:10, 11:15, 11:20, 11:20[1], 11:20[2], 11:20[3], 11:21, 11:22, 11:21, 11:22, 11:21, 11:22, 11:20[4], 11:20[5], 11:20[6], 11:20[7], 11:25, 11:30, 11:31, 11:30, 11:35, 11:40, 11:45, 11:70
8/11/21 08:23:47z ESP8266 ChipID: 16412174
8/11/21 08:23:47z IoTaWatt 5.0, Firmware version 02_06_05
8/11/21 08:23:47z SPIFFS mounted.
8/11/21 11:23:47 Local time zone: +2:00
8/11/21 11:23:47 Using Daylight Saving Time (BST) when in effect.
8/11/21 11:23:47 device name: IotaWatt
8/11/21 11:23:47 HTTP server started
8/11/21 11:23:47 timeSync: service started.
8/11/21 11:23:47 statService: started.
8/11/21 11:23:47 dataLog: service started.
8/11/21 11:23:47 dataLog: Last log entry 08/11/21 11:18:15
8/11/21 11:23:52 historyLog: service started.
8/11/21 11:23:52 historyLog: Last log entry 08/11/21 11:18:00
8/11/21 11:24:20 WiFi connected. SSID=Technische Dienst, IP=192.168.0.32, channel=1, RSSI -56db
8/11/21 11:24:20 MDNS responder started for hostname IotaWatt
8/11/21 11:24:20 LLMNR responder started for hostname IotaWatt
8/11/21 11:24:20 Updater: service started. Auto-update class is MINOR
8/11/21 11:24:34 Updater: Invalid response from server. HTTPcode: -4

** Restart **

SD initialized.
8/16/21 07:37:03z Real Time Clock is running. Unix time 1629099423
8/16/21 07:37:03z Power failure detected.
8/16/21 07:37:03z Reset reason: External System
8/16/21 07:37:03z ESP8266 ChipID: 16412174
8/16/21 07:37:03z IoTaWatt 5.0, Firmware version 02_06_05
8/16/21 07:37:03z SPIFFS mounted.
8/16/21 10:37:03 Local time zone: +2:00
8/16/21 10:37:03 Using Daylight Saving Time (BST) when in effect.
8/16/21 10:37:03 device name: IotaWatt
8/16/21 10:37:06 Connecting with WiFiManager.
8/16/21 10:37:52 HTTP server started
8/16/21 11:48:37 WiFi connected. SSID=wifi96, IP=192.168.0.130, channel=6, RSSI -61db
8/16/21 11:48:37 MDNS responder started for hostname IotaWatt
8/16/21 11:48:37 LLMNR responder started for hostname IotaWatt
8/16/21 13:00:12 timeSync: service started.
8/16/21 13:00:12 statService: started.
8/16/21 13:00:12 Updater: service started. Auto-update class is MINOR
8/16/21 13:00:12 dataLog: service started.
8/16/21 13:00:12 dataLog: Last log entry 08/11/21 11:28:05
8/16/21 13:00:12 historyLog: service started.
8/16/21 13:00:12 historyLog: Last log entry 08/11/21 11:28:00
8/16/21 14:16:48 dataLog: datalog WDT - restarting

Now that I see this message log details from the afternoon, I guess this timeSync did something to restart the dataLog & historyLog service?

That has nothing to do with it. SOP. The datalog WDT suggests you did not have a VT connected. Is that possible?

1 Like

Yes, correct no VT connected, because I’m not measuring anything anymore, just want to access the data to create my analysis.

That’s probably what was giving you trouble. The 60 Hz (or 50) is like a heartbeat and is what synchronizes the underlying pseudo operating system. It would be possible to simulate it with the system timer, but never made the effort as virtually all units have a VT.

1 Like