IoTaWatt seems to require daily rebooting to access

That’s a big clue. It happens almost exactly 15 minutes after the previous disconnect/reconnect. This is a watchdog timer in IoTaWatt that checks for client requests that never complete. The timeout interval is 15 minutes.

This indicates to me that the low-level IP code didn’t properly clean up and reset when WiFi disconnected. Now that you are running PVoutput, it has been detected with client requests.

Lets wait for the ping test after the next webserver stoppage. I’m guessing it will work.

I’ve been able to access since last time, as late as 5:20PM today (over two full days of uninterrupted access). But at 7:38PM today it didn’t work. I ping’d the IP. 4 packets sent, 4 received, 0 lost. “Destination host unreachable” each time. I did it 3 times with the same response.
Anything I should do before I reboot the wifi?

No, but after it’s working again, could you ping again and see if you still get the “Destination host unreachable”?

OK. I ping’d again while it was working, same response (“Destination host unreachable”).

Here is the latest log, it looks like it restarted itself because of a FW upgrade but that was while it was still accessible.

4/02/19 09:09:43 Updater: Update from 02_03_21 to 02_04_00
4/02/19 09:09:43 Updater: download 02_04_00
4/02/19 09:09:50 Updater: Release downloaded 6681ms, size 670392
4/02/19 09:09:57 Updater: Update downloaded and signature verified
4/02/19 09:10:03 Updater: firmware upgraded to version 02_04_00
4/02/19 09:10:03 Firmware updated, restarting.

** Restart **

SD initialized.
4/02/19 14:10:11z Real Time Clock is running. Unix time 1554214211
4/02/19 14:10:11z Reset reason: Software/System restart
4/02/19 14:10:11z Trace: 1:2[7], 9:0[7], 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[19], 1: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:4, 1:5[5]
4/02/19 14:10:11z ESP8266 ChipID: 2518015
4/02/19 14:10:11z IoTaWatt 4.x, Firmware version 02_04_00
4/02/19 14:10:11z Updater: Installing update files for version 02_04_00
4/02/19 14:10:11z Updater: Installing GRAPH.JS
4/02/19 14:10:11z Updater: Installing INDEX.HTM
4/02/19 14:10:12z Updater: Installing TABLES.TXT
4/02/19 14:10:12z Updater: Installing CNFSTYLE.CSS
4/02/19 14:10:12z Updater: Installing EDIT.HTM
4/02/19 14:10:12z Updater: Installing GRAPH.HTM
4/02/19 14:10:13z Updater: Installation complete.
4/02/19 14:10:13z SPIFFS mounted.
4/02/19 09:10:14 Local time zone: -6:00
4/02/19 09:10:14 Using Daylight Saving Time (BST) when in effect.
4/02/19 09:10:14 device name: IotaWatt
4/02/19 09:10:14 MDNS responder started for hostname IotaWatt
4/02/19 09:10:14 LLMNR responder started for hostname IotaWatt
4/02/19 09:10:14 HTTP server started
4/02/19 09:10:14 timeSync: service started.
4/02/19 09:10:14 statService: started.
4/02/19 09:10:14 dataLog: service started.
4/02/19 09:10:14 dataLog: Last log entry 04/02/19 09:09:50
4/02/19 09:10:14 historyLog: service started.
4/02/19 09:10:14 historyLog: Last log entry 04/02/19 09:09:00
4/02/19 09:10:15 WiFi connected. SSID=Konkle, IP=192.168.0.4, channel=1, RSSI -61db
4/02/19 09:10:15 Updater: service started. Auto-update class is MINOR
4/02/19 09:10:16 Updater: Auto-update is current for class MINOR.
4/02/19 09:10:24 PVoutput: started
4/02/19 09:10:24 PVoutput: System MicroWatt, interval 5, freeload mode
4/02/19 09:10:24 PVoutput: Start status beginning 04/02/19 09:05:00
4/02/19 20:57:02 WiFi disconnected.
4/02/19 20:58:05 WiFi connected. SSID=Konkle, IP=192.168.0.4, channel=11, RSSI -54db

This issue has been persistent - connection to IoTaWatt is lost every few days. So far in April the shortest time has been 9 hours, the longest 86 hours (counting from either a router reboot or an IoTaWatt restart). The average of the 7 lost connections is about 45 hours. Rebooting my wifi router always resolves the issue. Does anyone else have this problem?

I have had no issues with Wireless and the IoTaWatt sense this past Aug; initial install. I use Ubiquity Wireless controllers which provide Long Range (LR) and my IoTaWatt is about 30-40’ max between the two. Could it be a DHCP configuration as seems like a timed issue that resolves itself when you reboot the route, but not the IoTaWatt device. Seems like very odd behavior and different from the solid connectivity I have seen with mine.

At this point I would ask what is you WiFi router?
I don’t believe you ever stated that.

WiFi communication is actually quite complicated and it is to get in a bad state. There is the possibility there is a difference of opinion about the details of the specification between the implementation in the esp8266 and your router. Or, it is possible your router is starting to fail. My ASUS RT-N66 started having that problem a year ago. WiFi would go out completely every month or two. Rebooting the router brought it back. After a few times, I discovered that wired was still working fine, so I could use that and just restart the WiFi part and it would be fine. After a few months I got tired of that and replaced the router with a new one. It has been fine since then.

You have said nothing about what type of WiFi environment your devices are in, ie are there lots of other WiFi networks visible or is yours the only one?

Lots of people use the esp8266 with lots of different WiFi routers and have had good results. So, something is different about your environment. Some routers have had more issues than others as have more complex environments.

So it’s been a few weeks since now since you last checked in. Sorry to.hear this is persistent. If you would like to swap out the IoTaWatt PCB, I can do that. Just PM your address or tell me your original order number.

We’ll see if it’s the IoTaWatt radio or your router, or possibly other 2.4mHz devices. The important thing is that you are still getting logging, despite the WiFi drop off. You will not lose any data swapping the PCB.

Thanks @quella, I also have my router close to the IoTaWatt. And the issue resolves if I reboot the IoTaWatt or the router. By the way thanks for your IoTaWatt review, that was the main reason I decided to go ahead with it, and I’m super happy with it otherwise.

1 Like

Thanks @frogmore, my router is an Ubee DVW32C1. It’s the leased router that Spectrum (TWC) installed. I appreciate the complexity of WiFi and I admit I don’t know much about it, but everything else (phones, computer, printer, TVs) seems to do OK on the WiFi network. The only thing I’ve been unable to access is the IoTaWatt. That’s why it’s so surprising to me that no one else has had the issue.

If you would like to swap out the IoTaWatt PCB, I can do that.

Thanks @overeasy!

I can say that I have never experienced this type of behavior with the IoTaWatt, and of the others I have read it often comes down to IoTaWatt to Wireless AP communications. I previously looked the nearly all the commercial products and found the IoTaWatt to be superior with features, function, and support by a wonderful community and developer.

I hope you can find a solution as I know you will be happy with the product once operational and the persistent issue goes away. Thanks for the kind words on the review as I feel I only touched on the high-level details.

Looking at the online manual here (https://d15yx0mnc9teae.cloudfront.net/sites/default/files/ubee-dvw32cb-userguide.pdf) , I can see this is a bit older tech at around 2015 (its very young compared to me). I would have a look at the “Firewall Settings” on page 62 to see if you have any of these options enabled. Or, if something is showing int he logs where the wireless controller is seen scanning, or attacking the router due to the timed queries for NTP, etc. Check the logs for the IP/MAC address of the IoTaWatt here and see if you see any log info.

Second, the unit has “parental controls” (pg. 66) that may be enabled for all devices connected. I would confirm this is not enabled for the IoTaWatt as the router may be dropping the connection after a period of time thinking it is a person online who violates the controls in-place. This section also includes something call a TOD (Time of Day) policy. Check this is configured correctly. Check the logs here as well as they are in a different place from the previous ones.

Lastly, I would check the wireless section (pg. 73) to see you configured band(s) 2.4, 2.5, both. This system also has a feature to scan for wireless APs in your area. You may want to see if it sees the IoTaWatt in this state or when new and the data it finds when it scans this device. I would also look at any logs on the device around wireless to see if you have a clean signal, etc.

As @frogmore has stated, wireless is not the easiest thing to troubleshoot, and it may not even be wireless but configurations in your router/wireless AP as well. If you have access to this router/AP device, I would have a look here when the problem occurs and see if you have anything logged.

@overeasy was kind enough to send me a new pcb, which I installed and (with help, thanks @overeasy) got working using the same SD card. PVOutput even picked up where it left off! But alas, a day later I couldn’t connect via my wifi. Same as before, it works after a router reboot.

I guess that means it’s the router… Though I still don’t know why everything else consistently connects then.

I looked into everything @quella suggested in the router UI. I didn’t see anything in the firewall logs related to IoTaWatt, I don’t have parental controls set up, and I’m out of my depth in the “Wireless” tab but both channels were configured.

Any ideas?

At this point I’ve got nothing. If you would download the whole message log and upload it as a file, I’ll take a long look at it and see if there’s is any kind of pattern I can discern. Up to now it’s just been snippets, maybe there’s a big picture.

Sure, here is the log. For context, I started IoTaWatt at 14:41 on the 12th (responsive), it was unresponsive at 16:07 so I rebooted IoTaWatt (then it was responsive again), it was unresponsive at 17:16 so I rebooted wifi (then it was responsive again). I noted that it was responsive every hour or two after that, and a few times today (the 13th). It had worked as recently as 19:47 on the 13th. Then it was unresponsive at 20:20 so I rebooted wifi and it’s worked since (now 22:47).

iotamsgs.txt (9.7 KB)

Hello,
I have something else that might fit the theme. The WIFI transmission has always worked perfectly until about 2 weeks ago. Then failures have come. At first, I just turned off and on again IoTaWattt, which helped. Then I was able to fix these failures by turning off the Wi-Fi transmission in the router and restarting. Thereafter, IoTaWattt has supplied the values to Emoncms. Everything worked properly again. Maybe that helps to solve the problem. Below the log file.

6/11/19 12:00:58z WiFi connected. SSID=FritzBox-Rishalde, IP=192.168.2.5, channel=1, RSSI -83db
6/11/19 12:00:58z Updater: service started. Auto-update class is BETA
6/11/19 12:00:59z EmonService: Start posting at 06/11/19 10:35:50
6/11/19 12:00:59z Updater: Auto-update is current for class BETA.
6/11/19 12:05:34z WiFi disconnected.
6/11/19 13:05:34z WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
6/11/19 13:05:36z Real Time Clock is running. Unix time 1560258336
6/11/19 13:05:36z Reset reason: Software/System restart
6/11/19 13:05:36z Trace: 20:42, 1: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:4, 1:5[20], 20:0, 20:1, 20:2, 20:3, 20:4, 20:42, 1:6, 1:3, 1:4, 1:5[5], 1:6, 1:3, 1:4, 1:5[21]
6/11/19 13:05:36z ESP8266 ChipID: 417709
6/11/19 13:05:36z IoTaWatt 4.x, Firmware version 02_04_00
6/11/19 13:05:36z SPIFFS mounted.
6/11/19 13:05:37z Local time zone: +0:00
6/11/19 13:05:37z device name: IotaWatt
6/11/19 13:05:37z MDNS responder started for hostname IotaWatt
6/11/19 13:05:37z LLMNR responder started for hostname IotaWatt
6/11/19 13:05:37z HTTP server started
6/11/19 13:05:37z timeSync: service started.
6/11/19 13:05:38z statService: started.
6/11/19 13:05:38z dataLog: service started.
6/11/19 13:05:39z dataLog: Last log entry 06/11/19 13:05:30
6/11/19 13:05:39z historyLog: service started.
6/11/19 13:05:40z historyLog: Last log entry 06/11/19 13:05:00
6/11/19 13:05:42z EmonService: started. url:80=emoncms.org, node=IotaWatt, interval=10, encrypted
6/11/19 14:05:38z WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
6/11/19 14:05:39z Real Time Clock is running. Unix time 1560261939
6/11/19 14:05:39z Reset reason: Software/System restart
6/11/19 14:05:39z Trace: 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[20], 20:0, 20:1, 20:2, 20:3, 20:4, 20:42, 1:6, 1:1[1], 1:2[2], 9:0[2], 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]
6/11/19 14:05:39z ESP8266 ChipID: 417709
6/11/19 14:05:39z IoTaWatt 4.x, Firmware version 02_04_00
6/11/19 14:05:39z SPIFFS mounted.
6/11/19 14:05:40z Local time zone: +0:00
6/11/19 14:05:40z device name: IotaWatt
6/11/19 14:05:40z MDNS responder started for hostname IotaWatt
6/11/19 14:05:40z LLMNR responder started for hostname IotaWatt
6/11/19 14:05:40z HTTP server started
6/11/19 14:05:40z timeSync: service started.
6/11/19 14:05:41z statService: started.
6/11/19 14:05:41z dataLog: service started.
6/11/19 14:05:42z dataLog: Last log entry 06/11/19 14:05:35
6/11/19 14:05:42z historyLog: service started.
6/11/19 14:05:43z historyLog: Last log entry 06/11/19 14:05:00
6/11/19 14:05:45z EmonService: started. url:80=emoncms.org, node=IotaWatt, interval=10, encrypted
6/11/19 14:25:16z WiFi connected. SSID=FritzBox-Rishalde, IP=192.168.2.5, channel=1, RSSI -82db
6/11/19 14:25:16z Updater: service started. Auto-update class is BETA
6/11/19 14:25:32z Updater: Invalid response from server. HTTPcode: -4
6/11/19 14:25:35z WiFi disconnected.
6/11/19 15:25:36z WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
6/11/19 15:25:37z Real Time Clock is running. Unix time 1560266737
6/11/19 15:25:37z Reset reason: Software/System restart
6/11/19 15:25:37z Trace: 20:42, 1:6, 1:3, 1:4, 1:5[20], 20:0, 20:1, 20:2, 20:3, 20:4, 20:42, 1: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:4, 1:5[5], 1:6, 1:3, 1:4, 1:5[21]
6/11/19 15:25:37z ESP8266 ChipID: 417709
6/11/19 15:25:37z IoTaWatt 4.x, Firmware version 02_04_00
6/11/19 15:25:37z SPIFFS mounted.
6/11/19 15:25:38z Local time zone: +0:00
6/11/19 15:25:38z device name: IotaWatt
6/11/19 15:25:38z MDNS responder started for hostname IotaWatt
6/11/19 15:25:38z LLMNR responder started for hostname IotaWatt
6/11/19 15:25:38z HTTP server started
6/11/19 15:25:38z timeSync: service started.
6/11/19 15:25:39z statService: started.
6/11/19 15:25:39z dataLog: service started.
6/11/19 15:25:40z dataLog: Last log entry 06/11/19 15:25:35
6/11/19 15:25:40z historyLog: service started.
6/11/19 15:25:41z historyLog: Last log entry 06/11/19 15:25:00
6/11/19 15:25:43z EmonService: started. url:80=emoncms.org, node=IotaWatt, interval=10, encrypted
6/11/19 16:25:39z WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
6/11/19 16:25:40z Real Time Clock is running. Unix time 1560270340
6/11/19 16:25:40z Reset reason: Software/System restart
6/11/19 16:25:40z Trace: 1:3, 1:4, 1:5[20], 20:0, 20:1, 20:2, 20:3, 20:4, 20:42, 1:6, 1:1[8], 1:2, 9:0, 9:0, 8:4, 8:6, 8:8, 8:9, 1:2, 1:3, 1:4, 1:5[20], 20:0, 20:1, 20:2, 20:3, 20:4, 20:42, 1:6, 1:3, 1:4, 1:5[21]
6/11/19 16:25:40z ESP8266 ChipID: 417709
6/11/19 16:25:40z IoTaWatt 4.x, Firmware version 02_04_00
6/11/19 16:25:40z SPIFFS mounted.
6/11/19 16:25:41z Local time zone: +0:00
6/11/19 16:25:41z device name: IotaWatt
6/11/19 16:25:41z MDNS responder started for hostname IotaWatt
6/11/19 16:25:41z LLMNR responder started for hostname IotaWatt
6/11/19 16:25:41z HTTP server started
6/11/19 16:25:41z timeSync: service started.
6/11/19 16:25:42z statService: started.
6/11/19 16:25:42z dataLog: service started.
6/11/19 16:25:43z dataLog: Last log entry 06/11/19 16:25:35
6/11/19 16:25:43z historyLog: service started.
6/11/19 16:25:44z historyLog: Last log entry 06/11/19 16:25:00
6/11/19 16:25:46z EmonService: started. url:80=emoncms.org, node=IotaWatt, interval=10, encrypted
6/11/19 16:29:27z WiFi connected. SSID=FritzBox-Rishalde, IP=192.168.2.5, channel=1, RSSI -81db
6/11/19 16:29:27z Updater: service started. Auto-update class is BETA
6/11/19 16:29:28z EmonService: Start posting at 06/11/19 10:35:50
6/11/19 16:29:28z Updater: Auto-update is current for class BETA.
6/11/19 16:35:27z Heap memory has degraded below safe minimum, restarting.

** Restart **

SD initialized.
6/11/19 16:35:29z Real Time Clock is running. Unix time 1560270929
6/11/19 16:35:29z Reset reason: Software/System restart
6/11/19 16:35:29z Trace: 1:5[3], 3:0, 3:11, 1:6, 1:3, 1:4, 1:5[3], 3:0, 3:11, 1:6, 1:1[4], 1:2[5], 9:0[5], 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[3], 3:0, 3:11, 1:6, 1:3, 1:4, 1:5[21]
6/11/19 16:35:29z ESP8266 ChipID: 417709
6/11/19 16:35:29z IoTaWatt 4.x, Firmware version 02_04_00
6/11/19 16:35:29z SPIFFS mounted.
6/11/19 16:35:30z Local time zone: +0:00
6/11/19 16:35:30z device name: IotaWatt
6/11/19 16:35:30z MDNS responder started for hostname IotaWatt
6/11/19 16:35:30z LLMNR responder started for hostname IotaWatt
6/11/19 16:35:30z HTTP server started
6/11/19 16:35:30z timeSync: service started.
6/11/19 16:35:31z statService: started.
6/11/19 16:35:31z dataLog: service started.
6/11/19 16:35:32z dataLog: Last log entry 06/11/19 16:35:25
6/11/19 16:35:32z historyLog: service started.
6/11/19 16:35:33z historyLog: Last log entry 06/11/19 16:35:00
6/11/19 16:35:35z EmonService: started. url:80=emoncms.org, node=IotaWatt, interval=10, encrypted
6/11/19 16:55:46z WiFi connected. SSID=FritzBox-Rishalde, IP=192.168.2.5, channel=1, RSSI -83db
6/11/19 16:55:46z Updater: service started. Auto-update class is BETA
6/11/19 16:55:47z EmonService: Start posting at 06/11/19 11:06:20
6/11/19 16:55:47z Updater: Auto-update is current for class BETA.
6/11/19 17:05:35z WiFi disconnected.
6/11/19 17:20:30z Incomplete HTTP request detected, id 3, restarting.

** Restart **

SD initialized.
6/11/19 17:20:32z Real Time Clock is running. Unix time 1560273632
6/11/19 17:20:32z Reset reason: Software/System restart
6/11/19 17:20:32z Trace: 3:11, 1:6, 1:3, 1:4, 1:5[3], 3:0, 3:11, 1:6, 1:3, 1:4, 1:5[19], 1: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:4, 1:5[5], 1:6, 1:3, 1:4, 1:5[21]
6/11/19 17:20:32z ESP8266 ChipID: 417709
6/11/19 17:20:32z IoTaWatt 4.x, Firmware version 02_04_00
6/11/19 17:20:32z SPIFFS mounted.
6/11/19 17:20:33z Local time zone: +0:00
6/11/19 17:20:33z device name: IotaWatt
6/11/19 17:20:33z MDNS responder started for hostname IotaWatt
6/11/19 17:20:33z LLMNR responder started for hostname IotaWatt
6/11/19 17:20:33z HTTP server started
6/11/19 17:20:33z timeSync: service started.
6/11/19 17:20:34z statService: started.
6/11/19 17:20:34z dataLog: service started.
6/11/19 17:20:35z dataLog: Last log entry 06/11/19 17:20:30
6/11/19 17:20:35z historyLog: service started.
6/11/19 17:20:36z historyLog: Last log entry 06/11/19 17:20:00
6/11/19 17:20:38z EmonService: started. url:80=emoncms.org, node=IotaWatt, interval=10, encrypted
6/11/19 17:33:48z WiFi connected. SSID=FritzBox-Rishalde, IP=192.168.2.5, channel=6, RSSI -77db
6/11/19 17:33:48z Updater: service started. Auto-update class is BETA
6/11/19 17:33:48z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:33:51z Updater: Auto-update is current for class BETA.
6/11/19 17:33:51z EmonService: Start posting at 06/11/19 11:36:30
6/11/19 17:33:58z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:34:09z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:34:19z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:34:30z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:34:40z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:34:50z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:35:01z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:35:11z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:35:21z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:35:32z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:35:42z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163
6/11/19 17:35:52z timesync: Kiss-o’-Death, code RATE, ip: 85.195.227.163

Hello @hph,

Are you saying that your IoTaWatt is working ok now since 17:33 yesterday and Emoncms is now updated to the current time?

I see that with the last restart in the log, the WiFi channel changed from 1 to 6 and the RSSI improved By 5 dB. If problems recur, take note if the channel changes back.

Everything works properly since then. Has there bee any changes to the Wifi Modul since the last 2 weeks?

No changes, no updates.