No WIFI after IotaWatt restart

Support
1

If I reboot my IotaWatt, I also need to reboot my WIFI router, or it will never connect.

It will do the Red-Green-Green sequence for 30-60 seconds, then go to quick red flash.

If I reboot my WIFI router, then IotaWatt, it work well.

Here is the log before and after the reboot of the WIFI router.

It’s a standard ISP router with 2.4/5 Ghz activated


** Restart **

SD initialized.
3/31/25 17:03:33z Real Time Clock is running. Unix time 1743440613 
3/31/25 17:03:33z Reset reason: Hardware Watchdog
3/31/25 17:03:33z Trace:  34:30, 34:10[8], 34:30, 34:10[9], 34:30, 34:10[10], 34:30, 34:10[11], 34:30, 34:10[12], 34:30, 34:10[13], 34:30, 34:10[14], 34:30, 34:5, 34:5, 34:5, 34:6[3], 34:10[1], 34:30, 34:10[2], 11:31[3], 11:30[3], 11:35, 11:36, 11:35, 11:40, 11:45, 11:50, 11:55, 11:70
3/31/25 17:03:33z ESP8266 ID: 15160134, RTC PCF8523 (68)
3/31/25 17:03:33z IoTaWatt 6.4, Firmware version 02_08_03
3/31/25 17:03:33z SPIFFS mounted.
3/31/25 13:03:33 Local time zone: -5:00, using DST/BST when in effect.
3/31/25 13:03:33 device name: IotaWatt
3/31/25 13:03:33 HTTP server started
3/31/25 13:03:33 timeSync: service started.
3/31/25 13:03:33 statService: started.
3/31/25 13:03:33 dataLog: service started.
3/31/25 13:03:33 dataLog: Last log entry 03/31/25 13:02:00
3/31/25 13:03:38 historyLog: service started.
3/31/25 13:03:38 historyLog: Last log entry 03/31/25 13:01:00

** Restart **

SD initialized.
3/31/25 17:06:41z Real Time Clock is running. Unix time 1743440801 
3/31/25 17:06:41z Reset Reason: Power-fail restart.
3/31/25 17:06:41z ESP8266 ID: 15160134, RTC PCF8523 (68)
3/31/25 17:06:41z IoTaWatt 6.4, Firmware version 02_08_03
3/31/25 17:06:41z SPIFFS mounted.
3/31/25 13:06:41 Local time zone: -5:00, using DST/BST when in effect.
3/31/25 13:06:41 device name: IotaWatt
3/31/25 13:06:44 Connecting with WiFiManager.
3/31/25 13:06:50 HTTP server started
3/31/25 13:06:50 WiFi connected. SSID=LUNINFO, IP=192.168.2.170, channel=11, RSSI -38db
3/31/25 13:06:50 timeSync: service started.
3/31/25 13:06:53 statService: started.
3/31/25 13:06:53 Updater: service started. Auto-update class is MINOR
3/31/25 13:06:53 dataLog: service started.
3/31/25 13:06:53 dataLog: Last log entry 03/31/25 13:06:25
3/31/25 13:06:57 Updater: Auto-update is current for class MINOR.
3/31/25 13:06:58 historyLog: service started.
3/31/25 13:06:58 historyLog: Last log entry 03/31/25 13:06:00
2

There are two remarkable thing in the log:

The first restart reason is Hardware watchdog. That is unusual.

The WiFi RSSI which is very strong. In fact, I can’t ever recall seeing an RSSI in that range before. I have no idea if that is causing this issue, but it is somewhat related.

If you upload the whole message log (you can download it with the file manager), I’ll take a look.

3

Here is the log.

The device is 2 feet beside the router if that info can help.
iotamsgs.txt (26.4 KB)

4

My guess is that the basic problem has something to do with your WiFi. It looks like you had extracurricular activity on the 28th. I see that you have been trying to get Emoncms upload working, that you deleted the datalogs and at one point attempted to upload a new config file using the file-manager. Perhaps all that has nothing to do with it, but my guess is that there is more to it.

Can you post a copy of your config.txt file please?

5

Yes I tried to do emoncms, remove everything, and reconfigure today, since all my CT was now connected

Here is the config file
config.txt (4.2 KB)

6

OK, that looks pretty clean. Is it still running? Is the Emoncms uploading as seen in the uploaders tab of the status display?

7

Yep running fine, will run fine unless it need to be restarted

image

8

Any chance you can put some distance between it and the router?

Also, if it restarts and does not connect, after an hour it will restart again. I’m curious to see if that results in a connection w/o router restart.

9

I will try to put some distance, sadly the incoming fiber is just beside the electrical panel, and don’t have much free movement.

Ok next time it happen will wait an hour and see.