InfluxDBV1 uploader issues

[HomeAlone]

My location has very poor power. Frequent power outages and possible weird sinus waves. In any case once in a while the InfluxDB uploader gets stuck on a datapoint that in effect not only stops uploading but also starts a rebooting every 30 seconds or so.
6/15/22 01:39:23z Reset reason: Software Watchdog
The only way to solve this is by manually editing the config.txt to set influxdb uploader to stop. Then set the “upload from” an hour or so ahead. And start the uploader.

I don’t see this problem in the Iotawatt graphs. I guess it skips bad data. The Influxdb uploader does not have the same error handling abilities I guess.
Firmware 02.07.05

[overeasy]

Next time that happens, can you get a screenshot of the status display with all tabs expanded and post that along with the message log?

[arghhh40k]

I am having the same issue. Set up tags for my influx data and started a new DB for it. It was uploading backlog fine and it stopped and got the reboot loop. I managed to stop the influx before it rebooted itself again. Here is the screenshot.

6/22/22 13:39:51z ESP8266 ID: 560729, RTC M41T81 (68)
6/22/22 13:39:51z IoTaWatt 5.0, Firmware version 02_07_05
6/22/22 13:39:51z SPIFFS mounted.
6/22/22 10:39:51 Local time zone: -4:00, using DST/BST when in effect.
6/22/22 10:39:51 device name: IotaWatt
6/22/22 10:39:51 HTTP server started
6/22/22 10:39:51 influxDB_v1: Starting, interval:5, url:http://192.168.1.253:8086
6/22/22 10:39:51 timeSync: service started.
6/22/22 10:39:51 statService: started.
6/22/22 10:39:52 dataLog: service started.
6/22/22 10:39:52 dataLog: Last log entry 06/22/22 10:39:45
6/22/22 10:39:55 WiFi connected. SSID=Blackbeard, IP=192.168.1.227, channel=11, RSSI -53db
6/22/22 10:39:55 MDNS responder started for hostname IotaWatt
6/22/22 10:39:55 LLMNR responder started for hostname IotaWatt
6/22/22 10:39:55 Updater: service started. Auto-update class is MINOR
6/22/22 10:39:56 historyLog: service started.
6/22/22 10:39:56 historyLog: Last log entry 06/22/22 10:39:00
6/22/22 10:39:56 Updater: Auto-update is current for class MINOR.
6/22/22 10:39:57 influxDB_v1: Start posting at 06/01/22 00:15:00

** Restart **

SD initialized.
6/22/22 13:40:01z Real Time Clock is running. Unix time 1655905201 
6/22/22 13:40:01z Reset reason: Software Watchdog
6/22/22 13:40:01z Trace:  32:60, 32:60, 32:60, 32:62, 32:63, 31:1, 1:6[6], 1:1[7], 1:2[8], 9:0[8], 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[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[3], 32:60, 32:60, 32:60
6/22/22 13:40:01z ESP8266 ID: 560729, RTC M41T81 (68)
6/22/22 13:40:01z IoTaWatt 5.0, Firmware version 02_07_05
6/22/22 13:40:01z SPIFFS mounted.
6/22/22 10:40:01 Local time zone: -4:00, using DST/BST when in effect.
6/22/22 10:40:01 device name: IotaWatt
6/22/22 10:40:01 HTTP server started
6/22/22 10:40:01 influxDB_v1: Starting, interval:5, url:http://192.168.1.253:8086
6/22/22 10:40:01 timeSync: service started.
6/22/22 10:40:01 statService: started.
6/22/22 10:40:02 dataLog: service started.
6/22/22 10:40:02 dataLog: Last log entry 06/22/22 10:39:55
6/22/22 10:40:06 historyLog: service started.
6/22/22 10:40:06 historyLog: Last log entry 06/22/22 10:39:00
6/22/22 10:40:07 WiFi connected. SSID=Blackbeard, IP=192.168.1.227, channel=11, RSSI -52db
6/22/22 10:40:07 MDNS responder started for hostname IotaWatt
6/22/22 10:40:07 LLMNR responder started for hostname IotaWatt
6/22/22 10:40:07 Updater: service started. Auto-update class is MINOR
6/22/22 10:40:08 Updater: Auto-update is current for class MINOR.
6/22/22 10:40:08 influxDB_v1: Start posting at 06/01/22 00:15:00

** Restart **

SD initialized.
6/22/22 13:40:12z Real Time Clock is running. Unix time 1655905212 
6/22/22 13:40:12z Reset reason: Software Watchdog
6/22/22 13:40:12z Trace:  32:60, 32:60, 32:60, 32:62, 32:63, 31:1, 1:6[6], 1:1[11], 1:2[12], 9:0[12], 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[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[3], 32:60, 32:60, 32:60
6/22/22 13:40:12z ESP8266 ID: 560729, RTC M41T81 (68)
6/22/22 13:40:12z IoTaWatt 5.0, Firmware version 02_07_05
6/22/22 13:40:12z SPIFFS mounted.
6/22/22 10:40:12 Local time zone: -4:00, using DST/BST when in effect.
6/22/22 10:40:12 device name: IotaWatt
6/22/22 10:40:12 HTTP server started
6/22/22 10:40:12 influxDB_v1: Starting, interval:5, url:http://192.168.1.253:8086
6/22/22 10:40:12 timeSync: service started.
6/22/22 10:40:12 statService: started.
6/22/22 10:40:13 dataLog: service started.
6/22/22 10:40:13 dataLog: Last log entry 06/22/22 10:40:05
6/22/22 10:40:17 historyLog: service started.
6/22/22 10:40:17 historyLog: Last log entry 06/22/22 10:40:00
6/22/22 10:40:17 WiFi connected. SSID=Blackbeard, IP=192.168.1.227, channel=11, RSSI -52db
6/22/22 10:40:17 MDNS responder started for hostname IotaWatt
6/22/22 10:40:17 LLMNR responder started for hostname IotaWatt
6/22/22 10:40:17 Updater: service started. Auto-update class is MINOR
6/22/22 10:40:18 Updater: Auto-update is current for class MINOR.
6/22/22 10:40:18 influxDB_v1: Start posting at 06/01/22 00:15:00

** Restart **

SD initialized.
6/22/22 13:40:22z Real Time Clock is running. Unix time 1655905222 
6/22/22 13:40:22z Reset reason: Software Watchdog
6/22/22 13:40:22z Trace:  1:6[4], 31:0, 31:1, 31:2[3], 32:60, 32:60, 32:60, 32:62, 32:63, 31:1, 1:6[6], 1:1[14], 1:2, 9:0, 9:0, 8:4, 8:6, 8:8, 8:9, 1:2, 1:3, 1:3, 1:6[1], 1:6[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[3], 32:60, 32:60, 32:60
6/22/22 13:40:22z ESP8266 ID: 560729, RTC M41T81 (68)
6/22/22 13:40:22z IoTaWatt 5.0, Firmware version 02_07_05
6/22/22 13:40:22z SPIFFS mounted.
6/22/22 10:40:22 Local time zone: -4:00, using DST/BST when in effect.
6/22/22 10:40:22 device name: IotaWatt
6/22/22 10:40:22 HTTP server started
6/22/22 10:40:22 influxDB_v1: Starting, interval:5, url:http://192.168.1.253:8086
6/22/22 10:40:22 timeSync: service started.
6/22/22 10:40:22 statService: started.
6/22/22 10:40:23 dataLog: service started.
6/22/22 10:40:23 dataLog: Last log entry 06/22/22 10:40:15
6/22/22 10:40:26 WiFi connected. SSID=Blackbeard, IP=192.168.1.227, channel=11, RSSI -54db
6/22/22 10:40:26 MDNS responder started for hostname IotaWatt
6/22/22 10:40:26 LLMNR responder started for hostname IotaWatt
6/22/22 10:40:26 Updater: service started. Auto-update class is MINOR
6/22/22 10:40:27 historyLog: service started.
6/22/22 10:40:27 historyLog: Last log entry 06/22/22 10:40:00
6/22/22 10:40:27 Updater: Auto-update is current for class MINOR.
6/22/22 10:40:28 influxDB_v1: Start posting at 06/01/22 00:15:00

** Restart **

SD initialized.
6/22/22 13:40:32z Real Time Clock is running. Unix time 1655905232 
6/22/22 13:40:32z Reset reason: Software Watchdog
6/22/22 13:40:32z Trace:  32:60, 32:60, 32:60, 32:62, 32:63, 31:1, 1:6[6], 1:1[2], 1:2[3], 9:0[3], 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[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[3], 32:60, 32:60, 32:60
6/22/22 13:40:32z ESP8266 ID: 560729, RTC M41T81 (68)
6/22/22 13:40:32z IoTaWatt 5.0, Firmware version 02_07_05
6/22/22 13:40:32z SPIFFS mounted.
6/22/22 10:40:32 Local time zone: -4:00, using DST/BST when in effect.
6/22/22 10:40:32 device name: IotaWatt
6/22/22 10:40:32 HTTP server started
6/22/22 10:40:32 influxDB_v1: Starting, interval:5, url:http://192.168.1.253:8086
6/22/22 10:40:32 timeSync: service started.
6/22/22 10:40:32 statService: started.
6/22/22 10:40:33 dataLog: service started.
6/22/22 10:40:33 dataLog: Last log entry 06/22/22 10:40:25
6/22/22 10:40:37 historyLog: service started.
6/22/22 10:40:37 historyLog: Last log entry 06/22/22 10:40:00
6/22/22 10:40:38 WiFi connected. SSID=Blackbeard, IP=192.168.1.227, channel=11, RSSI -53db
6/22/22 10:40:38 MDNS responder started for hostname IotaWatt
6/22/22 10:40:38 LLMNR responder started for hostname IotaWatt
6/22/22 10:40:38 Updater: service started. Auto-update class is MINOR
6/22/22 10:40:40 Updater: Auto-update is current for class MINOR.

** Restart **

SD initialized.
6/22/22 13:40:41z Real Time Clock is running. Unix time 1655905241 
6/22/22 13:40:41z Reset reason: Exception
6/22/22 13:40:41z Trace:  32:35, 32:35, 32:35, 32:35, 32:37, 31:1, 1:6[6], 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[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[1], 32:20, 32:20, 32:20
6/22/22 13:40:41z ESP8266 ID: 560729, RTC M41T81 (68)
6/22/22 13:40:41z IoTaWatt 5.0, Firmware version 02_07_05
6/22/22 13:40:41z SPIFFS mounted.
6/22/22 10:40:41 Local time zone: -4:00, using DST/BST when in effect.
6/22/22 10:40:41 device name: IotaWatt
6/22/22 10:40:41 HTTP server started
6/22/22 10:40:41 influxDB_v1: Starting, interval:5, url:http://192.168.1.253:8086
6/22/22 10:40:41 timeSync: service started.
6/22/22 10:40:41 statService: started.
6/22/22 10:40:42 dataLog: service started.
6/22/22 10:40:42 dataLog: Last log entry 06/22/22 10:40:40
6/22/22 10:40:45 WiFi connected. SSID=Blackbeard, IP=192.168.1.227, channel=11, RSSI -54db
6/22/22 10:40:45 MDNS responder started for hostname IotaWatt
6/22/22 10:40:45 LLMNR responder started for hostname IotaWatt
6/22/22 10:40:45 Updater: service started. Auto-update class is MINOR
6/22/22 10:40:46 historyLog: service started.
6/22/22 10:40:46 historyLog: Last log entry 06/22/22 10:40:00
6/22/22 10:40:47 Updater: Auto-update is current for class MINOR.

** Restart **

SD initialized.
6/22/22 13:40:48z Real Time Clock is running. Unix time 1655905248 
6/22/22 13:40:48z Reset reason: Exception
6/22/22 13:40:48z Trace:  31:91, 31:9, 31:1, 1:6[6], 1:3, 1:3, 1:6[1], 1:6[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[2], 32:30, 32:35, 32:35, 32:35, 32:35, 32:37, 31:1, 1:6[6], 1:3, 1:3, 1:6[1], 1:6[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[1], 32:20, 32:20
6/22/22 13:40:48z ESP8266 ID: 560729, RTC M41T81 (68)
6/22/22 13:40:48z IoTaWatt 5.0, Firmware version 02_07_05
6/22/22 13:40:48z SPIFFS mounted.
6/22/22 10:40:48 Local time zone: -4:00, using DST/BST when in effect.
6/22/22 10:40:48 device name: IotaWatt
6/22/22 10:40:48 HTTP server started
6/22/22 10:40:48 influxDB_v1: Starting, interval:5, url:http://192.168.1.253:8086
6/22/22 10:40:48 timeSync: service started.
6/22/22 10:40:48 statService: started.
6/22/22 10:40:49 dataLog: service started.
6/22/22 10:40:49 dataLog: Last log entry 06/22/22 10:40:45
6/22/22 10:40:53 historyLog: service started.
6/22/22 10:40:53 historyLog: Last log entry 06/22/22 10:40:00
6/22/22 10:40:53 WiFi connected. SSID=Blackbeard, IP=192.168.1.227, channel=11, RSSI -53db
6/22/22 10:40:53 MDNS responder started for hostname IotaWatt
6/22/22 10:40:53 LLMNR responder started for hostname IotaWatt
6/22/22 10:40:53 Updater: service started. Auto-update class is MINOR
6/22/22 10:40:53 Updater: Auto-update is current for class MINOR.
6/22/22 10:40:54 influxDB_v1: stopped, Last post 06/01/22 00:14:55

[arghhh40k]

@overeasy

I am also getting some random high values logged to grafana, such as yottawatts.

[overeasy]

IoTaWatt doesn’t upload to Grafana, that would most likely be bad data in influxDB. The restarts appear to be caused by damage to the datalogs. That would also be the most likely cause of the YottaWatts.

Unfortunately, the only way to correct this is to delete both datalogs and start fresh. To do that enter this command into your browser:

http://iotawatt.local/command?deletelog=both

As an aside, you have your timezone set to -4 and it doesn’t seem to match your browser timezone which appears to be -5 (Eastern time). That’s why your status display shows the last influx upload at 5/31/2022 11:14:55 and the message log shows the next post at 6/1/2022 00:15:00.

[arghhh40k]

I am using influx v1 to upload to influx and grafana to view the data.

The yotta watts was yesterday and sort of unrelated to the issue with backfilling the logs but the damage may still be the culprit.

I will wipe the logs and start over.

I had a few random outages, could that have damaged the logs?

The time zone was a case of doing too much at one time and trying to update my timezone when taking screenshots and has since been fixed.

[overeasy]

@arghhh40k

I had a few random outages, could that have damaged the logs?

Outages happen all the time, that’s business as usual. Datalog damage is pretty rare these days. If you want to follow up before deleting the logs, try graphing the period between May 31 23:00 and June 1 01:00 and capture the CSV.

[arghhh40k]

That ship sailed, did a reset and so far it’s been great with no issues. Thank you for the support.

[arghhh40k]

@overeasy
Ended up with another weird blip pushed to influx 1.8 between KW, MW and YW depending on what graph it hit.

The Graph+ does not show it.

How can I verify the uploader is sending the correct data?

[overeasy]

You can see what IoTaWatt data is by looking at the CSV with a timeframe that yields 5 second intervals (<= 1hr).

[arghhh40k]

It looks like IotaWatt collected some poor data.

[overeasy]

Can you add voltage and plot 1am to 2am?

[arghhh40k]

I can’t seem to add voltage. It is now resetting the device every time I try to graph it. What I did see before it crashed was what looked like a huge voltage spike being measured. It looked like a negative value.

[overeasy]

Do you have the VT on a UPS?

Can I see a picture of your IoTaWatt installation?

[arghhh40k]

The VT and Iotawatt power adapter is on a receptacle installed right from the panel. I do have a UPS but it’s downstream and feeds a different subpanel.

The CTs go to the main panel and a few circuits in the UPS subpanel. I know some of the UPS subpanel circuits will be slightly off due to the UPS output voltage being regulated but it’s understood and not a concern.

[overeasy]

Can you zoom out so I can see the main1 CT, and can you tell me how many inputs exhibited this spike at that time?

[arghhh40k]

It looked like 3 inputs but it seemed it was only Leg 1 of 240v inputs that got hit.

Main 1
Garage 1
AC 1

[overeasy]

I don’t see the spike on Main1, but do see it on garage and AC1. Can you reproduce the graph with CSV using a timeframe of less than an hour so the CSV is 5 second intervals?

[arghhh40k]

Is there a way to get this data other than the graph? If I go below 2m resolution it reboots the iotawatt. It seems like the log is corrupted again.

[overeasy]

Graph+ uses query. It’s the datalog. I think it’s time to replace the SDcard. What was your order number?