New USA Install


#1

@overeasy

I just finished installing my first IoTaWatt. The install went well (I’ll post some pictures later.)

I have a question regarding the the “EmonService: Invalid configuration.” message below. I did click on the Setup -> Webserver menu, and selected the ‘Emoncms Add’ option, but then clicked CANCEL without entering any data. Afterwards, the following appeared in log.

I restarted the IoTaWatt, and at least the repeating error messages stopped. But there is still one “EmonService: Invalid configuration.” message during the startup. (see second restart below.) Is there any way to clear out the Invalid EmonService Configuration from the system?

** Restart **

SD initialized.
11/04/18 22:47:11z Real Time Clock is running. Unix time 1541371631 
11/04/18 22:47:11z Power failure detected.
11/04/18 22:47:11z Version 02_03_18
11/04/18 22:47:11z Reset reason: External System
11/04/18 22:47:11z Trace:  146:2[89], 106:149[158], 254:200[188], 254:224[133], 191:198[70], 52:194[11], 157:139[23], 124:94[107], 39:238[239], 180:193[253], 108:17[204], 123:22[59], 225:83[103], 127:144[244], 178:241[101], 69:90[76], 253:57[27], 17:100[249], 234:206[84], 6:3[107], 56:118[207], 212:23[189], 21:18[7], 56:56[9], 164:206[23], 205:69[162], 120:183[253], 212:151[216], 190:160[98], 206:69[220], 198:169[213], 64:137[27]
11/04/18 22:47:11z ESP8266 ChipID: 6911192
11/04/18 22:47:11z SPIFFS mounted.
11/04/18 18:47:12 EmonService: Invalid configuration.
11/04/18 18:47:12 Local time zone: -4
11/04/18 18:47:12 device name: IotaWatt, version: 3
11/04/18 18:47:15 MDNS responder started for hostname IotaWatt
11/04/18 18:47:15 LLMNR responder started for hostname IotaWatt
11/04/18 18:47:15 HTTP server started
11/04/18 18:47:15 timeSync: service started.
11/04/18 18:47:15 statService: started.
11/04/18 18:47:15 WiFi connected. SSID=PrivetDrive, IP=192.168.1.138, channel=1, RSSI -71db
11/04/18 18:47:15 Updater: service started. Auto-update class is MINOR
11/04/18 18:47:15 dataLog: service started.
11/04/18 18:47:15 dataLog: Last log entry 11/4/18 15:58:40 
11/04/18 18:47:15 historyLog: service started.
11/04/18 18:47:15 historyLog: Last log entry 11/4/18 15:58:00 
11/04/18 18:47:17 Updater: Auto-update is current for class MINOR.
11/04/18 18:47:20 influxDB: started, url=192.168.1.140:8086, db=IoTaWatt, interval=10
11/04/18 18:47:20 influxDB: Start posting at 11/4/18 15:58:40 
11/04/18 19:22:31 EmonService: Invalid configuration.
11/04/18 19:23:03 EmonService: Invalid configuration.
11/04/18 19:23:18 EmonService: Invalid configuration.
11/04/18 19:23:31 EmonService: Invalid configuration.
11/04/18 19:23:37 EmonService: Invalid configuration.
11/04/18 19:24:44 EmonService: Invalid configuration.
11/04/18 19:24:50 EmonService: Invalid configuration.
11/04/18 19:24:54 EmonService: Invalid configuration.
11/04/18 19:24:59 EmonService: Invalid configuration.
11/04/18 19:25:06 EmonService: Invalid configuration.
11/04/18 19:25:26 EmonService: Invalid configuration.
11/04/18 19:25:26 influxDB: Stopped. Last post 11/4/18 19:25:10 
11/04/18 19:34:25 EmonService: Invalid configuration.
11/04/18 19:35:28 EmonService: Invalid configuration.
11/04/18 19:36:07 EmonService: Invalid configuration.
11/04/18 19:36:19 EmonService: Invalid configuration.
11/04/18 19:36:49 EmonService: Invalid configuration.
11/04/18 19:37:35 EmonService: Invalid configuration.
11/04/18 19:38:00 EmonService: Invalid configuration.
11/04/18 19:38:43 EmonService: Invalid configuration.
11/04/18 19:40:32 EmonService: Invalid configuration.
11/04/18 19:46:15 EmonService: Invalid configuration.
11/04/18 19:46:37 EmonService: Invalid configuration.
11/04/18 19:46:58 EmonService: Invalid configuration.
11/04/18 19:59:44 EmonService: Invalid configuration.
11/04/18 20:07:02 EmonService: Invalid configuration.
11/04/18 20:07:16 EmonService: Invalid configuration.
11/04/18 20:08:10 EmonService: Invalid configuration.
11/04/18 20:35:02 EmonService: Invalid configuration.
11/04/18 20:35:25 EmonService: Invalid configuration.
11/04/18 20:35:36 EmonService: Invalid configuration.
11/04/18 20:36:04 EmonService: Invalid configuration.
11/04/18 20:36:47 EmonService: Invalid configuration.
11/04/18 20:37:29 EmonService: Invalid configuration.
11/04/18 20:37:59 EmonService: Invalid configuration.
11/04/18 20:38:10 EmonService: Invalid configuration.
11/04/18 20:38:28 EmonService: Invalid configuration.
11/04/18 20:38:48 EmonService: Invalid configuration.
11/04/18 20:39:07 EmonService: Invalid configuration.
11/04/18 20:39:23 EmonService: Invalid configuration.
11/04/18 20:44:40 EmonService: Invalid configuration.
11/04/18 20:44:54 EmonService: Invalid configuration.
11/04/18 20:45:10 EmonService: Invalid configuration.
11/04/18 20:45:18 EmonService: Invalid configuration.
11/04/18 20:45:28 EmonService: Invalid configuration.
11/04/18 20:45:40 EmonService: Invalid configuration.
11/04/18 20:57:50 EmonService: Invalid configuration.
11/04/18 20:59:59 EmonService: Invalid configuration.
11/04/18 21:01:25 EmonService: Invalid configuration.
11/04/18 21:01:29 EmonService: Invalid configuration.
11/04/18 21:01:33 EmonService: Invalid configuration.
11/04/18 21:01:37 EmonService: Invalid configuration.
11/04/18 21:01:40 EmonService: Invalid configuration.
11/04/18 21:30:08 Restart command received.

** Restart **

SD initialized.
11/05/18 01:30:11z Real Time Clock is running. Unix time 1541381411 
11/05/18 01:30:11z Version 02_03_18
11/05/18 01:30:11z Reset reason: Software/System restart
11/05/18 01:30:11z 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: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, 10:2, 10:3
11/05/18 01:30:11z ESP8266 ChipID: 6911192
11/05/18 01:30:11z SPIFFS mounted.
11/04/18 21:30:12 EmonService: Invalid configuration.
11/04/18 21:30:12 Local time zone: -4
11/04/18 21:30:12 device name: IotaWatt, version: 3
11/04/18 21:30:15 Connecting with WiFiManager.
11/04/18 21:30:18 MDNS responder started for hostname IotaWatt
11/04/18 21:30:18 LLMNR responder started for hostname IotaWatt
11/04/18 21:30:18 HTTP server started
11/04/18 21:30:18 timeSync: service started.
11/04/18 21:30:18 statService: started.
11/04/18 21:30:18 WiFi connected. SSID=PrivetDrive, IP=192.168.1.138, channel=7, RSSI -62db
11/04/18 21:30:18 Updater: service started. Auto-update class is MINOR
11/04/18 21:30:18 dataLog: service started.
11/04/18 21:30:18 dataLog: Last log entry 11/4/18 21:30:05 
11/04/18 21:30:18 historyLog: service started.
11/04/18 21:30:19 historyLog: Last log entry 11/4/18 21:30:00 
11/04/18 21:30:20 Updater: Auto-update is current for class MINOR.

#2

can you post your config.txt file?


#3

Here it is…

{
	"format": 2,
	"timezone": "-4",
	"update": "MINOR",
	"device": {
		"name": "IotaWatt",
		"version": 3,
		"channels": "15",
		"burden": [
			0,
			24,
			24,
			24,
			24,
			24,
			24,
			24,
			24,
			24,
			24,
			24,
			24,
			24,
			24
		]
	},
	"inputs": [
		{
			"channel": 0,
			"name": "Voltage",
			"type": "VT",
			"model": "TDC DA-10-09",
			"phase": 2.66,
			"cal": 11.23
		},
		{
			"channel": 1,
			"name": "SP_MainA",
			"type": "CT",
			"model": "ECS24200",
			"phase": 0.3,
			"turns": 4000,
			"cal": "166.7"
		},
		{
			"channel": 2,
			"name": "MstrBR_3rdFlr",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67",
			"reverse": true
		},
		{
			"channel": 3,
			"name": "PlayBath_DJO",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67",
			"reverse": true
		},
		{
			"channel": 4,
			"name": "Office_RJO",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67",
			"reverse": true
		},
		{
			"channel": 5,
			"name": "Micro_Freezer",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67",
			"reverse": true
		},
		{
			"channel": 6,
			"name": "LtsDwn_MRO",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67",
			"reverse": true
		},
		{
			"channel": 7,
			"name": "DW_Disposal",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67"
		},
		{
			"channel": 8,
			"name": "FmlyRm",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67"
		},
		{
			"channel": 9,
			"name": "FloodsBathOutdr",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67"
		},
		{
			"channel": 10,
			"name": "KitRec_LghtsDwn",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67"
		},
		{
			"channel": 11,
			"name": "WashMach",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67"
		},
		{
			"channel": 12,
			"name": "KitRec",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67"
		},
		{
			"channel": 13,
			"name": "Dryer",
			"type": "CT",
			"model": "ECOL09",
			"phase": 0.3,
			"turns": 1000,
			"cal": "41.67"
		},
		{
			"channel": 14,
			"name": "SP_MainB",
			"type": "CT",
			"model": "ECS24200",
			"phase": 0.3,
			"turns": 4000,
			"cal": "166.7"
		}
	],
	"outputs": [
		{
			"name": "Misc",
			"units": "Watts",
			"script": "@1+@14-@2-@3-@4-@5-@6-@7-@8-@9-@10-@11-@12-@13"
		},
		{
			"name": "Total",
			"units": "Watts",
			"script": "@1+@14"
		}
	],
	"server": {
		"type": "influxdb",
		"postInterval": 10,
		"bulksend": 1,
		"url": "http://192.168.1.140",
		"database": "IoTaWatt",
		"outputs": [
			{
				"name": "Input1",
				"units": "watts",
				"script": "@1"
			},
			{
				"name": "VT",
				"units": "volts",
				"script": "@0"
			}
		]
	}
}

#4

I can see the problem. No idea how that happened right now. If you upload the config.txt file, I’ll fix it and post it back.

Anything unusual happen when you tried to add influxDB service?


#5

Sorry for missing the obvious… How do i upload the config.txt file to you? I thought the copy/paste above was the file? Is there a way on the IoTaWatt web interface to copy a file to my PC? I can only see an option to upload a file from my PC to the IoTaWatt. (Update: Right Click on file, then choose Download.)

I initially had InfluxDB working fine for just one or two pieces of data going to a RPi running InfluxDB and Grafana. I have since moved those apps to my main Windows 10 home server. I did try to remove the old InfluxDB config from IoTaWatt to make sure it didn’t keep trying to connect to the old RPi server.


#6

I figured it out…

config.txt (2.9 KB)


#7

The file manager editor is nice. I developed the entire JS app right on the IoTaWatt.

Just to be clear, since I don’t fully understand what’s going on yet, your IoTaWatt is not currently posting to influx. The influx configuration is in a bad place. Do you want me to remove it or make it work?


#8

Remove it, please. I plan on adding a new one in the future, once I get everything working the way I want it to.


#9

Here you go.

config.txt (2.7 KB)

To install:
Download to your computer
In file manager, click the Choose File button in the upper left.
Browse to the downloaded file and open.
In file manager click the upload button at the top.

Now the file has replaced the old config.txt. The trick with this file is to make sure the app doesn’t save a new one before this one is loaded.

Go back to the config app.
Refresh it. This will load the new config into the app.
Now use tools-restart to restart the IoTaWatt.

That should do it. I’ll try to figure out what happened there, and if it looks like it could happen again, I’ll give you a shout.


#10

Thanks Bob! Your fix worked great! Loving the IoTaWatt! Thanks for all of your hard work on this product!

** Restart **

SD initialized.
11/05/18 03:19:13z Real Time Clock is running. Unix time 1541387953 
11/05/18 03:19:13z Version 02_03_18
11/05/18 03:19:13z Reset reason: Software/System restart
11/05/18 03:19:13z 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: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, 10:2, 10:3
11/05/18 03:19:13z ESP8266 ChipID: 6911192
11/05/18 03:19:13z SPIFFS mounted.
11/04/18 23:19:14 Local time zone: -4
11/04/18 23:19:14 device name: IotaWatt, version: 3
11/04/18 23:19:14 MDNS responder started for hostname IotaWatt
11/04/18 23:19:14 LLMNR responder started for hostname IotaWatt
11/04/18 23:19:14 HTTP server started
11/04/18 23:19:14 timeSync: service started.
11/04/18 23:19:15 statService: started.
11/04/18 23:19:15 WiFi connected. SSID=PrivetDrive, IP=192.168.1.138, channel=7, RSSI -63db
11/04/18 23:19:15 Updater: service started. Auto-update class is MINOR
11/04/18 23:19:15 dataLog: service started.
11/04/18 23:19:15 dataLog: Last log entry 11/4/18 23:19:10 
11/04/18 23:19:15 historyLog: service started.
11/04/18 23:19:15 historyLog: Last log entry 11/4/18 23:19:00 
11/04/18 23:19:16 Updater: Auto-update is current for class MINOR.

#11

Minor detail, time-zone is now -5.


#12

Here are some pictures of my installation in case you’re curious.