WiFi drops off requires restart - Resolved

Support
1

Got my IoTaWatt installed last week (along with a full set off ECOL09 CTs) and it’s day to day usage is working great, logging to both local InfluxDB and local EmonCMS.

Every now and then though, the wifi appears to just drop out and it doesn’t try and reconnect? When this happens I can no longer ping the device, and I have to power cycle the unit to get it to come back on the wifi. When it comes back it starts submitting all the data that it collected while it was disconnected, so I don’t actually lose any data, I just don’t have realtime info.

I’m relatively sure the WiFi is all good as I have heaps of other ESP8266 IoT devices that are maintaining wifi to the same AP during the periods that the IoTaWatt is disconnecting, and some of these are in the same general area as the IoTaWatt.

The system logs aren’t giving anything away:

SD initialized.
2/23/19 10:15:09z Real Time Clock is running. Unix time 1550916909 
2/23/19 10:15:09z Reset reason: Hardware Watchdog
2/23/19 10:15:09z Trace:  8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[3], 3:0, 3:9, 3:9, 3:9, 3:9, 3:9, 15:1, 15:0, 15:1, 15:0, 15:1, 3:10, 3:10, 3:10, 3:10, 1:6, 1:1[2], 1:2[3], 9:0[3], 9:0, 9:1
2/23/19 10:15:09z ESP8266 ChipID: 2330070
2/23/19 10:15:09z IoTaWatt revision 4.8, firmware version 02_03_21
2/23/19 10:15:09z SPIFFS mounted.
2/23/19 22:15:10 Local time zone: +12:00
2/23/19 22:15:10 device name: IotaWatt
2/23/19 22:15:10 MDNS responder started for hostname IotaWatt
2/23/19 22:15:10 LLMNR responder started for hostname IotaWatt
2/23/19 22:15:10 HTTP server started
2/23/19 22:15:10 timeSync: service started.
2/23/19 22:15:11 statService: started.
2/23/19 22:15:11 dataLog: service started.
2/23/19 22:15:11 dataLog: Last log entry 02/23/19 22:15:00
2/23/19 22:15:12 historyLog: service started.
2/23/19 22:15:12 historyLog: Last log entry 02/23/19 22:15:00
2/23/19 22:15:15 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/23/19 22:15:15 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/23/19 22:15:15 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -77db
2/23/19 22:15:15 Updater: service started. Auto-update class is MINOR
2/23/19 22:15:16 EmonService: Start posting at 02/23/19 22:15:00
2/23/19 22:15:17 Updater: Auto-update is current for class MINOR.
2/23/19 22:15:18 influxDB: Start posting at 02/23/19 22:14:50
2/25/19 04:35:59 EmonService: HTTP response -4, retrying.
2/25/19 04:44:38 influxDB: Post Failed: -4
2/25/19 05:18:38 Updater: Invalid response from server. HTTPcode: -4

It’s the last three lines that seem to be consistent. Basically it fails to post any updates, and then it fails to check for any IoTaWatt updates, and then it does nothing…

I couldn’t see any obvious WiFi setting, is there anything locally on the device I could try?

2

Coul$ you post the full message log since this started happening? This log is only half of the story, the rest is in the state detected on restart, and I’d look at all of these failures and restarts.
Also, next time it happens, note the state of the LED before restarting.

3

The LED appears to be flashing green (which I am assuming is as per normal) prior to restart. The first time it happened I just assumed a power lead had come out.

Larger log (am away from home now, can get more later if there should be more):

2/18/19 23:57:18 EmonService: HTTP response -4, retrying.
2/19/19 00:05:56 influxDB: Post Failed: -4
2/19/19 00:22:48 Updater: Invalid response from server. HTTPcode: -4

** Restart **

SD initialized.
2/19/19 08:03:37z Real Time Clock is running. Unix time 1550563417 
2/19/19 08:03:37z Power failure detected.
2/19/19 08:03:37z Reset reason: External System
2/19/19 08:03:37z ESP8266 ChipID: 2330070
2/19/19 08:03:37z IoTaWatt revision 4.8, firmware version 02_03_21
2/19/19 08:03:37z SPIFFS mounted.
2/19/19 20:03:38 Local time zone: +12:00
2/19/19 20:03:38 device name: IotaWatt
2/19/19 20:03:41 Connecting with WiFiManager.
2/19/19 20:03:48 MDNS responder started for hostname IotaWatt
2/19/19 20:03:48 LLMNR responder started for hostname IotaWatt
2/19/19 20:03:48 HTTP server started
2/19/19 20:03:48 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -78db
2/19/19 20:03:48 timeSync: service started.
2/19/19 20:03:51 statService: started.
2/19/19 20:03:51 Updater: service started. Auto-update class is MINOR
2/19/19 20:03:51 dataLog: service started.
2/19/19 20:03:51 dataLog: Last log entry 02/19/19 20:03:30
2/19/19 20:03:51 historyLog: service started.
2/19/19 20:03:52 historyLog: Last log entry 02/19/19 20:03:00
2/19/19 20:03:53 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/19/19 20:03:53 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/19/19 20:03:53 Updater: Auto-update is current for class MINOR.
2/19/19 20:03:54 EmonService: Start posting at 02/18/19 23:43:20
2/19/19 20:03:56 influxDB: Start posting at 02/18/19 23:43:10

** Restart **

SD initialized.
2/20/19 20:22:00z Real Time Clock is running. Unix time 1550694120 
2/20/19 20:22:00z Reset reason: Hardware Watchdog
2/20/19 20:22:00z Trace:  9:5, 9:9, 1:2, 1:3, 1:4, 1:5[7], 7:0, 7:7, 1:6, 1:3, 1:4, 1:5[3], 3:0, 3:9, 3:9, 3:9, 3:9, 3:9, 15:1, 15:0, 15:1, 15:0, 15:1, 3:10, 3:10, 3:10, 3:10, 1:6, 1:1[14], 1:2, 9:0, 9:0
2/20/19 20:22:00z ESP8266 ChipID: 2330070
2/20/19 20:22:00z IoTaWatt revision 4.8, firmware version 02_03_21
2/20/19 20:22:00z SPIFFS mounted.
2/21/19 08:22:01 Local time zone: +12:00
2/21/19 08:22:01 device name: IotaWatt
2/21/19 08:22:01 MDNS responder started for hostname IotaWatt
2/21/19 08:22:01 LLMNR responder started for hostname IotaWatt
2/21/19 08:22:01 HTTP server started
2/21/19 08:22:01 timeSync: service started.
2/21/19 08:22:02 statService: started.
2/21/19 08:22:02 dataLog: service started.
2/21/19 08:22:02 dataLog: Last log entry 02/21/19 08:21:50
2/21/19 08:22:03 historyLog: service started.
2/21/19 08:22:03 historyLog: Last log entry 02/21/19 08:21:00
2/21/19 08:22:04 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -81db
2/21/19 08:22:04 Updater: service started. Auto-update class is MINOR
2/21/19 08:22:05 Updater: Auto-update is current for class MINOR.
2/21/19 08:22:06 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/21/19 08:22:06 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/21/19 08:22:07 EmonService: Start posting at 02/21/19 08:21:50
2/21/19 08:22:08 influxDB: Start posting at 02/21/19 08:21:50

** Restart **

SD initialized.
2/22/19 16:10:30z Real Time Clock is running. Unix time 1550851830 
2/22/19 16:10:30z Reset reason: Hardware Watchdog
2/22/19 16:10:30z Trace:  9:9, 1:2, 1:3, 1:4, 1:5[7], 7:0, 7:7, 1:6, 1:3, 1:4, 1:5[3], 3:0, 3:9, 3:9, 3:9, 3:9, 3:9, 15:1, 15:0, 15:1, 15:0, 15:1, 3:10, 3:10, 3:10, 3:10, 1:6, 1:1[5], 1:2[6], 9:0[6], 9:0, 9:1
2/22/19 16:10:30z ESP8266 ChipID: 2330070
2/22/19 16:10:30z IoTaWatt revision 4.8, firmware version 02_03_21
2/22/19 16:10:30z SPIFFS mounted.
2/23/19 04:10:31 Local time zone: +12:00
2/23/19 04:10:31 device name: IotaWatt
2/23/19 04:10:31 MDNS responder started for hostname IotaWatt
2/23/19 04:10:31 LLMNR responder started for hostname IotaWatt
2/23/19 04:10:31 HTTP server started
2/23/19 04:10:31 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -76db
2/23/19 04:10:31 timeSync: service started.
2/23/19 04:10:31 statService: started.
2/23/19 04:10:31 Updater: service started. Auto-update class is MINOR
2/23/19 04:10:31 dataLog: service started.
2/23/19 04:10:32 dataLog: Last log entry 02/23/19 04:10:20
2/23/19 04:10:32 historyLog: service started.
2/23/19 04:10:32 historyLog: Last log entry 02/23/19 04:10:00
2/23/19 04:10:33 Updater: Auto-update is current for class MINOR.
2/23/19 04:10:36 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/23/19 04:10:36 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/23/19 04:10:37 EmonService: Start posting at 02/23/19 04:10:20
2/23/19 04:10:38 influxDB: Start posting at 02/23/19 04:10:20

** Restart **

SD initialized.
2/23/19 10:15:09z Real Time Clock is running. Unix time 1550916909 
2/23/19 10:15:09z Reset reason: Hardware Watchdog
2/23/19 10:15:09z Trace:  8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[3], 3:0, 3:9, 3:9, 3:9, 3:9, 3:9, 15:1, 15:0, 15:1, 15:0, 15:1, 3:10, 3:10, 3:10, 3:10, 1:6, 1:1[2], 1:2[3], 9:0[3], 9:0, 9:1
2/23/19 10:15:09z ESP8266 ChipID: 2330070
2/23/19 10:15:09z IoTaWatt revision 4.8, firmware version 02_03_21
2/23/19 10:15:09z SPIFFS mounted.
2/23/19 22:15:10 Local time zone: +12:00
2/23/19 22:15:10 device name: IotaWatt
2/23/19 22:15:10 MDNS responder started for hostname IotaWatt
2/23/19 22:15:10 LLMNR responder started for hostname IotaWatt
2/23/19 22:15:10 HTTP server started
2/23/19 22:15:10 timeSync: service started.
2/23/19 22:15:11 statService: started.
2/23/19 22:15:11 dataLog: service started.
2/23/19 22:15:11 dataLog: Last log entry 02/23/19 22:15:00
2/23/19 22:15:12 historyLog: service started.
2/23/19 22:15:12 historyLog: Last log entry 02/23/19 22:15:00
2/23/19 22:15:15 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/23/19 22:15:15 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/23/19 22:15:15 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -77db
2/23/19 22:15:15 Updater: service started. Auto-update class is MINOR
2/23/19 22:15:16 EmonService: Start posting at 02/23/19 22:15:00
2/23/19 22:15:17 Updater: Auto-update is current for class MINOR.
2/23/19 22:15:18 influxDB: Start posting at 02/23/19 22:14:50
2/25/19 04:35:59 EmonService: HTTP response -4, retrying.
2/25/19 04:44:38 influxDB: Post Failed: -4
2/25/19 05:18:38 Updater: Invalid response from server. HTTPcode: -4

** Restart **

SD initialized.
2/24/19 21:59:22z Real Time Clock is running. Unix time 1551045562 
2/24/19 21:59:22z Power failure detected.
2/24/19 21:59:22z Reset reason: Power on
2/24/19 21:59:22z ESP8266 ChipID: 2330070
2/24/19 21:59:22z IoTaWatt revision 4.8, firmware version 02_03_21
2/24/19 21:59:22z SPIFFS mounted.
2/25/19 09:59:23 Local time zone: +12:00
2/25/19 09:59:23 device name: IotaWatt
2/25/19 09:59:26 Connecting with WiFiManager.
2/25/19 09:59:33 MDNS responder started for hostname IotaWatt
2/25/19 09:59:33 LLMNR responder started for hostname IotaWatt
2/25/19 09:59:33 HTTP server started
2/25/19 09:59:33 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -80db
2/25/19 09:59:33 timeSync: service started.
2/25/19 09:59:33 statService: started.
2/25/19 09:59:33 Updater: service started. Auto-update class is MINOR
2/25/19 09:59:33 dataLog: service started.
2/25/19 09:59:33 dataLog: Last log entry 02/25/19 09:50:50
2/25/19 09:59:34 historyLog: service started.
2/25/19 09:59:34 historyLog: Last log entry 02/25/19 09:50:00
2/25/19 09:59:36 Updater: Auto-update is current for class MINOR.
2/25/19 09:59:38 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/25/19 09:59:38 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/25/19 09:59:40 EmonService: Start posting at 02/25/19 04:22:50
2/25/19 09:59:42 influxDB: Start posting at 02/25/19 04:22:50

Relatively sure all of the Power failure detected are me power cycling the device.

4

There are a couple of things going on here that are atypical and probably related to the problem:

First, there are the Hardware Watchdog resets. These seem to come out of nowhere while the IoTaWatt is otherwise working fine. There are three in the log above and I never see these. When they do occur, your system has been otherwise running fine, and the external server postings are up to date. It looks as if something has interrupted the ESP and caused it to chase it’s tail. I suspect the interrupt was wifi related.

When the system stops posting to the servers, it is otherwise working fine. Ordinarily, the failure mode with WiFi is that the IoTaWatt disconnects from WiFi. When that happens, if it doesn’t reconnect within an hour, it will restart automatically. In your case, the IoTaWatt doesn’t disconnect from WiFi but cannot connect to anything on the network (code -4).

Two things you could try are improving the WiFi RSSI and/or changing the WiFi channel that your router uses. The other thing would be to swap out the IoTaWatt and see if the problem goes away. If you bought it from the Stuff site, I can arrange that.

5

I ordered from OpenEnergyMonitor shop December 2017, only got it installed as part of a solar install ~3 weeks ago. Also I am in New Zealand so maybe not so easy to swap out.

I’ll setup a dedicated wifi AP outside the enclosure that the device is in and report back.

6

I am sure you know this already… but I have to ask… :wink:

What type of enclosure is the IoTaWatt in? An all metal enclosure will attenuate the WiFi 2.4GHz signal dramatically. A plastic enclosure is definitely a better choice.

7

@ogiewon no problems asking :slight_smile: It’s in a plastic media enclosure next to my fuse box. Further away from this I have esp8266 devices inside server racks monitoring temps. While I realise the RSSI could be higher, I guess I was expecting a WiFi drop out to present itself differently?

I’ve got a spare basic AP lying around, I’ll configure it and put it in the same room (so it’ll be just outside the plastic door to the IoTaWatt) and the IoTaWatt will be the only device connected to it, and report back.

Cheers.

8

Setup a new closer AP (in the same room now):

2/26/19 18:40:53 WiFi disconnected.
2/26/19 18:40:56 WiFi connected. SSID=Home, IP=10.111.111.80, channel=6, RSSI -53db

Will report back if I notice it again.

9

Short duration disconnects that are detected are not a problem at all. The RSSI is much better.

1 Like
10

Yes, that was me turning off the AP it was already associated with and it jumping onto the other one. That’s the sort of “WiFi disconnected” message I was expecting to see in the logs when I’ve had the random failures, so good to know that’s all working.

FYI I’m using Aruba IAPs. The controllers own internal connection quality metric was ok original AP due to the low speed requirements… Will keep an eye on it over the next week anyway.

11

Unfortunately it happened again today. Logs from the last time I posted. Note, the restart at 2/26/19 07:20:21z was me power cycling it to make sure it got onto the new AP with better signal (doesn’t appear that the IoTaWatt respects 802.11r / Fast Roaming - but not expecting it too…). The rest is with no interaction from me.

Same looking failure happened at 3/01/19 11:13:50 today.

** Restart **

SD initialized.
2/24/19 22:07:14z Real Time Clock is running. Unix time 1551046034 
2/24/19 22:07:14z Power failure detected.
2/24/19 22:07:14z Reset reason: External System
2/24/19 22:07:14z ESP8266 ChipID: 2330070
2/24/19 22:07:14z IoTaWatt revision 4.8, firmware version 02_03_21
2/24/19 22:07:14z SPIFFS mounted.
2/25/19 10:07:15 Local time zone: +12:00
2/25/19 10:07:15 device name: IotaWatt
2/25/19 10:07:18 Connecting with WiFiManager.
2/25/19 10:07:21 MDNS responder started for hostname IotaWatt
2/25/19 10:07:21 LLMNR responder started for hostname IotaWatt
2/25/19 10:07:21 HTTP server started
2/25/19 10:07:21 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -76db
2/25/19 10:07:21 timeSync: service started.
2/25/19 10:07:21 statService: started.
2/25/19 10:07:21 Updater: service started. Auto-update class is MINOR
2/25/19 10:07:21 dataLog: service started.
2/25/19 10:07:21 dataLog: Last log entry 02/25/19 10:07:10
2/25/19 10:07:21 historyLog: service started.
2/25/19 10:07:21 historyLog: Last log entry 02/25/19 10:07:00
2/25/19 10:07:25 Updater: Auto-update is current for class MINOR.
2/25/19 10:07:26 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/25/19 10:07:26 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/25/19 10:07:27 EmonService: Start posting at 02/25/19 10:07:20
2/25/19 10:07:29 influxDB: Start posting at 02/25/19 10:07:00
2/26/19 18:40:53 WiFi disconnected.
2/26/19 18:40:56 WiFi connected. SSID=Home, IP=10.111.111.80, channel=6, RSSI -53db
2/26/19 18:43:16 WiFi disconnected.
2/26/19 18:43:35 WiFi connected. SSID=Home, IP=10.111.111.80, channel=11, RSSI -79db

** Restart **

SD initialized.
2/26/19 07:20:21z Real Time Clock is running. Unix time 1551165621 
2/26/19 07:20:21z Power failure detected.
2/26/19 07:20:21z Reset reason: External System
2/26/19 07:20:21z ESP8266 ChipID: 2330070
2/26/19 07:20:21z IoTaWatt revision 4.8, firmware version 02_03_21
2/26/19 07:20:21z SPIFFS mounted.
2/26/19 19:20:22 Local time zone: +12:00
2/26/19 19:20:22 device name: IotaWatt
2/26/19 19:20:25 Connecting with WiFiManager.
2/26/19 19:20:32 MDNS responder started for hostname IotaWatt
2/26/19 19:20:32 LLMNR responder started for hostname IotaWatt
2/26/19 19:20:32 HTTP server started
2/26/19 19:20:32 WiFi connected. SSID=Home, IP=10.111.111.80, channel=6, RSSI -54db
2/26/19 19:20:32 timeSync: service started.
2/26/19 19:20:32 statService: started.
2/26/19 19:20:32 Updater: service started. Auto-update class is MINOR
2/26/19 19:20:32 dataLog: service started.
2/26/19 19:20:32 dataLog: Last log entry 02/26/19 19:20:15
2/26/19 19:20:32 historyLog: service started.
2/26/19 19:20:32 historyLog: Last log entry 02/26/19 19:20:00
2/26/19 19:20:34 Updater: Auto-update is current for class MINOR.
2/26/19 19:20:37 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/26/19 19:20:37 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/26/19 19:20:38 EmonService: Start posting at 02/26/19 19:20:20
2/26/19 19:20:38 influxDB: Start posting at 02/26/19 19:20:00
2/26/19 21:34:33 Heap memory has degraded below safe minimum, restarting.

** Restart **

SD initialized.
2/26/19 09:34:35z Real Time Clock is running. Unix time 1551173675 
2/26/19 09:34:35z Reset reason: Software/System restart
2/26/19 09:34:35z Trace:  1:4, 1:5[7], 7:0, 7:9, 1:6, 1:3, 1:4, 1:5[3], 3:0, 3:6, 3:6, 3:6, 3:6, 3:6, 3:6, 1:6, 1:1[10], 1:2[11], 9:0[11], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[21]
2/26/19 09:34:35z ESP8266 ChipID: 2330070
2/26/19 09:34:35z IoTaWatt revision 4.8, firmware version 02_03_21
2/26/19 09:34:35z SPIFFS mounted.
2/26/19 21:34:36 Local time zone: +12:00
2/26/19 21:34:36 device name: IotaWatt
2/26/19 21:34:36 MDNS responder started for hostname IotaWatt
2/26/19 21:34:36 LLMNR responder started for hostname IotaWatt
2/26/19 21:34:36 HTTP server started
2/26/19 21:34:36 timeSync: service started.
2/26/19 21:34:37 statService: started.
2/26/19 21:34:37 dataLog: service started.
2/26/19 21:34:38 dataLog: Last log entry 02/26/19 21:34:30
2/26/19 21:34:38 historyLog: service started.
2/26/19 21:34:38 historyLog: Last log entry 02/26/19 21:34:00
2/26/19 21:34:41 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
2/26/19 21:34:41 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
2/26/19 21:34:41 WiFi connected. SSID=Home, IP=10.111.111.80, channel=6, RSSI -50db
2/26/19 21:34:41 Updater: service started. Auto-update class is MINOR
2/26/19 21:34:42 EmonService: Start posting at 02/26/19 21:28:40
2/26/19 21:34:43 Updater: Auto-update is current for class MINOR.
2/26/19 21:34:43 influxDB: Start posting at 02/26/19 21:28:30
3/01/19 11:13:50 EmonService: HTTP response -4, retrying.
3/01/19 11:19:39 influxDB: Post Failed: -4
3/01/19 11:41:19 Updater: Invalid response from server. HTTPcode: -4

** Restart **

SD initialized.
3/01/19 04:40:05z Real Time Clock is running. Unix time 1551415205 
3/01/19 04:40:05z Power failure detected.
3/01/19 04:40:05z Reset reason: External System
3/01/19 04:40:05z ESP8266 ChipID: 2330070
3/01/19 04:40:05z IoTaWatt revision 4.8, firmware version 02_03_21
3/01/19 04:40:05z SPIFFS mounted.
3/01/19 16:40:06 Local time zone: +12:00
3/01/19 16:40:06 device name: IotaWatt
3/01/19 16:40:09 Connecting with WiFiManager.
3/01/19 16:40:16 MDNS responder started for hostname IotaWatt
3/01/19 16:40:16 LLMNR responder started for hostname IotaWatt
3/01/19 16:40:16 HTTP server started
3/01/19 16:40:16 WiFi connected. SSID=Home, IP=10.111.111.80, channel=6, RSSI -54db
3/01/19 16:40:16 timeSync: service started.
3/01/19 16:40:16 statService: started.
3/01/19 16:40:16 Updater: service started. Auto-update class is MINOR
3/01/19 16:40:16 dataLog: service started.
3/01/19 16:40:17 dataLog: Last log entry 03/01/19 16:40:00
3/01/19 16:40:17 historyLog: service started.
3/01/19 16:40:17 historyLog: Last log entry 03/01/19 16:40:00
3/01/19 16:40:18 Updater: Auto-update is current for class MINOR.
3/01/19 16:40:21 EmonService: started. url=10.111.111.36:8080, node=IotaWatt_1, interval=10, encrypted
3/01/19 16:40:21 influxDB: started, url=10.111.111.35:8086, db=iotawatt, interval=10
3/01/19 16:40:22 EmonService: Start posting at 03/01/19 11:00:10
3/01/19 16:40:23 influxDB: Start posting at 03/01/19 11:00:00
12

Well, it was a nice try to change the router. From what you say it is the same model router, but at this point I don’t think that’s it. The vintage of your IoTaWatt is 2017. The newer units use a later model ESP12S and although there have never been reports of problems like this before, my gut says it’s the ESP WiFi.

If you PM your email and shipping address, I’ll send a replacement PCB. you should be able to just swap it in with your SD card from the old PCB and retain all of your configuration and history.

If that doesn’t solve the problem, we would need to do some WireShark to flesh out the problem. You sound like you may be able to do that.

1 Like
13

Note, after replacing the board in my unit I’ve had problem free operation. Am sending the faulty one back to @overeasy for analysis.

3 Likes
14

Thanks for the followup. Always nice to see the final resolution to issues like this.