IoTaWatt User Community - Latest posts

Device does not boot after power loss unless manually power cycled

@overeasy — Fri, 20 Mar 2026 18:13:40 +0000

Thanks. This doesn’t fit the profile for the random boot problem. Is this repeatable within a reasonable number of power cycles?

Wi-Fi disconnection

@DavidReche — Fri, 20 Mar 2026 06:07:28 +0000

Thank you so much for your response and for addressing the problem. I appreciate your help.

I’ll try what you recommended and test it.

What I don’t understand is that it hadn’t given me any problems until now, and my network didn’t change.

Anyway, I’ll create a separate network to see if that solves the problem.

Thanks again.

Device does not boot after power loss unless manually power cycled

@f1xedgear — Fri, 20 Mar 2026 01:46:26 +0000

I bought it in November 2021

Device does not boot after power loss unless manually power cycled

@overeasy — Thu, 19 Mar 2026 19:59:31 +0000

I see the two power failure gaps. This is very unusual. There is a fairly obscure and random boot problem in older units that may be at play here. When was the unit installed?

Wi-Fi disconnection

@overeasy — Thu, 19 Mar 2026 19:42:06 +0000

I do think that your problem is your LAN topology, but I can’t help you with that. I don’t know if this ever worked for you, if it did when it stopped, what might have changed with your network or other related systems.

The home assistant integration typically uses the zeroconfig .local to resolve the IoTaWatt address. Those protocols, Bonjour (apple) and LLMNR(microsoft) rely on an underlying broadcast capability to which IoTaWatt responds with it’s current IP address. This is all deep in the IP stack provider by the ESP8266 IDE (not ESP32) and well below the scope of any of the IoTaWatt developed firmware.

It works fine in a typical single router configuration, and also in higher quality WiFi gear like Ubiquity. Many routers have optional security features to defeat the broadcast and identify protocols however. In your case, I see that you have at least three APs, all of differing brands. Moreover you suggest a mesh network. Mesh networks have been very troublesome for ESP SOCs. I also don’t know if with all the different pieces there could be more than one DHCP server active. In any event I definitely feel the problem is your network.

You suggest that AP switching should be more robust and that binding the IoTaWatt to a single AP would be excessively restrictive. I disagree. The IoTaWatt is not a phone or other mobile device. It is installed in a single place and is tethered by it’s many connections to CTs, VTs and the power supply. There is no reason why it should seamlessly switch to different APs. I asked at the beginning six days ago:

Received no answer. Please take some time to isolate the IoTaWatt or preferably stand up a temporary independent LAN with a single router and see if the problem goes away.

Wi-Fi disconnection

@DavidReche — Thu, 19 Mar 2026 08:17:00 +0000

Well, now it’s failing again, so it seems it’s not the access points either.

Look, I can ping it, but web access isn’t working, and it’s not registering the parameters in Home Assistant.

I’m going a bit crazy with this problem.

Wi-Fi disconnection

@DavidReche — Thu, 19 Mar 2026 07:08:40 +0000

It seems I’ve found the problem.
The issue stems from the ESP32’s difficulty roaming between access points.
Even though the different access points have different channels, the ESP32 doesn’t seem to like it and gets lost, which is why the green LED on the Iotawatt remains lit.
Is there any new firmware that fixes this ESP32 problem? I understand it’s just a software issue and can be resolved.
I don’t think the best solution is to try to prevent the different access points from sharing a coverage area; this situation is very common in homes these days.

What do you think?

Device does not boot after power loss unless manually power cycled

@f1xedgear — Thu, 19 Mar 2026 02:19:46 +0000

Whenever I have a power outage at home I have to remember to unplug and reconnect the 5v power to the IoTaWatt to manually reboot it. If I don’t do this, the device does not boot or record data at all. It’s a bit frustrating when I forget as I’ll have weeks of data lost sometimes.

When the power comes back on, the device has the “dull red” led state, and is not available on the network. After I power cycle it, things resume working but as mentioned there is no data recorded during this period between power loss and manual power cycle.

In the logs below, I had a power outage on Nov 10th, then realized I had to reboot on Dec 1. I had another power outage today (mar 18) at 21:26 and cycled the power at 21:41.

6/25/25 10:36:59 HVAC: Started
6/25/25 10:37:02 HVAC: Last log entry 06/25/25 04:41:50
6/25/25 10:37:02 TotalPower: Started
6/25/25 10:37:04 TotalPower: Last log entry 06/25/25 04:41:50
6/25/25 10:37:05 WaterSystem: Started
6/25/25 10:37:07 WaterSystem: Last log entry 06/25/25 04:41:45
6/25/25 10:37:38 Updater: service started. Auto-update class is MAJOR
6/25/25 10:37:38 WiFi connected. SSID=Pegasus, IP=10.1.1.114, channel=11, RSSI -57db
6/25/25 10:37:39 Updater: Auto-update is current for class MAJOR.
8/06/25 10:38:41 timeSync: Six week routine restart.

** Restart **

SD initialized.
8/06/25 14:38:43z Real Time Clock is running. Unix time 1754491123 
8/06/25 14:38:43z Reset reason: Software/System restart
8/06/25 14:38:43z Trace:  1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:5, 9:9, 1:3, 1:3, 1:6[1], 1:6[2], 1:6[2], 1:6[2], 1:6[3], 1:5[20], 1:6[4], 20:0, 20:1
8/06/25 14:38:43z ESP8266 ID: 16295196, RTC PCF8523 (68)
8/06/25 14:38:43z IoTaWatt 5.0, Firmware version 02_08_03
8/06/25 14:38:43z SPIFFS mounted.
8/06/25 10:38:43 Local time zone: -5:00, using DST/BST when in effect.
8/06/25 10:38:43 device name: IotaWatt
8/06/25 10:38:43 HTTP server started
8/06/25 10:38:43 timeSync: service started.
8/06/25 10:38:43 statService: started.
8/06/25 10:38:43 dataLog: service started.
8/06/25 10:38:45 dataLog: Last log entry 08/06/25 10:38:40
8/06/25 10:38:48 historyLog: service started.
8/06/25 10:38:49 historyLog: Last log entry 08/06/25 10:38:00
8/06/25 10:38:49 WiFi connected. SSID=Pegasus, IP=10.1.1.114, channel=11, RSSI -59db
8/06/25 10:38:49 Updater: service started. Auto-update class is MAJOR
8/06/25 10:38:49 HVAC: Started
8/06/25 10:38:52 HVAC: Last log entry 08/06/25 10:38:40
8/06/25 10:38:53 Updater: Auto-update is current for class MAJOR.
8/06/25 10:38:53 TotalPower: Started
8/06/25 10:38:55 TotalPower: Last log entry 08/06/25 10:38:40
8/06/25 10:38:56 WaterSystem: Started
8/06/25 10:38:58 WaterSystem: Last log entry 08/06/25 10:38:40

** Restart **

SD initialized.
8/18/25 01:46:35z Real Time Clock is running. Unix time 1755481595 
8/18/25 01:46:35z Reset Reason: Power-fail restart.
8/18/25 01:46:35z ESP8266 ID: 16295196, RTC PCF8523 (68)
8/18/25 01:46:35z IoTaWatt 5.0, Firmware version 02_08_03
8/18/25 01:46:35z SPIFFS mounted.
8/17/25 21:46:36 Local time zone: -5:00, using DST/BST when in effect.
8/17/25 21:46:36 device name: IotaWatt
8/17/25 21:46:39 Connecting with WiFiManager.
8/17/25 21:46:42 HTTP server started
8/17/25 21:46:42 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -56db
8/17/25 21:46:42 timeSync: service started.
8/17/25 21:46:42 statService: started.
8/17/25 21:46:42 Updater: service started. Auto-update class is MAJOR
8/17/25 21:46:42 dataLog: service started.
8/17/25 21:46:45 dataLog: Last log entry 08/13/25 09:50:50
8/17/25 21:46:45 Updater: Auto-update is current for class MAJOR.
8/17/25 21:46:47 historyLog: service started.
8/17/25 21:46:49 historyLog: Last log entry 08/13/25 09:50:00
8/17/25 21:46:49 HVAC: Started
8/17/25 21:46:51 HVAC: Last log entry 08/13/25 09:50:50
8/17/25 21:46:52 TotalPower: Started
8/17/25 21:46:54 TotalPower: Last log entry 08/13/25 09:50:50
8/17/25 21:46:54 WaterSystem: Started
8/17/25 21:46:57 WaterSystem: Last log entry 08/13/25 09:50:45
8/17/25 21:49:45 Updater: Auto-update class changed to MINOR
8/17/25 21:49:46 Updater: Auto-update is current for class MINOR.
8/18/25 11:05:46 WiFi disconnected.
8/18/25 11:05:49 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -86db
8/18/25 13:55:39 WiFi disconnected.
8/18/25 13:55:42 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -56db
8/28/25 15:42:44 WiFi disconnected.
8/28/25 15:42:47 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -89db
8/29/25 18:40:50 WiFi disconnected.
8/29/25 18:40:53 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -59db
9/02/25 18:57:56 WiFi disconnected.
9/02/25 18:57:59 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -86db
9/04/25 14:32:14 WiFi disconnected.
9/04/25 14:32:44 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -88db
9/04/25 14:32:44 Updater: Invalid response from server. HTTPcode: -4
9/05/25 23:54:50 WiFi disconnected.
9/05/25 23:54:54 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -58db
9/11/25 22:47:17 WiFi disconnected.
9/11/25 22:48:17 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -91db
9/21/25 14:11:20 WiFi disconnected.
9/21/25 14:11:23 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -60db
9/28/25 21:52:46 timeSync: Six week routine restart.

** Restart **

SD initialized.
9/29/25 01:52:48z Real Time Clock is running. Unix time 1759110768 
9/29/25 01:52:48z Reset reason: Software/System restart
9/29/25 01:52:48z Trace:  1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:1[3], 1:2[4], 9:0[4], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:5, 9:9, 1:3, 1:3, 1:6[1], 1:6[2], 1:6[2], 1:6[3], 1:5[20], 1:6[4], 20:0, 20:1
9/29/25 01:52:48z ESP8266 ID: 16295196, RTC PCF8523 (68)
9/29/25 01:52:48z IoTaWatt 5.0, Firmware version 02_08_03
9/29/25 01:52:48z SPIFFS mounted.
9/28/25 21:52:48 Local time zone: -5:00, using DST/BST when in effect.
9/28/25 21:52:48 device name: IotaWatt
9/28/25 21:52:48 HTTP server started
9/28/25 21:52:48 timeSync: service started.
9/28/25 21:52:48 statService: started.
9/28/25 21:52:48 dataLog: service started.
9/28/25 21:52:51 dataLog: Last log entry 09/28/25 21:52:45
9/28/25 21:52:53 historyLog: service started.
9/28/25 21:52:54 historyLog: Last log entry 09/28/25 21:52:00
9/28/25 21:52:54 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -64db
9/28/25 21:52:54 Updater: service started. Auto-update class is MINOR
9/28/25 21:52:54 HVAC: Started
9/28/25 21:52:57 HVAC: Last log entry 09/28/25 21:52:45
9/28/25 21:52:57 Updater: Auto-update is current for class MINOR.
9/28/25 21:52:57 TotalPower: Started
9/28/25 21:53:00 TotalPower: Last log entry 09/28/25 21:52:45
9/28/25 21:53:00 WaterSystem: Started
9/28/25 21:53:02 WaterSystem: Last log entry 09/28/25 21:52:45
10/07/25 02:12:33 Updater: Invalid response from server. HTTPcode: -4
10/08/25 17:29:07 WiFi disconnected.
10/08/25 17:30:27 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -59db
10/08/25 17:30:33 WiFi disconnected.
10/08/25 17:30:34 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -56db
10/12/25 03:11:38 WiFi disconnected.
10/12/25 03:12:04 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -90db
10/12/25 20:12:29 WiFi disconnected.
10/12/25 20:12:32 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -58db
10/13/25 07:31:35 WiFi disconnected.
10/13/25 07:47:09 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -59db
10/13/25 11:12:16 WiFi disconnected.
10/13/25 11:12:32 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -88db
10/14/25 03:00:41 WiFi disconnected.
10/14/25 03:00:45 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -64db
10/21/25 06:49:29 WiFi disconnected.
10/21/25 07:14:25 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -59db
10/26/25 17:24:44 WiFi disconnected.
10/26/25 17:26:15 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -91db
10/27/25 12:24:38 WiFi disconnected.
10/27/25 12:24:42 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -57db
11/05/25 06:19:30 WiFi disconnected.
11/05/25 06:19:35 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -89db
11/05/25 09:05:14 WiFi disconnected.
11/05/25 09:05:17 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -64db
11/09/25 21:16:38 timeSync: Six week routine restart.

** Restart **

SD initialized.
11/10/25 02:16:39z Real Time Clock is running. Unix time 1762740999 
11/10/25 02:16:39z Reset reason: Software/System restart
11/10/25 02:16:39z Trace:  1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:1[4], 1:2[5], 9:0[5], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:5, 9:9, 1:3, 1:3, 1:6[1], 1:6[2], 1:6[2], 1:6[3], 1:5[20], 1:6[4], 20:0, 20:1
11/10/25 02:16:39z ESP8266 ID: 16295196, RTC PCF8523 (68)
11/10/25 02:16:39z IoTaWatt 5.0, Firmware version 02_08_03
11/10/25 02:16:39z SPIFFS mounted.
11/09/25 21:16:39 Local time zone: -5:00, using DST/BST when in effect.
11/09/25 21:16:39 device name: IotaWatt
11/09/25 21:16:39 HTTP server started
11/09/25 21:16:39 timeSync: service started.
11/09/25 21:16:39 statService: started.
11/09/25 21:16:39 dataLog: service started.
11/09/25 21:16:42 dataLog: Last log entry 11/09/25 21:16:35
11/09/25 21:16:44 historyLog: service started.
11/09/25 21:16:46 historyLog: Last log entry 11/09/25 21:16:00
11/09/25 21:16:46 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -66db
11/09/25 21:16:46 Updater: service started. Auto-update class is MINOR
11/09/25 21:16:46 HVAC: Started
11/09/25 21:16:48 HVAC: Last log entry 11/09/25 21:16:35
11/09/25 21:16:48 Updater: Auto-update is current for class MINOR.
11/09/25 21:16:49 TotalPower: Started
11/09/25 21:16:51 TotalPower: Last log entry 11/09/25 21:16:35
11/09/25 21:16:51 WaterSystem: Started
11/09/25 21:16:53 WaterSystem: Last log entry 11/09/25 21:16:35

** Restart **

SD initialized.
12/02/25 01:29:34z Real Time Clock is running. Unix time 1764638974 
12/02/25 01:29:34z Reset Reason: Power-fail restart.
12/02/25 01:29:34z ESP8266 ID: 16295196, RTC PCF8523 (68)
12/02/25 01:29:34z IoTaWatt 5.0, Firmware version 02_08_03
12/02/25 01:29:34z SPIFFS mounted.
12/01/25 20:29:35 Local time zone: -5:00, using DST/BST when in effect.
12/01/25 20:29:35 device name: IotaWatt
12/01/25 20:29:38 Connecting with WiFiManager.
12/01/25 20:29:41 HTTP server started
12/01/25 20:29:41 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -55db
12/01/25 20:29:41 timeSync: service started.
12/01/25 20:29:41 statService: started.
12/01/25 20:29:41 Updater: service started. Auto-update class is MINOR
12/01/25 20:29:41 dataLog: service started.
12/01/25 20:29:44 dataLog: Last log entry 11/10/25 09:25:35
12/01/25 20:29:44 Updater: Auto-update is current for class MINOR.
12/01/25 20:29:46 historyLog: service started.
12/01/25 20:29:47 historyLog: Last log entry 11/10/25 09:25:00

** Restart **

SD initialized.
12/02/25 01:31:35z Real Time Clock is running. Unix time 1764639095 
12/02/25 01:31:35z Reset reason: Exception
12/02/25 01:31:35z Trace:  10:16[1], 10:16[1], 10:16[1], 34:30, 34:30, 33:0, 34:30, 34:30, 34:30, 33:0, 34:30, 10:16[1], 34:30, 34:30, 33:0, 34:30, 10:16[1], 34:30, 34:30, 33:0, 34:30, 10:16[1], 34:30, 34:30, 33:0, 34:30, 10:16[2], 10:17, 10:17, 10:18, 10:23, 10:17
12/02/25 01:31:35z ESP8266 ID: 16295196, RTC PCF8523 (68)
12/02/25 01:31:35z IoTaWatt 5.0, Firmware version 02_08_03
12/02/25 01:31:35z SPIFFS mounted.
12/01/25 20:31:35 Local time zone: -5:00, using DST/BST when in effect.
12/01/25 20:31:35 device name: IotaWatt
12/01/25 20:31:35 HTTP server started
12/01/25 20:31:35 timeSync: service started.
12/01/25 20:31:35 statService: started.
12/01/25 20:31:35 dataLog: service started.
12/01/25 20:31:38 dataLog: Last log entry 12/01/25 20:31:30
12/01/25 20:31:40 historyLog: service started.
12/01/25 20:31:42 historyLog: Last log entry 11/12/25 09:00:00
12/01/25 20:31:42 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -57db
12/01/25 20:31:42 Updater: service started. Auto-update class is MINOR
12/01/25 20:31:43 Updater: Auto-update is current for class MINOR.
12/01/25 20:49:39 HVAC: Started
12/01/25 20:49:42 HVAC: Last log entry 11/10/25 09:25:35
12/01/25 20:49:42 TotalPower: Started
12/01/25 20:49:44 TotalPower: Last log entry 11/10/25 09:25:35
12/01/25 20:49:45 WaterSystem: Started
12/01/25 20:49:47 WaterSystem: Last log entry 11/10/25 09:25:30
12/19/25 19:39:30 WiFi disconnected.
12/19/25 19:39:34 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -95db
12/21/25 11:13:50 WiFi disconnected.
12/21/25 11:18:07 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -92db
12/21/25 11:22:27 WiFi disconnected.
12/21/25 11:23:50 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -92db
12/21/25 14:19:08 WiFi disconnected.
12/21/25 14:20:53 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -91db
12/21/25 14:41:07 WiFi disconnected.
12/21/25 14:45:32 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -91db
12/21/25 15:23:40 WiFi disconnected.
12/21/25 15:29:09 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -90db
12/21/25 20:14:43 WiFi disconnected.
12/21/25 20:14:46 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -63db
12/24/25 15:20:59 WiFi disconnected.
12/24/25 15:21:03 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -83db
12/24/25 21:07:31 WiFi disconnected.
12/24/25 21:07:35 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -66db
12/28/25 22:51:21 WiFi disconnected.
12/28/25 22:51:34 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -89db
12/30/25 23:08:56 WiFi disconnected.
12/30/25 23:08:59 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -62db

** Restart **

SD initialized.
1/09/26 13:28:14z Real Time Clock is running. Unix time 1767965294 
1/09/26 13:28:14z Reset Reason: Power-fail restart.
1/09/26 13:28:14z ESP8266 ID: 16295196, RTC PCF8523 (68)
1/09/26 13:28:14z IoTaWatt 5.0, Firmware version 02_08_03
1/09/26 13:28:14z SPIFFS mounted.
1/09/26 08:28:15 Local time zone: -5:00, using DST/BST when in effect.
1/09/26 08:28:15 device name: IotaWatt
1/09/26 08:28:18 Connecting with WiFiManager.
1/09/26 08:30:27 Did not connect after power-fail. Restarting to reset WiFi.

** Restart **

SD initialized.
1/09/26 13:30:28z Real Time Clock is running. Unix time 1767965428 
1/09/26 13:30:28z Reset reason: Software/System restart
1/09/26 13:30:28z Trace:  34:5, 34:6[2], 34:25[43], 34:28[1], 34:5, 34:5, 34:5, 34:6[14], 34:25[43], 34:28[1], 34:30, 34:10[4], 34:30, 34:10[3], 34:30, 34:10[5], 34:30, 34:10[6], 34:30, 34:10[7], 34:30, 34:10[8], 11:31[3], 11:30[3], 11:35, 11:36, 11:35, 11:40, 11:45, 11:50, 11:55, 11:70
1/09/26 13:30:28z ESP8266 ID: 16295196, RTC PCF8523 (68)
1/09/26 13:30:28z IoTaWatt 5.0, Firmware version 02_08_03
1/09/26 13:30:28z SPIFFS mounted.
1/09/26 08:30:28 Local time zone: -5:00, using DST/BST when in effect.
1/09/26 08:30:28 device name: IotaWatt
1/09/26 08:30:28 HTTP server started
1/09/26 08:30:28 timeSync: service started.
1/09/26 08:30:28 statService: started.
1/09/26 08:30:28 dataLog: service started.
1/09/26 08:30:31 dataLog: Last log entry 01/09/26 08:28:05
1/09/26 08:30:33 historyLog: service started.
1/09/26 08:30:34 historyLog: Last log entry 01/09/26 08:28:00
1/09/26 08:30:34 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -56db
1/09/26 08:30:34 Updater: service started. Auto-update class is MINOR
1/09/26 08:30:34 HVAC: Started
1/09/26 08:30:38 HVAC: Last log entry 01/09/26 08:28:05
1/09/26 08:30:38 Updater: Auto-update is current for class MINOR.
1/09/26 08:30:38 TotalPower: Started
1/09/26 08:30:42 TotalPower: Last log entry 01/09/26 08:28:05
1/09/26 08:30:42 WaterSystem: Started
1/09/26 08:30:46 WaterSystem: Last log entry 01/09/26 08:28:00
1/24/26 05:57:41 Updater: Invalid response from server. HTTPcode: -4
2/10/26 17:35:02 WiFi disconnected.
2/10/26 17:35:05 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -88db
2/10/26 17:58:44 WiFi disconnected.
2/10/26 17:58:47 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -63db
2/11/26 03:50:15 WiFi disconnected.
2/11/26 03:50:18 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -84db
2/11/26 11:43:40 WiFi disconnected.
2/11/26 11:43:43 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -62db
2/12/26 03:55:55 WiFi disconnected.
2/12/26 03:56:01 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -86db
2/12/26 13:53:03 WiFi disconnected.
2/12/26 13:53:06 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -59db
2/20/26 09:24:31 timeSync: Six week routine restart.

** Restart **

SD initialized.
2/20/26 14:24:32z Real Time Clock is running. Unix time 1771597472 
2/20/26 14:24:32z Reset reason: Software/System restart
2/20/26 14:24:32z Trace:  1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:1[7], 1:2[8], 9:0[8], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:5, 9:9, 1:3, 1:3, 1:6[1], 1:6[2], 1:6[2], 1:6[3], 1:5[20], 1:6[4], 20:0, 20:1
2/20/26 14:24:32z ESP8266 ID: 16295196, RTC PCF8523 (68)
2/20/26 14:24:32z IoTaWatt 5.0, Firmware version 02_08_03
2/20/26 14:24:32z SPIFFS mounted.
2/20/26 09:24:32 Local time zone: -5:00, using DST/BST when in effect.
2/20/26 09:24:32 device name: IotaWatt
2/20/26 09:24:32 HTTP server started
2/20/26 09:24:32 timeSync: service started.
2/20/26 09:24:32 statService: started.
2/20/26 09:24:32 dataLog: service started.
2/20/26 09:24:37 dataLog: Last log entry 02/20/26 09:24:30
2/20/26 09:24:37 historyLog: service started.
2/20/26 09:24:38 historyLog: Last log entry 02/20/26 09:24:00
2/20/26 09:24:39 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -56db
2/20/26 09:24:39 Updater: service started. Auto-update class is MINOR
2/20/26 09:24:39 HVAC: Started
2/20/26 09:24:40 HVAC: Last log entry 02/20/26 09:24:30
2/20/26 09:24:41 Updater: Auto-update is current for class MINOR.
2/20/26 09:24:41 TotalPower: Started
2/20/26 09:24:42 TotalPower: Last log entry 02/20/26 09:24:30
2/20/26 09:24:43 WaterSystem: Started
2/20/26 09:24:44 WaterSystem: Last log entry 02/20/26 09:24:30
2/27/26 09:41:46 Updater: Invalid response from server. HTTPcode: -4
3/01/26 02:27:17 WiFi disconnected.
3/01/26 02:27:20 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -83db
3/04/26 14:15:24 WiFi disconnected.
3/04/26 14:15:26 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -96db
3/06/26 13:09:19 WiFi disconnected.
3/06/26 13:10:21 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -90db
3/06/26 15:20:33 WiFi disconnected.
3/06/26 15:20:36 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -57db
3/18/26 10:48:26 WiFi disconnected.
3/18/26 10:49:27 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -85db
3/18/26 10:49:34 WiFi disconnected.
3/18/26 10:49:36 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=9, RSSI -87db

** Restart **

SD initialized.
3/19/26 01:41:09z Real Time Clock is running. Unix time 1773884469 
3/19/26 01:41:09z Reset Reason: Power-fail restart.
3/19/26 01:41:09z ESP8266 ID: 16295196, RTC PCF8523 (68)
3/19/26 01:41:09z IoTaWatt 5.0, Firmware version 02_08_03
3/19/26 01:41:09z SPIFFS mounted.
3/18/26 21:41:10 Local time zone: -5:00, using DST/BST when in effect.
3/18/26 21:41:10 device name: IotaWatt
3/18/26 21:41:13 HTTP server started
3/18/26 21:41:13 WiFi connected. SSID=Pegasus, IP=192.168.1.85, channel=1, RSSI -54db
3/18/26 21:41:13 timeSync: service started.
3/18/26 21:41:13 statService: started.
3/18/26 21:41:13 Updater: service started. Auto-update class is MINOR
3/18/26 21:41:13 dataLog: service started.
3/18/26 21:41:17 dataLog: Last log entry 03/18/26 21:26:55
3/18/26 21:41:17 Updater: Auto-update is current for class MINOR.
3/18/26 21:41:18 historyLog: service started.
3/18/26 21:41:20 historyLog: Last log entry 03/18/26 21:26:00
3/18/26 21:41:20 HVAC: Started
3/18/26 21:41:22 HVAC: Last log entry 03/18/26 21:26:55
3/18/26 21:41:23 TotalPower: Started
3/18/26 21:41:24 TotalPower: Last log entry 03/18/26 21:26:55
3/18/26 21:41:25 WaterSystem: Started
3/18/26 21:41:26 WaterSystem: Last log entry 03/18/26 21:26:50

Wi-Fi disconnection

@overeasy — Tue, 17 Mar 2026 16:28:51 +0000

That is not IoTaWatt graph+. It looks like gaps caused by communication lapses. Also, are you using an IoTaWatt uploader or some other method to accumulate that data?

What looks like a router log above shows differing IP addresses. The ESP8266 does not do well with changing IP addresses. Is it possible that the unit is switching between APs? If so, I think you need to restrict that from happening.

Wi-Fi disconnection

@DavidReche — Tue, 17 Mar 2026 09:02:09 +0000

Look at the number of outages between 7:00 and 9:00 AM today.
Do you think it could be the SD card?
Can you give me instructions on how to send a command to iotta to check the SD card?

Let me explain my network setup:

I have an ADSL router where I’ve set the Wi-Fi to channel 1: The iotta connects directly to the router because it’s only 2 meters away.
I have a mesh network with an Orbi configured as an access point (AP), set to Wi-Fi channel 6 (the iotta could connect to this AP as it’s also nearby).
I have a TP-Link access point in the garage set to Wi-Fi channel 11 (the iotta can’t reach this AP; it’s too far away).

I have them on separate channels precisely to avoid problems, but I’m mentioning it in case the ESP32 has any issues working with these Wi-Fi devices.

Do you have any idea what might be happening?

Wi-Fi disconnection

@DavidReche — Tue, 17 Mar 2026 07:41:37 +0000

Hi
Yes, the LED is definitely solid green, and that’s what’s causing these problems with the green LED.
Look, you can see that when you ping it, it stops responding and then suddenly starts responding again, but the log doesn’t say anything about it having stopped communicating.

** Restart **

SD initialized.
3/16/26 14:32:27z Real Time Clock is running. Unix time 1773671547 
3/16/26 14:32:27z Reset reason: Software/System restart
3/16/26 14:32:27z Trace:  1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:1[8], 1:2[9], 9:0[9], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:5, 9:9, 1:3, 10:2, 10:3
3/16/26 14:32:27z ESP8266 ID: 15866494, RTC PCF8523 (68)
3/16/26 14:32:27z IoTaWatt 5.0, Firmware version 02_08_03
3/16/26 14:32:27z SPIFFS mounted.
3/16/26 15:32:27 Local time zone: +1:00
3/16/26 15:32:27 device name: IotaWatt
3/16/26 15:32:27 HTTP server started
3/16/26 15:32:27 timeSync: service started.
3/16/26 15:32:27 statService: started.
3/16/26 15:32:27 dataLog: service started.
3/16/26 15:32:29 dataLog: Last log entry 03/16/26 15:32:25
3/16/26 15:32:32 historyLog: service started.
3/16/26 15:32:32 historyLog: Last log entry 03/16/26 15:32:00
3/16/26 15:32:32 WiFi connected. SSID=xx, IP=xx, channel=1, RSSI -74db
3/16/26 15:32:32 Updater: service started. Auto-update class is MINOR
3/16/26 15:32:33 Updater: Auto-update is current for class MINOR.
3/16/26 17:32:58 Updater: Invalid response from server. HTTPcode: -4

Buying IoTaWatt in Australia, or that will ship to Australia?

@garylovesbeer — Mon, 16 Mar 2026 21:08:05 +0000

Be great if this goes ahead!

Wi-Fi disconnection

@overeasy — Mon, 16 Mar 2026 14:44:33 +0000

That’s not a disconnection, its not logging at all. This is a datalog issue. Whether its caused by an SDcard problem or something else is not clear. I’ve never seen an issue like this without some indication on the LED. Are you sure the LED was solid green on during the extended outage about noon on the 12th through about midnight on the 14th?

Wi-Fi disconnection

@DavidReche — Mon, 16 Mar 2026 14:21:07 +0000

Yes, I’m in Spain, I’ve changed from zone 0 to zone 1. I’ll send you the graph; you’ll see there are disconnections.

Wi-Fi disconnection

@overeasy — Mon, 16 Mar 2026 13:34:46 +0000

Can you post a graph of voltage for the13th and 14th?

Not suspected as the problem but you have the timezone set to 0. Are you in Europe?

Wi-Fi disconnection

@DavidReche — Mon, 16 Mar 2026 11:18:08 +0000

It’s still solid green, like when everything is working properly.

I’ve ordered a new SD card to replace it, just in case.

Although I’ve tried removing the current one, formatting it, and copying the files back, it’s still giving me problems.

Any ideas?

Thanks so much for everything.

Wi-Fi disconnection

@DavidReche — Mon, 16 Mar 2026 06:20:46 +0000

It remains solid green, like when everything is OK.

Wi-Fi disconnection

@overeasy — Mon, 16 Mar 2026 01:11:02 +0000

It looks like the unit stops logging data. What is the state of the LED when you lose access?

CT Installation Questions (120/240)

@overeasy — Mon, 16 Mar 2026 01:02:41 +0000

https://docs.iotawatt.com/en/master/CTbasics.html#v-split-phase-circuits

I’d double check the dryer. Most use a 120V motor for the tumbler and 240V for the heater. The heater is a much bigger load so you might not be noticing the motor load. This is a good candidate for the reversed conductors in one CT as described in the link above.

Also, not clear where you have the IoTaWatt but sounds like you may have placed it inside the panel. That would be a definite code violation and the IoTaWatt is not safety certified for that.

CT Installation Questions (120/240)

@ANZAC — Mon, 16 Mar 2026 00:14:56 +0000

I was able to figure out the hot tub, dryer, range, furnace/glycol pump all used both legs equally, so doubled those and freed up some CTs to bring on those new circuits. I basically watched both legs and created an output that was leg 1 - leg 2 to see any big differences.

BUT the oven is a combo unit with a built in microwave. Figured out that for the oven it uses both legs but for the microwave just one, so a huge asymmetry of power, so that has to keep two CTs.

Also found my breaker panel had the labels for range and oven were reversed!

It also worked out nicely with 7 CTs in the first panel, and 7 CTs in the second panel which made the cable routing neater.

Thanks again for the help.

CT Installation Questions (120/240)

@Linwood — Sun, 15 Mar 2026 21:52:51 +0000

I am not an electrician but I’m pretty sure you can’t have wires going out a knockout without a connector (sharp edges on the metal and such, probably chance of critters crawling into the hole). But to be sure check with a real electrician. Or spend the 50 cents.

Postscript: I just realized you meant the stud up against the size. Not sure there. You can also go out the bottom thru the stud and back up. If you find out the real answer about the stud please post.

Postscript 2: I put my iotawatt in a separate box and run conduit into the panel for the low voltage wiring to the CT’s. Actually two pieces of conduit, one I ran two 120v circuits for outlets for the reference transformers for each leg (overkill with both), and one for low voltage. I’m not sure the conduit needs to be separate, but the HV and LV in the separate plastic box has to have a barrier. This is a sprinkler box that works nicely for this.

CT Installation Questions (120/240)

@ANZAC — Sun, 15 Mar 2026 21:18:01 +0000

Yes, I considered two units but I was trying to get maximum bang for the buck – so getting 2 extra 200A CTs seemed easier and cheaper and then all the data is one place too.

While some of the circuit info is interesting (the hot tub OMG!) the panel total numbers are the most important to me. I need to find out if code allows me to pop two knock outs and drill a hole through the stud between both panels to route the CT wires across. I would think this is ok for low voltage without a nipple/connector but there’s always something surprising in the NEC.

I assume people just sandwich the 5v power and 9v reference cables under the break panel fascia on their way to the outlet?

CT Installation Questions (120/240)

@Linwood — Sun, 15 Mar 2026 20:52:07 +0000

A prior house I had two 200a panels, I bought an iotawatt for each. At the most recent house I had one panel very full, so I just used both iotawatts and all the CT’s.

There are always surprises. I’m working today because I couldn’t reconcile my 200a input and the CT’s I had, and found a landscape transformer with lights turned off actually was drawing 90w full time just to keep the lights ready to turn on (they were wifi lights so it’s not a huge surprise but a bit of one).

There are always surprises when you dive into the iotawatt data.

Wi-Fi disconnection

@DavidReche — Sun, 15 Mar 2026 20:23:11 +0000

** Restart **

SD initialized.
3/14/26 22:55:34z Real Time Clock is running. Unix time 1773528934 
3/14/26 22:55:34z Reset Reason: Power-fail restart.
3/14/26 22:55:34z ESP8266 ID: 15866494, RTC PCF8523 (68)
3/14/26 22:55:34z IoTaWatt 5.0, Firmware version 02_08_03
3/14/26 22:55:34z SPIFFS mounted.
3/14/26 22:55:34z Local time zone: +0:00
3/14/26 22:55:34z device name: IotaWatt
3/14/26 22:55:37z Connecting with WiFiManager.
3/14/26 22:55:42z HTTP server started
3/14/26 22:55:42z WiFi connected. SSID=xx, IP=192.168.xx, channel=1, RSSI -58db
3/14/26 22:55:42z timeSync: service started.
3/14/26 22:55:49z statService: started.
3/14/26 22:55:49z Updater: service started. Auto-update class is MINOR
3/14/26 22:55:50z dataLog: service started.
3/14/26 22:55:53z dataLog: Last log entry 03/12/26 10:39:20
3/14/26 22:55:53z Updater: Auto-update is current for class MINOR.
3/14/26 22:55:54z historyLog: service started.
3/14/26 22:55:55z historyLog: Last log entry 03/12/26 10:39:00

** Restart **

SD initialized.
3/14/26 23:09:41z Real Time Clock is running. Unix time 1773529781 
3/14/26 23:09:41z Reset Reason: Power-fail restart.
3/14/26 23:09:41z ESP8266 ID: 15866494, RTC PCF8523 (68)
3/14/26 23:09:41z IoTaWatt 5.0, Firmware version 02_08_03
3/14/26 23:09:41z SPIFFS mounted.
3/14/26 23:09:41z Local time zone: +0:00
3/14/26 23:09:41z device name: IotaWatt
3/14/26 23:09:44z Connecting with WiFiManager.
3/14/26 23:11:53z Did not connect after power-fail. Restarting to reset WiFi.

** Restart **

SD initialized.
3/14/26 23:11:54z Real Time Clock is running. Unix time 1773529914 
3/14/26 23:11:54z Reset reason: Software/System restart
3/14/26 23:11:54z Trace:  34:10[11], 34:30, 34:5, 34:5, 34:5, 34:6[3], 34:10[4], 34:30, 34:15, 34:5, 34:5, 34:5, 34:6[1], 34:10[3], 34:5, 34:5, 34:5, 34:6[4], 34:10[3], 34:30, 34:10[4], 34:30, 11:31[3], 11:30[3], 11:35, 11:36, 11:35, 11:40, 11:45, 11:50, 11:55, 11:70
3/14/26 23:11:54z ESP8266 ID: 15866494, RTC PCF8523 (68)
3/14/26 23:11:54z IoTaWatt 5.0, Firmware version 02_08_03
3/14/26 23:11:54z SPIFFS mounted.
3/14/26 23:11:54z Local time zone: +0:00
3/14/26 23:11:54z device name: IotaWatt
3/14/26 23:11:54z HTTP server started
3/14/26 23:11:54z timeSync: service started.
3/14/26 23:11:54z statService: started.
3/14/26 23:11:55z dataLog: service started.
3/14/26 23:11:58z dataLog: Last log entry 03/14/26 23:08:20
3/14/26 23:11:59z historyLog: service started.
3/14/26 23:12:01z historyLog: Last log entry 03/14/26 23:08:00
3/14/26 23:12:02z WiFi connected. SSID=xx, IP=192.168.xx, channel=1, RSSI -62db
3/14/26 23:12:02z Updater: service started. Auto-update class is MINOR
3/14/26 23:12:03z Updater: Auto-update is current for class MINOR.
3/15/26 00:12:21z Updater: Invalid response from server. HTTPcode: -4

** Restart **

SD initialized.
3/15/26 12:04:14z Real Time Clock is running. Unix time 1773576254 
3/15/26 12:04:14z Reset Reason: Power-fail restart.
3/15/26 12:04:14z ESP8266 ID: 15866494, RTC PCF8523 (68)
3/15/26 12:04:14z IoTaWatt 5.0, Firmware version 02_08_03
3/15/26 12:04:14z SPIFFS mounted.
3/15/26 12:04:14z Local time zone: +0:00
3/15/26 12:04:14z device name: IotaWatt
3/15/26 12:04:17z Connecting with WiFiManager.
3/15/26 12:04:20z HTTP server started
3/15/26 12:04:21z WiFi connected. SSID=xx, IP=192.168.xx, channel=1, RSSI -58db
3/15/26 12:04:21z timeSync: service started.
3/15/26 12:04:21z statService: started.
3/15/26 12:04:21z Updater: service started. Auto-update class is MINOR
3/15/26 12:04:21z dataLog: service started.
3/15/26 12:04:23z dataLog: Last log entry 03/15/26 11:02:40
3/15/26 12:04:23z Updater: Auto-update is current for class MINOR.
3/15/26 12:04:26z historyLog: service started.
3/15/26 12:04:26z historyLog: Last log entry 03/15/26 11:02:00


You can check the log to see if you can diagnose where the problem is, thanks

CT Installation Questions (120/240)

@ANZAC — Sun, 15 Mar 2026 20:17:52 +0000

Thanks, looks like I have everything set up, except for my 200A CTs for the first panel.

Sucks that I ran out of inputs, I chose the oven, but didn’t have room for dryer or range. All three are “user driven” unlike some of the other big ones (hot tub, furnace) which are more environment driven.

The other interesting thing is the well controller bounces around each leg between 0-9 W randomly. It is a variable drive so it must be in a “ramped down” rather than “shut off” state or something. It also has a cooling fan which I would think would probably be 120V along with the control brain.

I guess I will run for a few days and see how things look.

I’m trying to scope out my solar system design – and I got to the point where I realized I was over-sizing it based on everything’s maximum capacity. Now that a lot of the inverters do grid pass through up to 200A, I realized I didn’t have to get it perfect (at least for when the grid is up), so trying to see if I can make a single inverter (the new Sol Ark 18k) cover everything vs two 15ks.

Thanks again for the help.

CT Installation Questions (120/240)

@Linwood — Sun, 15 Mar 2026 19:50:44 +0000

Generally speaking the double is used when the device only uses 240v. I would expect most well pumps to only be 240v, but if there are control circuits above for pump control or report, they may operate off of 110v. A lot of cases are just that – heavy draw users at 240v with controls , gauges, displays at 110v.

It’s never wrong to use 2 CT’s and not double. If it’s a huge draw item (like a dryer, range) it’s likely the 110v component is very small compared to the main draw. Some people just decide to ignore this minor difference and double (double the larger leg errs high, double the smaller errs low, take your pick). Putting on two CT’s and going through the normal modes of operation is a good way to tell how much it matters (if at all).

Just because manufacturers are cheap, if the device itself has 4 wires it’s likely it uses 110v internally. That doesn’t mean the electrician that wired it did it correctly of course, but if you see 4 wires using two CT’s is the most likely correct way. Unless you run out of CT’s and don’t need high accuracy on those, then just pick one.

CT Installation Questions (120/240)

@ANZAC — Sun, 15 Mar 2026 18:15:56 +0000

So my house has two 200A panels. One of these panels has a 125A breaker that feeds my shop.

I have the basic kit and also ordered two additional 200A CTs for the 2nd panel.

The iotawatt web site says (re “Double” option) :

”In North American split-phase power systems (120V/240V), all circuits are assumed to be 120V. When this option is selected, power will be computed using double the value of the reference voltage, or nominally 240V. Use this for 240V circuits where one CT has been applied to one of the conductors and there is no neutral (white) wire used by the appliance. Typical circuits would be Water Heater, Water Pump, Mini-Split Heat-Pump. There are other ways to monitor 240V circuits as well.”

My well water pump definitely has four wires going to it (ie a neutral) but I think only 3 at the well head. Should I just use 2 CTs here?

Also, my dryer is definitely a 4 wire cable and does not have bonded neutral, should I also use two CTs?

My total list of 240V circuits is:

Shop (which I assume has to be 2 CTs because there are circuits on both legs
Furnace (electric geothermal furnace with an external glycol pump - not sure how the pump is wired as it can be wired for either 120 or 240)
Well pump controller (and pump)
Range
Oven
Hot Tub
Dryer

Any advice on 2 CTs vs 1 CT or do I really need to inspect how each one is wired?

What if I started with 2 CTs on each, and then it the consumption between legs is somewhat identical, switch to 1 CT and select double?

And what are the “other ways” to monitor 240v circuits?

Thanks.

Wi-Fi disconnection

@overeasy — Fri, 13 Mar 2026 21:07:59 +0000

Has anything changed with your WiFi, including firmware update?

Probably a red-herring but was it working with HA before this started happening?

Not clear on this. What exactly did you reconfigure.

Assigning a static LAN IP is pretty standard. Are you saying that doing so causes different problems?

This smells like a router problem managing the zeroconfig (.local) protocol. Is the channel of your AP fixed? If you have multiple APs, is the IoTaWatt bound to one of them?

Wi-Fi disconnection

@DavidReche — Fri, 13 Mar 2026 08:43:28 +0000

For several weeks now, my iotawatt has been giving me Wi-Fi problems.
It’s connected to Home Assistant, and it keeps losing connection.
I have to restart the device and check the IP address assigned by the router locally and reconfigure it. But the next day, the problem persists.
I’ve assigned a static IP address using the MAC address, but that also gives me problems.
I’ve changed the 5VDC power supply, but nothing has worked.

I try to access it locally at http://iotawatt.local/, but it doesn’t connect, although the device can still ping. I have to unplug the device, but after a few hours, the problem returns.

Is anyone else experiencing this problem?

Thanks a lot.

CircuitIQ - Ordering Kits, Update & Contact

@rrvzts4q — Thu, 12 Mar 2026 15:11:37 +0000

I have been using a Ted Pro from The Energy Detective for years. It is no longer supported and most functions no longer work. I was ready to buy the IoTaWatt system but I discovered them to late. Glad to see a new supplier.

Buying IoTaWatt in Australia, or that will ship to Australia?

@adampetrovic — Tue, 10 Mar 2026 08:02:43 +0000

Count me in!

Iotawatt won't save graph

@overeasy — Sun, 08 Mar 2026 16:00:14 +0000

Don’t know what’s going on with discourse. I get the same thing. I’ve modified the post to take you to github where there is a download button for the file. Probably better than putting a static copy in the forum anyway.

Iotawatt won't save graph

@OffGridInTheCity — Sun, 08 Mar 2026 14:41:22 +0000

When I click on the graph2.js to download I get and can’t seem to get it.

Iotawatt won't save graph

@murphy — Sat, 07 Mar 2026 19:56:34 +0000

Thank you! I did seem to figure it out by manually setting the custom date option, then selecting the dates. It would seem that if I just select dates and let it change to custom dates on its own, it won’t save the changes.
Thank you!!!

Iotawatt won't save graph

@overeasy — Fri, 06 Mar 2026 22:30:58 +0000

Upon further examination I see what is going on, why you thought it used to work and now doesn’t and how to either fix it or work around it.

I can recreate the problem by selecting any relative period for the graph and subsequently changing the dates either by explicitly modifying the start or end date, using the zoom/forward/back keys or selecting a section of the existing graph with the mouse. Notwithstanding the period shown is changed to “custom dates”, such a graph when saved restores with the original relative period selected prior to date override and generates the appropriate relative dates. .

On the other hand, if “custom dates” is explicitly selected from the period drop-down, any graph subsequently saved will retain the dates at the time of saving.

I would call this a bug in that the “period” drop-down is automatically changes to “custom dates” whenever you implicitly change the date range, so this graph2.js file will fix the problem in either case. Simply download it and then upload to your IoTaWatt root.

CircuitIQ - Ordering Kits, Update & Contact

@nereocystis — Thu, 05 Mar 2026 05:52:16 +0000

I received my IotaWatt, from CircuitIQ.

Now, I have to install it.

Iotawatt won't save graph

@overeasy — Tue, 03 Mar 2026 02:27:09 +0000

I took a quick look and would have to say that I don’t think it ever worked in graph+. That said, the times are saved with the graph so it should be possible. Its been a long time since I worked on that JQUERY code so it will take a few days before I can come back up to speed and make that work. I’ll get back to you.

Iotawatt won't save graph

@murphy — Mon, 02 Mar 2026 20:48:28 +0000

I used to create graphs without problems, give it a name, hit the save button, and I can access that graph anytime.
Now, when I try to save a graph, Iotawatt won’t save the date settings. I configure the date from (start) Feb 17 2026 to (end) Feb 16 2027, but when I try recall the graph, the date is today for both the start and end dates.

Nothing I do seems to be able to force it to save the proper date range.
I tried a reboot but it didn’t work.

CircuitIQ - Ordering Kits, Update & Contact

@CircuitIQ — Mon, 02 Mar 2026 16:05:35 +0000

Hi @ANZAC . Apologies, does not seem like anything came through. Could you provide me your email and I will reach out directly.

Best regards,

CircuitIQ - Ordering Kits, Update & Contact

@ANZAC — Mon, 02 Mar 2026 15:35:44 +0000

@CircuitIQ just checking, I sent you both email on Feb 26, did you receive it? Thanks.

Buying IoTaWatt in Australia, or that will ship to Australia?

@DikGatDolf — Sun, 01 Mar 2026 21:35:14 +0000

Update: I’m all out (Thanks for the support, guys!)

I am considering doing another run of 20 or 25 units, but I would need to print enclosures as well since the current distributor isn’t too keen on homebrew IotaWatt units being sold in OG branded enclosures… understandable, I guess.

Once I have designed new enclosure and get a manufacturing price, I will advertise on this forum again to guage interest before I order PCB’s, parts and enclosures.

Mind you, it will be mostly aimed at the Aussie market.

Dimensions with connectors?

@trapacivet — Sun, 01 Mar 2026 02:57:07 +0000

For all those in the future looking at how much room is needed. Here’s a picture. My guestimate for minimum comfortable enclosure is 17cm x 19cm

Mechanical Dimensions for the Iotawatt

@trapacivet — Sun, 01 Mar 2026 00:42:47 +0000

I had the question of how big it was with the CT’s connected. Here’s a picture. My guestimations for future people looking is 17xm x 19 cm would be comfortable minimum.

CircuitIQ - Ordering Kits, Update & Contact

@ANZAC — Thu, 26 Feb 2026 23:25:38 +0000

Thanks. I sent the mail on 2/10 to [email protected]

I’ll fwd it to them.

CircuitIQ - Ordering Kits, Update & Contact

@CircuitIQ — Thu, 26 Feb 2026 22:05:46 +0000

Hi @ANZAC. Apologies, I do not seem to have received an email.

Please send an email to both [email protected] and [email protected] and we will see if we are able to accommodate you.

CircuitIQ - Ordering Kits, Update & Contact

@ANZAC — Thu, 26 Feb 2026 20:00:28 +0000

Hi @circuitiq – I sent some email to CircuitIQ a few weeks ago but didn’t get a reply.
You had CTs listed in the shop but they were removed. I emailed to try and see if you could provide them with a system order.

I didn’t get a reply, so I just ordered a system and you shipped it.

I need two additional 200A CTs because we have 2 x 200A panels in our house.

Iotawatt Slow, Rapid Flashing Green LED

@BenAus — Wed, 25 Feb 2026 03:29:16 +0000

Thanks

I have looked into this more and it seems to be a common issue with TP Link Deco Mesh units and ESP32/ESP8266 devices and constant drop outs and reconnects.

Thanks

Ben

Iotawatt Slow, Rapid Flashing Green LED

@overeasy — Fri, 20 Feb 2026 17:21:40 +0000

The IoTaWatt is not disconnecting from the AP. In the picture it looks like you have some sort of AP on top of the IoTaWatt box and that it is connected to something via ethernet. I don’t see a power cable so it might be POE? In any event, perhaps what you are seeing is some sort of disconnect between that AP and whatever its connected to.

Probably not the cause, but an RSSI of -27 indicates a huge signal strength. In fact, I don’t ever recall seeing such an RSSI in user posts or in my own multi IoTaWatt environment with several Ubiquiti APs in close proximity. If you can dial it down to an RSSI maybe in the -60s that should be fine.

If you know the IP address assigned (You have it edited out of the log), have you tried to get to it using the IP address rather than iotawatt.local?

Lastly, to be clear, this appears to be a purely WiFi issue external to the IoTaWatt.

Iotawatt Slow, Rapid Flashing Green LED

@BenAus — Fri, 20 Feb 2026 04:14:55 +0000

This is the log

The connects/disconnects alert me from my Wifi system but for some reason dont show in the iotawatt log. When the disconnects happen I cant access the iotawatt

Ben

SD initialized.
2/19/26 04:44:54z Real Time Clock is running. Unix time 1771476294 
2/19/26 04:44:54z Reset reason: Software/System restart
2/19/26 04:44:54z Trace:  1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:3, 1:1[11], 1:2[12], 9:0[12], 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:5, 9:9, 1:3, 10:2, 10:3
2/19/26 04:44:54z ESP8266 ID: 15159939, RTC PCF8523 (68)
2/19/26 04:44:54z IoTaWatt 6.4, Firmware version 02_08_03
2/19/26 04:44:54z SPIFFS mounted.
2/19/26 14:44:54 Local time zone: +10:00
2/19/26 14:44:54 device name: IotaWatt
2/19/26 14:44:54 HTTP server started
2/19/26 14:44:54 timeSync: service started.
2/19/26 14:44:54 statService: started.
2/19/26 14:44:54 dataLog: service started.
2/19/26 14:44:54 dataLog: Last log entry 02/19/26 14:44:50
2/19/26 14:44:59 historyLog: service started.
2/19/26 14:44:59 historyLog: Last log entry 02/19/26 14:44:00
2/19/26 14:44:59 WiFi connected. SSID=, IP=, channel=6, RSSI -27db
2/19/26 14:44:59 Updater: service started. Auto-update class is MINOR
2/19/26 14:44:59 Mains_Power: Started
2/19/26 14:44:59 Mains_Power: Last log entry 02/19/26 14:44:50
2/19/26 14:45:01 Updater: Auto-update is current for class MINOR.

LED sequence: Red Green Red

@overeasy — Fri, 20 Feb 2026 03:23:08 +0000

The docs say that RGR means the datalog is corrupted. When you say you “recovered” all except the IoTaLog I assume that means you copied iotalog.log and histlog.log. One of those is corrupted, so that’s your problem.

I’d suggest you remove the SD card, delete the iotawatt directory, replace the SD card and restart. It should create new datalogs as well as a new message log. You will of course be starting fresh with no history.