Connecting to the device with a web browser to access the configuration app - Resolved

Support
1

I just received my IoTaWatt and set it up yesterday. I am having much difficulty connecting to the device with my Windows laptop, android phone and tablet. The first time I tried to connect with the laptop, I used IoTaWatt/local and tried its IP address. After several attempts, I finally got it to connect using the IP address. The phone took much longer and many attempts. I did get it connected by VPNing in to my LAN and then switching back to my regular LAN and it connected. The tablet would connect after multiple tries. If I wait some time, then sometimes it will connect and sometimes i have to again try multiple times to connect. When it connects, it doesn’t seem to lose the connection. I never have a problem with other web interfaces (UPS, Switches, router, etc) so I am puzzled on why this is happening. If I come home and want to do a quick check of the status of a circuit, it is a 50/50 chance that i will be successful or have to keep trying to connect.

I also set the IoTaWatt up with my Hubitat and it did connect (after a reboot of the IoTaWatt). It seems to work very well and i haven’t lost the connection yet.

It seems like the computer has the best chance of connecting most of the time. Anyone have any thoughts. Maybe i have a defective unit but when it connects, it seems to run perfectly.

Thanks for any help!!

2

FCould you post the message log and explain what you mean by “regular LAN”?

How are you connecting to the Hubitat?

3

Thank you for the fast response. What i meant by “regular LAN” was simply my home LAN network accessed from a local device as opposed to a device connecting to my local LAN through my VPN.

It took me about 15 minutes to log into the IoTaWatt so i could pull the logs. After multiple tries, it finally connected and i accessed the logs. My Hubitat did not lose the connection to the IoTaWatt and i was able to see power changes from the IoTaWatt in Hubitat. Very strange behavior. I’m sure I must be doing something wrong.

Here is the logs:

12/27/19 02:20:46 historyLog: service started.
12/27/19 02:20:46 historyLog: Last log entry 12/27/19 02:18:00

** Restart **

SD initialized.
12/27/19 07:21:57z Real Time Clock is running. Unix time 1577431317
12/27/19 07:21:57z Reset reason: Exception
12/27/19 07:21:57z Trace: 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6]
12/27/19 07:21:57z ESP8266 ChipID: 6308294
12/27/19 07:21:57z IoTaWatt 5.0, Firmware version 02_05_02
12/27/19 07:21:57z SPIFFS mounted.
12/27/19 02:21:58 Local time zone: -5:00
12/27/19 02:21:58 Using Daylight Saving Time (BST) when in effect.
12/27/19 02:21:58 device name: IotaWatt
12/27/19 02:21:58 MDNS responder started for hostname IotaWatt
12/27/19 02:21:58 LLMNR responder started for hostname IotaWatt
12/27/19 02:21:58 HTTP server started
12/27/19 02:21:58 timeSync: service started.
12/27/19 02:21:58 statService: started.
12/27/19 02:21:58 Updater: service started. Auto-update class is MINOR
12/27/19 02:21:58 dataLog: service started.
12/27/19 02:21:58 dataLog: Last log entry 12/27/19 02:21:55
12/27/19 02:21:59 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -73db
12/27/19 02:22:09 Updater: Auto-update is current for class MINOR.
12/27/19 02:22:58 historyLog: service started.
12/27/19 02:22:58 historyLog: Last log entry 12/27/19 02:21:00

** Restart **

SD initialized.
12/27/19 07:24:13z Real Time Clock is running. Unix time 1577431453
12/27/19 07:24:13z Reset reason: Exception
12/27/19 07:24:13z Trace: 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6]
12/27/19 07:24:13z ESP8266 ChipID: 6308294
12/27/19 07:24:13z IoTaWatt 5.0, Firmware version 02_05_02
12/27/19 07:24:13z SPIFFS mounted.
12/27/19 02:24:14 Local time zone: -5:00
12/27/19 02:24:14 Using Daylight Saving Time (BST) when in effect.
12/27/19 02:24:14 device name: IotaWatt
12/27/19 02:24:14 MDNS responder started for hostname IotaWatt
12/27/19 02:24:14 LLMNR responder started for hostname IotaWatt
12/27/19 02:24:14 HTTP server started
12/27/19 02:24:14 timeSync: service started.
12/27/19 02:24:14 statService: started.
12/27/19 02:24:14 Updater: service started. Auto-update class is MINOR
12/27/19 02:24:14 dataLog: service started.
12/27/19 02:24:14 dataLog: Last log entry 12/27/19 02:24:10
12/27/19 02:24:15 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -76db
12/27/19 02:24:15 Updater: Auto-update is current for class MINOR.
12/27/19 02:25:14 historyLog: service started.
12/27/19 02:25:14 historyLog: Last log entry 12/27/19 02:24:00

** Restart **

SD initialized.
12/27/19 07:39:06z Real Time Clock is running. Unix time 1577432346
12/27/19 07:39:06z Reset reason: Exception
12/27/19 07:39:06z Trace: 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6]
12/27/19 07:39:06z ESP8266 ChipID: 6308294
12/27/19 07:39:06z IoTaWatt 5.0, Firmware version 02_05_02
12/27/19 07:39:06z SPIFFS mounted.
12/27/19 02:39:07 Local time zone: -5:00
12/27/19 02:39:07 Using Daylight Saving Time (BST) when in effect.
12/27/19 02:39:07 device name: IotaWatt
12/27/19 02:39:07 MDNS responder started for hostname IotaWatt
12/27/19 02:39:07 LLMNR responder started for hostname IotaWatt
12/27/19 02:39:07 HTTP server started
12/27/19 02:39:07 timeSync: service started.
12/27/19 02:39:07 statService: started.
12/27/19 02:39:07 Updater: service started. Auto-update class is MINOR
12/27/19 02:39:07 dataLog: service started.
12/27/19 02:39:07 dataLog: Last log entry 12/27/19 02:39:00
12/27/19 02:39:08 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db
12/27/19 02:39:08 Updater: Auto-update is current for class MINOR.
12/27/19 02:40:07 historyLog: service started.
12/27/19 02:40:07 historyLog: Last log entry 12/27/19 02:39:00

** Restart **

SD initialized.
12/27/19 07:42:24z Real Time Clock is running. Unix time 1577432544
12/27/19 07:42:24z Reset reason: Exception
12/27/19 07:42:24z Trace: 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6]
12/27/19 07:42:24z ESP8266 ChipID: 6308294
12/27/19 07:42:24z IoTaWatt 5.0, Firmware version 02_05_02
12/27/19 07:42:24z SPIFFS mounted.
12/27/19 02:42:25 Local time zone: -5:00
12/27/19 02:42:25 Using Daylight Saving Time (BST) when in effect.
12/27/19 02:42:25 device name: IotaWatt
12/27/19 02:42:25 MDNS responder started for hostname IotaWatt
12/27/19 02:42:25 LLMNR responder started for hostname IotaWatt
12/27/19 02:42:25 HTTP server started
12/27/19 02:42:25 timeSync: service started.
12/27/19 02:42:25 statService: started.
12/27/19 02:42:25 Updater: service started. Auto-update class is MINOR
12/27/19 02:42:25 dataLog: service started.
12/27/19 02:42:25 dataLog: Last log entry 12/27/19 02:42:20
12/27/19 02:42:26 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db
12/27/19 02:42:26 Updater: Auto-update is current for class MINOR.
12/27/19 02:43:25 historyLog: service started.
12/27/19 02:43:25 historyLog: Last log entry 12/27/19 02:42:00

** Restart **

SD initialized.
12/27/19 09:15:59z Real Time Clock is running. Unix time 1577438159
12/27/19 09:15:59z Reset reason: Exception
12/27/19 09:15:59z Trace: 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6]
12/27/19 09:15:59z ESP8266 ChipID: 6308294
12/27/19 09:15:59z IoTaWatt 5.0, Firmware version 02_05_02
12/27/19 09:15:59z SPIFFS mounted.
12/27/19 04:16:00 Local time zone: -5:00
12/27/19 04:16:00 Using Daylight Saving Time (BST) when in effect.
12/27/19 04:16:00 device name: IotaWatt
12/27/19 04:16:00 MDNS responder started for hostname IotaWatt
12/27/19 04:16:00 LLMNR responder started for hostname IotaWatt
12/27/19 04:16:00 HTTP server started
12/27/19 04:16:00 timeSync: service started.
12/27/19 04:16:00 statService: started.
12/27/19 04:16:00 Updater: service started. Auto-update class is BETA
12/27/19 04:16:00 dataLog: service started.
12/27/19 04:16:00 dataLog: Last log entry 12/27/19 04:15:55
12/27/19 04:16:01 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db
12/27/19 04:16:01 Updater: Auto-update is current for class BETA.
12/27/19 04:17:00 historyLog: service started.
12/27/19 04:17:00 historyLog: Last log entry 12/27/19 04:15:00
12/27/19 21:17:40 Updater: Invalid response from server. HTTPcode: -4
12/27/19 21:57:13 WiFi disconnected.
12/27/19 22:57:13 WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
12/28/19 03:57:15z Real Time Clock is running. Unix time 1577505435
12/28/19 03:57:15z Reset reason: Software/System restart
12/28/19 03:57:15z Trace: 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 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[5], 5:0, 1:6, 1:3, 1:4, 1:5[21], 21:0, 21:2
12/28/19 03:57:15z ESP8266 ChipID: 6308294
12/28/19 03:57:15z IoTaWatt 5.0, Firmware version 02_05_02
12/28/19 03:57:15z SPIFFS mounted.
12/27/19 22:57:16 Local time zone: -5:00
12/27/19 22:57:16 Using Daylight Saving Time (BST) when in effect.
12/27/19 22:57:16 device name: IotaWatt
12/27/19 22:57:16 MDNS responder started for hostname IotaWatt
12/27/19 22:57:16 LLMNR responder started for hostname IotaWatt
12/27/19 22:57:16 HTTP server started
12/27/19 22:57:16 timeSync: service started.
12/27/19 22:57:16 statService: started.
12/27/19 22:57:16 dataLog: service started.
12/27/19 22:57:16 dataLog: Last log entry 12/27/19 22:57:10
12/27/19 22:57:22 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -72db
12/27/19 22:57:22 Updater: service started. Auto-update class is BETA
12/27/19 22:57:41 Updater: Auto-update is current for class BETA.
12/27/19 22:58:16 historyLog: service started.
12/27/19 22:58:16 historyLog: Last log entry 12/27/19 22:57:00

** Restart **

SD initialized.
12/28/19 04:23:02z Real Time Clock is running. Unix time 1577506982
12/28/19 04:23:02z Power failure detected.
12/28/19 04:23:02z Reset reason: External System
12/28/19 04:23:02z ESP8266 ChipID: 6308294
12/28/19 04:23:02z IoTaWatt 5.0, Firmware version 02_05_02
12/28/19 04:23:02z SPIFFS mounted.
12/27/19 23:23:03 Local time zone: -5:00
12/27/19 23:23:03 Using Daylight Saving Time (BST) when in effect.
12/27/19 23:23:03 device name: IotaWatt
12/27/19 23:23:06 MDNS responder started for hostname IotaWatt
12/27/19 23:23:06 LLMNR responder started for hostname IotaWatt
12/27/19 23:23:06 HTTP server started
12/27/19 23:23:06 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -75db
12/27/19 23:23:06 timeSync: service started.
12/27/19 23:23:06 statService: started.
12/27/19 23:23:06 Updater: service started. Auto-update class is BETA
12/27/19 23:23:06 dataLog: service started.
12/27/19 23:23:06 dataLog: Last log entry 12/27/19 23:22:45
12/27/19 23:23:07 Updater: Auto-update is current for class BETA.
12/27/19 23:24:06 historyLog: service started.
12/27/19 23:24:06 historyLog: Last log entry 12/27/19 23:22:100:

Thanks again!!

4

That all looks fine, but I’d like to know more about how you are connecting to Hubitat. I suspect you are using the status API, which may have something to do with the problem. So can you elaborate on that connection?

5

The Hubitat is definitely not the problem because the issue began before I had the Hubitat connected to the IoTaWatt. I connected to the Hubitat with this proceedure.

Any thoughts of what could be wrong?

6

OK, I get that you had issues before the Hubitat, but so I understand the load on the web-server, what polling interval have you set for Hubitat.

Also, you posted that you have a windows laptop, android phone and tablet. Isd that an android tablet or something else?

With the windows laptop, is it windows 10? Would you download and install Bonjour to see if that helps?

Do you have a single router? repeaters? mesh routers?

Have you set any passwords for the IoTaWatt?

7

Still interested in the answers to the above, but following up on something else in the message log. There is a bug that I’ve been chasing for awhile now, and this newer release has additional diagnostics to aid in diagnosing it. Your message log has several instances of the bug causing an exception. I can’t say if it’s related to your connectivity issue except that I cannot see a connection.

But to follow up on that, the trace isn’t definitive but points to two areas of activity:

  • Attempting to save a graph in Graph+
  • Processing a change in configuration

Did you experience problems with either of these activities?

8

I will try to give you as much info as possible.

Hubitat Polling Interval: 30 Seconds (I never changed this default).

Devices:
Toshiba Laptop running the latest version of Windows 10. (I’m not sure what Bonjour would do because I have same issue on other devices.)
Samsung Galaxy S8+ Android Phone
Samsung Galaxy Tab S2 Android Tablet

Single Asus Router connected to a cable modem. No repeaters or mesh routers. Wifi signal level is ok. I thought it might be related to the WiFi signal but some devices won’t connect while others are getting the signal fine. Again, the initial connection to the IoTaWatt is the issue.

No passwords were set. I did purchase another IoTaWatt Bundle today because i wanted to control more circuits and was curious to see how the second unit behaved. I really love the way the unit performs when it connects.

I poked around in Graph+ but never attempted to save a graph yet.

I have changed the configuration many times by saving new names to the Inputs and creating Outputs. But again, I had the issue right from the start. In fact right now I am still trying to get to the configuration page.

Keep getting this:

"This site can’t be reached
192.168.8.186 took too long to respond.
Try:

Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_TIMED_OUT"

Something interesting, I just unplugged and plugged the power cord on the IoTaWatt and the configuration screen came right up, however it does not respond to the menus.

I been trying for a while now and I can’t get to the configuration. The main menu is there now but clicking on anything does nothing. Do you think i may have a defective unit?

9

A little more info:

I been trying to get into the configuration page and I still get the main configuration screen but clicking the buttons does nothing.

I rebooted the router (unplugged) and the IoTaWatt and have the same issue.
The IoTaWatt pings fine and the IP shows up on my router config page.
The Hubitat is updating the IoTaWatt just fine.

I’m really feeling like the unit is defective because the issue is getting worse.

10

It finally responded at 9:05pm EST

Here are the logs:

12/27/19 02:39:07 HTTP server started
12/27/19 02:39:07 timeSync: service started.
12/27/19 02:39:07 statService: started.
12/27/19 02:39:07 Updater: service started. Auto-update class is MINOR
12/27/19 02:39:07 dataLog: service started.
12/27/19 02:39:07 dataLog: Last log entry 12/27/19 02:39:00
12/27/19 02:39:08 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db
12/27/19 02:39:08 Updater: Auto-update is current for class MINOR.
12/27/19 02:40:07 historyLog: service started.
12/27/19 02:40:07 historyLog: Last log entry 12/27/19 02:39:00

** Restart **

SD initialized.
12/27/19 07:42:24z Real Time Clock is running. Unix time 1577432544
12/27/19 07:42:24z Reset reason: Exception
12/27/19 07:42:24z Trace: 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6]
12/27/19 07:42:24z ESP8266 ChipID: 6308294
12/27/19 07:42:24z IoTaWatt 5.0, Firmware version 02_05_02
12/27/19 07:42:24z SPIFFS mounted.
12/27/19 02:42:25 Local time zone: -5:00
12/27/19 02:42:25 Using Daylight Saving Time (BST) when in effect.
12/27/19 02:42:25 device name: IotaWatt
12/27/19 02:42:25 MDNS responder started for hostname IotaWatt
12/27/19 02:42:25 LLMNR responder started for hostname IotaWatt
12/27/19 02:42:25 HTTP server started
12/27/19 02:42:25 timeSync: service started.
12/27/19 02:42:25 statService: started.
12/27/19 02:42:25 Updater: service started. Auto-update class is MINOR
12/27/19 02:42:25 dataLog: service started.
12/27/19 02:42:25 dataLog: Last log entry 12/27/19 02:42:20
12/27/19 02:42:26 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db
12/27/19 02:42:26 Updater: Auto-update is current for class MINOR.
12/27/19 02:43:25 historyLog: service started.
12/27/19 02:43:25 historyLog: Last log entry 12/27/19 02:42:00

** Restart **

SD initialized.
12/27/19 09:15:59z Real Time Clock is running. Unix time 1577438159
12/27/19 09:15:59z Reset reason: Exception
12/27/19 09:15:59z Trace: 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6], 15:2[6], 15:3, 15:0[6]
12/27/19 09:15:59z ESP8266 ChipID: 6308294
12/27/19 09:15:59z IoTaWatt 5.0, Firmware version 02_05_02
12/27/19 09:15:59z SPIFFS mounted.
12/27/19 04:16:00 Local time zone: -5:00
12/27/19 04:16:00 Using Daylight Saving Time (BST) when in effect.
12/27/19 04:16:00 device name: IotaWatt
12/27/19 04:16:00 MDNS responder started for hostname IotaWatt
12/27/19 04:16:00 LLMNR responder started for hostname IotaWatt
12/27/19 04:16:00 HTTP server started
12/27/19 04:16:00 timeSync: service started.
12/27/19 04:16:00 statService: started.
12/27/19 04:16:00 Updater: service started. Auto-update class is BETA
12/27/19 04:16:00 dataLog: service started.
12/27/19 04:16:00 dataLog: Last log entry 12/27/19 04:15:55
12/27/19 04:16:01 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db
12/27/19 04:16:01 Updater: Auto-update is current for class BETA.
12/27/19 04:17:00 historyLog: service started.
12/27/19 04:17:00 historyLog: Last log entry 12/27/19 04:15:00
12/27/19 21:17:40 Updater: Invalid response from server. HTTPcode: -4
12/27/19 21:57:13 WiFi disconnected.
12/27/19 22:57:13 WiFi disconnected more than 60 minutes, restarting.

** Restart **

SD initialized.
12/28/19 03:57:15z Real Time Clock is running. Unix time 1577505435
12/28/19 03:57:15z Reset reason: Software/System restart
12/28/19 03:57:15z Trace: 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 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[5], 5:0, 1:6, 1:3, 1:4, 1:5[21], 21:0, 21:2
12/28/19 03:57:15z ESP8266 ChipID: 6308294
12/28/19 03:57:15z IoTaWatt 5.0, Firmware version 02_05_02
12/28/19 03:57:15z SPIFFS mounted.
12/27/19 22:57:16 Local time zone: -5:00
12/27/19 22:57:16 Using Daylight Saving Time (BST) when in effect.
12/27/19 22:57:16 device name: IotaWatt
12/27/19 22:57:16 MDNS responder started for hostname IotaWatt
12/27/19 22:57:16 LLMNR responder started for hostname IotaWatt
12/27/19 22:57:16 HTTP server started
12/27/19 22:57:16 timeSync: service started.
12/27/19 22:57:16 statService: started.
12/27/19 22:57:16 dataLog: service started.
12/27/19 22:57:16 dataLog: Last log entry 12/27/19 22:57:10
12/27/19 22:57:22 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -72db
12/27/19 22:57:22 Updater: service started. Auto-update class is BETA
12/27/19 22:57:41 Updater: Auto-update is current for class BETA.
12/27/19 22:58:16 historyLog: service started.
12/27/19 22:58:16 historyLog: Last log entry 12/27/19 22:57:00

** Restart **

SD initialized.
12/28/19 04:23:02z Real Time Clock is running. Unix time 1577506982
12/28/19 04:23:02z Power failure detected.
12/28/19 04:23:02z Reset reason: External System
12/28/19 04:23:02z ESP8266 ChipID: 6308294
12/28/19 04:23:02z IoTaWatt 5.0, Firmware version 02_05_02
12/28/19 04:23:02z SPIFFS mounted.
12/27/19 23:23:03 Local time zone: -5:00
12/27/19 23:23:03 Using Daylight Saving Time (BST) when in effect.
12/27/19 23:23:03 device name: IotaWatt
12/27/19 23:23:06 MDNS responder started for hostname IotaWatt
12/27/19 23:23:06 LLMNR responder started for hostname IotaWatt
12/27/19 23:23:06 HTTP server started
12/27/19 23:23:06 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -75db
12/27/19 23:23:06 timeSync: service started.
12/27/19 23:23:06 statService: started.
12/27/19 23:23:06 Updater: service started. Auto-update class is BETA
12/27/19 23:23:06 dataLog: service started.
12/27/19 23:23:06 dataLog: Last log entry 12/27/19 23:22:45
12/27/19 23:23:07 Updater: Auto-update is current for class BETA.
12/27/19 23:24:06 historyLog: service started.
12/27/19 23:24:06 historyLog: Last log entry 12/27/19 23:22:00

** Restart **

SD initialized.
12/29/19 01:18:12z Real Time Clock is running. Unix time 1577582292
12/29/19 01:18:12z Power failure detected.
12/29/19 01:18:12z Reset reason: External System
12/29/19 01:18:12z ESP8266 ChipID: 6308294
12/29/19 01:18:12z IoTaWatt 5.0, Firmware version 02_05_02
12/29/19 01:18:12z SPIFFS mounted.
12/28/19 20:18:13 Local time zone: -5:00
12/28/19 20:18:13 Using Daylight Saving Time (BST) when in effect.
12/28/19 20:18:13 device name: IotaWatt
12/28/19 20:18:16 Connecting with WiFiManager.
12/28/19 20:18:20 MDNS responder started for hostname IotaWatt
12/28/19 20:18:20 LLMNR responder started for hostname IotaWatt
12/28/19 20:18:20 HTTP server started
12/28/19 20:18:21 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -73db
12/28/19 20:18:21 timeSync: service started.
12/28/19 20:18:21 statService: started.
12/28/19 20:18:21 Updater: service started. Auto-update class is BETA
12/28/19 20:18:21 dataLog: service started.
12/28/19 20:18:21 dataLog: Last log entry 12/28/19 20:18:00
12/28/19 20:18:22 Updater: Auto-update is current for class BETA.
12/28/19 20:19:21 historyLog: service started.
12/28/19 20:19:21 historyLog: Last log entry 12/28/19 20:18:00

** Restart **

SD initialized.
12/29/19 01:25:34z Real Time Clock is running. Unix time 1577582734
12/29/19 01:25:34z Power failure detected.
12/29/19 01:25:34z Reset reason: External System
12/29/19 01:25:34z ESP8266 ChipID: 6308294
12/29/19 01:25:34z IoTaWatt 5.0, Firmware version 02_05_02
12/29/19 01:25:34z SPIFFS mounted.
12/28/19 20:25:35 Local time zone: -5:00
12/28/19 20:25:35 Using Daylight Saving Time (BST) when in effect.
12/28/19 20:25:35 device name: IotaWatt
12/28/19 20:25:38 Connecting with WiFiManager.
12/28/19 20:25:44 MDNS responder started for hostname IotaWatt
12/28/19 20:25:44 LLMNR responder started for hostname IotaWatt
12/28/19 20:25:44 HTTP server started
12/28/19 20:25:45 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db
12/28/19 20:25:45 timeSync: service started.
12/28/19 20:25:45 statService: started.
12/28/19 20:25:45 Updater: service started. Auto-update class is BETA
12/28/19 20:25:45 dataLog: service started.
12/28/19 20:25:45 dataLog: Last log entry 12/28/19 20:25:15
12/28/19 20:25:46 Updater: Auto-update is current for class BETA.
12/28/19 20:26:45 historyLog: service started.
12/28/19 20:26:45 historyLog: Last log entry 12/28/19 20:25:00
12/28/19 20:41:23 WiFi disconnected.
12/28/19 20:44:35 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -74db

** Restart **

SD initialized.
12/29/19 01:51:52z Real Time Clock is running. Unix time 1577584312
12/29/19 01:51:52z Power failure detected.
12/29/19 01:51:52z Reset reason: External System
12/29/19 01:51:52z ESP8266 ChipID: 6308294
12/29/19 01:51:52z IoTaWatt 5.0, Firmware version 02_05_02
12/29/19 01:51:52z SPIFFS mounted.
12/28/19 20:51:53 Local time zone: -5:00
12/28/19 20:51:53 Using Daylight Saving Time (BST) when in effect.
12/28/19 20:51:53 device name: IotaWatt
12/28/19 20:51:56 MDNS responder started for hostname IotaWatt
12/28/19 20:51:56 LLMNR responder started for hostname IotaWatt
12/28/19 20:51:56 HTTP server started
12/28/19 20:51:56 WiFi connected. SSID=loumarjr, IP=192.168.8.186, channel=11, RSSI -76db
12/28/19 20:51:56 timeSync: service started.
12/28/19 20:51:56 statService: started.
12/28/19 20:51:56 Updater: service started. Auto-update class is BETA
12/28/19 20:51:57 dataLog: service started.
12/28/19 20:51:57 dataLog: Last log entry 12/28/19 20:50:50
12/28/19 20:51:58 Updater: Auto-update is current for class BETA.
12/28/19 20:52:56 historyLog: service started.
12/28/19 20:52:56 historyLog: Last log entry 12/28/19 20:50:00

11

I’d like to concentrate on the PC as I don’t test or otherwise use android. I would prefer that you install bonjour. It may not solve your problem, but it does provide explicit support for mDNS which is what resolved the iotawatt.local URL to an IP address on your LAN.

I doubt this is a defective IoTaWatt because the transactions you are using from habitat are identical to the transaction your browser should be issuing for the status display.

That said, it may be an SDcard issue, although there is no indication of that in the message log, and there is evidence of a lot of successful reading and writing.

By your timezone, it looks like you are on the US east coast. What was your order number?

If you are comfortable running the JavaScript debugger on your browser (PC PF12), it would be helpful to see a network trace while refreshing the config utility.

12

I have been looking for the bonjour program on the web and the information says it an older program for setting up and configuring networks by apple.

You said, “it does provide explicit support for mDNS which is what resolved the iotawatt.local URL to an IP address on your LAN” I never could bring up the configuration page using the iotawatt.local URL and I tried multiple times. The only way I was able to bring it up was using the static IP address.

The reason I thought it was defective was I don’t believe anyone else has had this difficulty in loading the configuration page. It loads at times but it is a struggle to load after sitting idle for a time.

How do I determine if it is a SD card issue?

I’m located in upstate, New York Order# 116362 and 117041

The network trace seems to show nothing. What should i be looking for. I cant get it to come up again.

13

2019-12-29%20IoTaWatt%20IE
2019-12-29 IoTaWatt IE.png1717Ă—910 45.9 KB

This was from IE. Clicking on Status or any other button did nothing.

2019-12-29%20IoTaWatt%20Chrome
2019-12-29 IoTaWatt Chrome.png1909Ă—1007 71.3 KB

This was from Google Chrome. Was fully functional.

2019-12-29%20IoTaWatt%20Chrome2
2019-12-29 IoTaWatt Chrome2.png1910Ă—1005 41.3 KB

This was chrome after a reset.

14

2019-12-29%20IoTaWatt%20Chrome3
2019-12-29 IoTaWatt Chrome3.png1910Ă—1007 67.8 KB

Here is chrome after a slow but sucessful load.

15

Exactly.

I myself have this problem accessing an IoTaWatt that is in an outbuilding and using a WiFi bridge.

The network traces generally show slow and/or incomplete responses to requests as here:

1035Ă—544 57.1 KB

These are status requests, typically issued every second to refresh the status screen, but the time for response varies from 107mS to 14 seconds, and ends with a pending request.

These slow and sometimes failed requests are typically caused poor WiFi connection. Your message log shows an RSSI signal strength that is OK but not great. There may be an issue with interference where the IoTaWatt is mounted, or with another device on the network or using the same frequency.

Can you change the channel being used on the router from 11 to 6 or 1 and see what happens?

It doesn’t look like an SD issue because these status requests do not use the SDcard.

16

The WiFi may be an issue but I am not sure. I done some checking and I had two other devices broadcasting an SSID on channel 11. I turned those devices off and checked my WiFI with WiFi Analyzer.

Channel 11 is now very clear and the only thing broadcasting in my house is my main SSDI. The issue persists and I cannot connect to the IoTaWatt (same as before the disabling of the two other SSIDs).

When i check my ASUS RT-AC88U router, the IoTaWatt WiFi signal is very weak. I do remember checking it a few days ago, and saw the same weak signal from the IoTaWatt WiFi connection.

My Rinnai Water Heater WiFi module is in the same room as the IoTaWatt and the Rinnai signal is very strong. Maybe the IoTaWatt WiFi radio is defective. The router is very close to the IoTaWatt and I brought other devices to exactly where the IoTaWatt is located and those devices had very strong signals.

What doesnt make sense is why the Hubitat is getting the signal reliably or maybe i just think it is. I still think it is the IoTaWatt WiFi Radio. Your thoughts?

2019-12-29%20IoTaWatt%20Asus
2019-12-29 IoTaWatt Asus.png1010Ă—96 9.01 KB

17

Can you change the channel being used on the router from 11 to 6 or 1 and see what happens?

18

There is no change. Channel 1 is clear. Channel 6 appears that someone in the neighborhood is using a hidden SSID. Channel 11 is clear. It doesn’t matter what channel i use, same results. Do you think it is the WiFi Radio in the IoTaWatt?

I wanted to bring the IotaWatt right to the router to see if i can get a better signal. Is there an issue with keeping the CTs unplugged from the IoTaWatt but connected to the circuits in the panel for an extended time? If yes, how do I short the CT wires properly?

19

I’ll be offline now until tomorrow.

20

Ok Thank you. I really appreciate you help. Take you much needed and deserved break!!