Non-specific problem post

hello Bob,

long time not write here:

SD initialized.
1/05/22 16:19:27z Real Time Clock is running. Unix time 1641399567
1/05/22 16:19:27z Reset reason: Software/System restart
1/05/22 16:19:27z Trace: 1:1[3], 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:3, 1:6[1], 1:6[2], 1:6[2], 1:6[3], 1:5[21], 1:6[4], 21:0, 21:1, 21:10, 21:20, 21:21, 21:30, 21:99, 1:6[6], 1:3, 10:2, 10:3
1/05/22 16:19:27z ESP8266 ID: 2518253, RTC PCF8523 (68)
1/05/22 16:19:27z IoTaWatt 4.x, Firmware version 02_07_05
1/05/22 16:19:27z SPIFFS mounted.
1/05/22 18:19:27 Local time zone: +2:00, using DST/BST when in effect.
1/05/22 18:19:27 device name: IotaWatt
1/05/22 18:19:27 HTTP server started
1/05/22 18:19:27 influxDB_v1: Starting, interval:5, url:
1/05/22 18:19:27 timeSync: service started.
1/05/22 18:19:27 statService: started.
1/05/22 18:19:28 dataLog: service started.
1/05/22 18:19:30 dataLog: Last log entry 01/05/22 18:19:25
1/05/22 18:19:32 historyLog: service started.
1/05/22 18:19:32 historyLog: Last log entry 01/05/22 18:19:00
1/05/22 18:19:32 WiFi connected. SSID=Etaj, IP=, channel=11, RSSI -59db
1/05/22 18:19:32 MDNS responder started for hostname IotaWatt
1/05/22 18:19:32 LLMNR responder started for hostname IotaWatt
1/05/22 18:19:32 Updater: service started. Auto-update class is ALPHA
1/05/22 18:19:33 influxDB_v1: Authentication failed. Stopping influx service.
1/05/22 18:19:33 influxDB_v1: stopped, Last post 01/01/70 02:00:00
1/05/22 18:19:34 Updater: Auto-update is current for class ALPHA.
1/05/22 20:20:04 emoncms: Starting, interval:5, url:
1/05/22 20:20:04 emoncms: No existing inputs found for node IotaWatt.
1/05/22 20:20:04 emoncms: Start posting at 01/05/22 00:00:05
1/05/22 20:20:29 emoncms: stopped, Last post 01/05/22 00:36:00
1/05/22 20:40:40 emoncms: Start posting at 01/05/22 00:36:05
1/05/22 20:41:43 emoncms: stopped, Last post 01/05/22 02:06:00
1/05/22 20:42:42 emoncms: No existing inputs found for node IotaWatt.
1/05/22 20:42:42 emoncms: Start posting at 01/05/22 00:00:05
1/05/22 20:49:38 emoncms: stopped, Last post 01/05/22 05:20:45
1/05/22 21:00:06 emoncms: No existing inputs found for node IotaWatt.
1/05/22 21:00:06 emoncms: Start posting at 01/05/22 00:00:05
1/05/22 21:07:31 emoncms: stopped, Last post 01/05/22 11:55:55
1/05/22 21:13:34 emoncms: Start posting at 01/05/22 00:00:05
1/05/22 21:19:09 emoncms: stopped, Last post 01/05/22 08:23:15
1/05/22 21:25:56 emoncms: Start posting at 01/05/22 08:23:20
1/05/22 21:27:21 emoncms: stopped, Last post 01/05/22 10:12:15
1/05/22 21:28:00 emoncms: Start posting at 01/05/22 10:12:20
1/30/22 20:19:28 Updater: Invalid response from server. HTTPcode: -4
2/16/22 18:20:34 timeSync: Six week routine restart.
can t acces any graph: no Graph +, no original Graph
even a restart don t help
how we can solve it?

Don’t see a problem here. Are you saying that is the end of the message log? That the unit initiated the six week restart and never restarted? How did you access the message log?

hello Bob,

in fact, every time when i need to see/work in Graph+ or Original Graph, is not apear nothing in browser - take a long times/ minutes and remain x.x.x.x/graph2htm in browser and nothing apear; all another options of the IOTAWATT menu are OK, working , except the fact that can t go insite Graph+ or Original graph. I can work in any option of Iotawatt menu except Graph …
Switch between several browsers, and nothing change; after several restart and long time waiting,everything is working again, can t explain what it was happened.

Can you post your status display with all tabs expanded please?

This is an interesting case. You originally posted this in a thread where the problem reported where the root file, index.htm, was not found. Here, you report having trouble with Graph+ but seem to be able to access index.htm. There are a couple of things I’d like you to try:

Can you access the file manager?

If you can access the file manager, if you click on graph2.htm does the contents appear in the editor window? How about other files in the root directory?

just read your replay; i will return in this afternoon with more data.
thank you,

back in picture:

  1. it was by instinct to post in another specific area…sorry for my mistake. was just Graph+ and Original Graph that was not working when is hapenned the situation. All anothers from meniu was working OK.
    3.all files from root directory can be accesed at that time that time I don t perform click on the grapf.htm2, but actualy is showing the content if a do this action.
    just now, after more time, everything is OK.

OK, transient problem. One question is whether it may be related to a specific plot and if it might have something to do with a corruption in your datalog. I’ll take this opportunity to post some observations about this case:

This is quite an older unit. It has been running for more than three years. During that time, several problems with datalog resiliency to power failures were identified and also newer stategies were developed that very significantly reduce SDcard wear by minimizing write operations. These changes have been worked into the release stream and any unit that subscribes to auto-update has benefitted from them.

But while damage can be minimized going forward, there are a few things that can be done about wear or damage that occurred in the past.

Some SDcards have wear leveling firmware that remaps sectors with excessive write history. Consumers have little visibility into the presence or effectiveness of technology and the techniques vary by manufacturer. Older units were subjected to a lot more writes. The cards in those units were 4GB, and when the datalogs grow, there is a lot less space to remap. For the past couple of years new units have 8GB cards for just that reason.

For peace of mind, units with 4GB SDcards older than two to three years might consider upgrading to an 8GB level 10 microSD card. All you need to do is get a new card and copy the complete contents of your current card to the new. Read this post for information on removing your SDcard. Understand that there is some risk of damaging your existing card so consider that and be careful if you do so.

Most of the issues found in older SDcards were with the current log. That log contains only the most recent years’ worth of 5 second data. By now, even an older card will have overwritten any older power-fail type errors in the current log and it should be OK. The history log is another story. It will not wrap for ten years and, while much less volatile, may have errors in the early data. Should that be suspected, the history log can be deleted and it will be rebuilt for the most recent year using data from the current log.

clear understood .
I will proced acording with your path and return when in done.

thank you,

Hello Bob,

Love the device. I used it to show the electric company the new smart meter they installed was overcharging customers.

I am having the same problem and it started a couple days ago. Whenever I click on graph or graph+, the device reboots. I followed the directions above and opened file manager and I can click on some of the files but others cause a reboot, specifically graph.htm and graph2.htm. I downloaded the files from Git and uploaded them over the existing ones and that fixed the problem. My device is just under three years old. Would you recommend replacing the SD card with a newer one? Is there anymore troubleshooting I can do to see what caused the corruption? The log files show less than what is listed by the original post.

Thanks in advance.

I would recommend replacing a three year old card with a new one. If you copy the card, you should not lose any data.