Continually resetting?

Hardware IoTaWatt
1

I think my IoTaWatt is continually resetting. Data stopped on the emonPi. I looked at the Status page and the Running time drops to 0h 0m 0s and the Inputs go to 0 and this repeats every five seconds. After 3 or 4 cycles the Status screen will freeze.

I can send you a movie of it happening but I don’t want to fill up the OEM server.

I was moving a CT from one circuit breaker to another and relabeling the inputs and outputs when this happened (the circuits were not live at the time). Restarting the iotawatt did not help. And powering down/up did not help.

No data is going to the emonPi.

Message Log:

** Restart **

No clock yet: SD initialized.
11/20/17 20:19:47 Real Time Clock is running. Unix time: 1511209187
11/20/17 20:19:47 Version: 02_02_26
11/20/17 20:19:47 Reset reason: Exception
11/20/17 20:19:47 Trace: 30,16,17,18,11,90,12,13,14,15,16,17,18,11,90,12,13,14,15,16,17,18,11,90,12,13,14,15,30,34,31,35
11/20/17 20:19:47 ESP8266 ChipID:451998
11/20/17 14:19:47 device name: IotaWatt, version: 3
11/20/17 14:19:47 Local time zone: -6
11/20/17 14:19:47 MDNS responder started
11/20/17 14:19:47 You can now connect to http://IotaWatt.local
11/20/17 14:19:47 HTTP server started
11/20/17 14:19:48 dataLog: service started.
11/20/17 14:19:48 dataLog: Last log entry:1511209185
11/20/17 14:19:48 statService: started.
11/20/17 14:19:48 timeSync: service started.
11/20/17 14:19:48 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:19:48 historyLog: service started.
11/20/17 14:19:48 historyLog: Last log entry:1511209140
11/20/17 14:19:53 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:19:53 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:19:53 Real Time Clock is running. Unix time: 1511209193
11/20/17 20:19:53 Version: 02_02_26
11/20/17 20:19:53 Reset reason: Exception
11/20/17 20:19:53 Trace: 30,16,17,18,11,90,12,13,14,15,16,17,18,11,90,12,13,14,15,16,17,18,11,90,12,13,14,15,30,34,31,35
11/20/17 20:19:53 ESP8266 ChipID:451998
11/20/17 14:19:53 device name: IotaWatt, version: 3
11/20/17 14:19:53 Local time zone: -6
11/20/17 14:19:55 MDNS responder started
11/20/17 14:19:55 You can now connect to http://IotaWatt.local
11/20/17 14:19:55 HTTP server started
11/20/17 14:19:55 dataLog: service started.
11/20/17 14:19:55 dataLog: Last log entry:1511209190
11/20/17 14:19:55 statService: started.
11/20/17 14:19:55 timeSync: service started.
11/20/17 14:19:55 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:19:55 historyLog: service started.
11/20/17 14:19:55 historyLog: Last log entry:1511209140
11/20/17 14:20:00 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:20:00 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:20:00 Real Time Clock is running. Unix time: 1511209200
11/20/17 20:20:00 Version: 02_02_26
11/20/17 20:20:00 Reset reason: Exception
11/20/17 20:20:00 Trace: 12,13,14,15,16,17,18,11,90,12,13,14,15,160,164,165,167,168,169,16,17,18,11,90,12,13,14,15,30,34,31,35
11/20/17 20:20:00 ESP8266 ChipID:451998
11/20/17 14:20:00 device name: IotaWatt, version: 3
11/20/17 14:20:00 Local time zone: -6
11/20/17 14:20:00 MDNS responder started
11/20/17 14:20:00 You can now connect to http://IotaWatt.local
11/20/17 14:20:00 HTTP server started
11/20/17 14:20:00 dataLog: service started.
11/20/17 14:20:01 dataLog: Last log entry:1511209200
11/20/17 14:20:01 statService: started.
11/20/17 14:20:01 timeSync: service started.
11/20/17 14:20:01 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:20:01 historyLog: service started.
11/20/17 14:20:01 historyLog: Last log entry:1511209200
11/20/17 14:20:05 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:20:05 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:20:05 Real Time Clock is running. Unix time: 1511209205
11/20/17 20:20:05 Version: 02_02_26
11/20/17 20:20:05 Reset reason: Exception
11/20/17 20:20:05 Trace: 14,15,16,17,18,11,90,12,13,14,15,16,17,18,11,90,91,84,86,88,93,94,95,99,12,13,14,15,30,34,31,35
11/20/17 20:20:05 ESP8266 ChipID:451998
11/20/17 14:20:05 device name: IotaWatt, version: 3
11/20/17 14:20:05 Local time zone: -6
11/20/17 14:20:07 MDNS responder started
11/20/17 14:20:07 You can now connect to http://IotaWatt.local
11/20/17 14:20:07 HTTP server started
11/20/17 14:20:07 dataLog: service started.
11/20/17 14:20:07 dataLog: Last log entry:1511209205
11/20/17 14:20:07 statService: started.
11/20/17 14:20:07 timeSync: service started.
11/20/17 14:20:07 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:20:07 historyLog: service started.
11/20/17 14:20:08 historyLog: Last log entry:1511209200
11/20/17 14:20:12 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:20:12 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:20:13 Real Time Clock is running. Unix time: 1511209213
11/20/17 20:20:13 Version: 02_02_26
11/20/17 20:20:13 Reset reason: Exception
11/20/17 20:20:13 Trace: 17,18,11,90,91,84,86,88,93,94,95,99,12,13,14,15,16,17,18,13,14,15,16,17,18,13,14,15,30,34,31,35
11/20/17 20:20:13 ESP8266 ChipID:451998
11/20/17 14:20:13 device name: IotaWatt, version: 3
11/20/17 14:20:13 Local time zone: -6
11/20/17 14:20:13 MDNS responder started
11/20/17 14:20:13 You can now connect to http://IotaWatt.local
11/20/17 14:20:13 HTTP server started
11/20/17 14:20:14 dataLog: service started.
11/20/17 14:20:14 dataLog: Last log entry:1511209210
11/20/17 14:20:14 statService: started.
11/20/17 14:20:14 timeSync: service started.
11/20/17 14:20:14 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:20:14 historyLog: service started.
11/20/17 14:20:14 historyLog: Last log entry:1511209200
11/20/17 14:20:19 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:20:19 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:20:19 Real Time Clock is running. Unix time: 1511209219
11/20/17 20:20:19 Version: 02_02_26
11/20/17 20:20:19 Reset reason: Exception
11/20/17 20:20:19 Trace: 30,16,17,18,11,90,12,13,14,15,16,17,18,11,90,12,13,14,15,16,17,18,11,90,12,13,14,15,30,34,31,35
11/20/17 20:20:19 ESP8266 ChipID:451998
11/20/17 14:20:19 device name: IotaWatt, version: 3
11/20/17 14:20:19 Local time zone: -6
11/20/17 14:20:19 MDNS responder started
11/20/17 14:20:19 You can now connect to http://IotaWatt.local
11/20/17 14:20:19 HTTP server started
11/20/17 14:20:19 dataLog: service started.
11/20/17 14:20:20 dataLog: Last log entry:1511209215
11/20/17 14:20:20 statService: started.
11/20/17 14:20:20 timeSync: service started.
11/20/17 14:20:20 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:20:20 historyLog: service started.
11/20/17 14:20:20 historyLog: Last log entry:1511209200
11/20/17 14:20:24 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:20:24 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:20:24 Real Time Clock is running. Unix time: 1511209224
11/20/17 20:20:24 Version: 02_02_26
11/20/17 20:20:24 Reset reason: Exception
11/20/17 20:20:24 Trace: 17,18,11,90,91,84,86,88,93,94,95,99,12,13,14,15,16,17,18,13,14,15,16,17,18,13,14,15,30,34,31,35
11/20/17 20:20:24 ESP8266 ChipID:451998
11/20/17 14:20:24 device name: IotaWatt, version: 3
11/20/17 14:20:24 Local time zone: -6
11/20/17 14:20:24 MDNS responder started
11/20/17 14:20:24 You can now connect to http://IotaWatt.local
11/20/17 14:20:24 HTTP server started
11/20/17 14:20:24 dataLog: service started.
11/20/17 14:20:25 dataLog: Last log entry:1511209220
11/20/17 14:20:25 statService: started.
11/20/17 14:20:25 timeSync: service started.
11/20/17 14:20:25 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:20:25 historyLog: service started.
11/20/17 14:20:25 historyLog: Last log entry:1511209200
11/20/17 14:20:29 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:20:29 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:20:29 Real Time Clock is running. Unix time: 1511209229
11/20/17 20:20:29 Version: 02_02_26
11/20/17 20:20:29 Reset reason: Exception
11/20/17 20:20:29 Trace: 17,18,11,90,91,84,86,88,93,94,95,99,12,13,14,15,16,17,18,13,14,15,16,17,18,13,14,15,30,34,31,35
11/20/17 20:20:29 ESP8266 ChipID:451998
11/20/17 14:20:29 device name: IotaWatt, version: 3
11/20/17 14:20:29 Local time zone: -6
11/20/17 14:20:29 MDNS responder started
11/20/17 14:20:29 You can now connect to http://IotaWatt.local
11/20/17 14:20:29 HTTP server started
11/20/17 14:20:29 dataLog: service started.
11/20/17 14:20:30 dataLog: Last log entry:1511209225
11/20/17 14:20:30 statService: started.
11/20/17 14:20:30 timeSync: service started.
11/20/17 14:20:30 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139
11/20/17 14:20:30 historyLog: service started.
11/20/17 14:20:30 historyLog: Last log entry:1511209200
11/20/17 14:20:34 EmonService: started.url: 192.168.60.230:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
11/20/17 14:20:34 EmonService: Start posting from 1511206370

** Restart **

No clock yet: SD initialized.
11/20/17 20:20:34 Real Time Clock is running. Unix time: 1511209234
11/20/17 20:20:34 Version: 02_02_26
11/20/17 20:20:34 Reset reason: Exception
11/20/17 20:20:34 Trace: 17,18,11,90,91,84,86,88,93,94,95,99,12,13,14,15,16,17,18,13,14,15,16,17,18,13,14,15,30,34,31,35
11/20/17 20:20:34 ESP8266 ChipID:451998
11/20/17 14:20:34 device name: IotaWatt, version: 3
11/20/17 14:20:34 Local time zone: -6
11/20/17 14:20:36 MDNS responder started
11/20/17 14:20:36 You can now connect to http://IotaWatt.local
11/20/17 14:20:36 HTTP server started
11/20/17 14:20:36 dataLog: service started.
11/20/17 14:20:36 dataLog: Last log entry:1511209230
11/20/17 14:20:36 statService: started.
11/20/17 14:20:36 timeSync: service started.
11/20/17 14:20:36 WiFi connected. SSID: GizmoWL2, IP: 192.168.60.139

Pic 1:

33 PM
33 PM1456×1424 427 KB

Pic 2:
49 PM
49 PM1456×1424 422 KB

pic 3:
00 PM
00 PM1456×1424 423 KB

pic 4:
24 PM
24 PM1456×1424 427 KB

pic 5:
34 PM
34 PM1456×1424 423 KB

2

When you say the circuits were not live at the time, I’m assuming the IoTaWatt was running.

The trace shows that it is taking an exception while preparing a data packet for Emoncms. There is the possibility that you have damaged the op-amp.

If it stays up long enough to run the config app, setting server to NONE should give you some relief from the resets. If you can’t stop it through the config app, then you will need to power it down, remove the SD card, and edit the config file to stop the Emoncms Service from starting. I’ll work with you to get this done, but first try to stop it using the config app.

3

Ugh! I think I figured it out - a cockpit error on my part!

I wandered into the Setup Web Server page and had made a change to the Configuration Output Name. I thought I had cancelled out of it but I had not (the Name was changed from 1 to V1). Once I changed the Configuration Output Name back to 1 everything took off and started working again.

59 PM
59 PM1472×2120 257 KB

I am curious - are the Names on this page never to be touched?!?

33 PM
33 PM1472×1728 242 KB

4

Whew! I was imagining the worse. I do have development code that senses continual reboots and an working on code to boot it up in “emergency mode” with minimal Services, just the web server so diagnostics can be run. That’s a ways off.

To answer your question about the Emoncms output names, they must be integers between 1 and 15. The protocol that IoTaWatt uses to post to Emoncms passes the data prepositionally in an array, so the number indicates the position in the array, as well as matches the numerical “key” that is associated with each input on the node.

But the naming convention should be taken care of with the regular-expression that checks the name. So whatever is going on there, it’s a bug, and I’ve noted it. Not sure I can recreate it, but I’ll definitely review the name checking enforcement.

The latest version of the app also does not allow you to leave without saving or cancelling.

EDIT: Judging by where the exception was occurring and this new info about the naming, It is most probably a problem with the script associated with that channel, and it was fixed when you saved the config. This is not the first time corrupted scripts have caused problems, so I guess I’ll have to make that more bulletproof.