WiFi Connection Issues

Support
1

Hi IoTaWatt community,

Just got an IoTaWatt and have installed it permanently next to my panel. Initial setup went smoothly, although I missed the step about assigning a static IP in the documentation so had to reboot my router and PC to get it connected again the 2nd morning.

I went away for a few days and was excited to check the data when I got home but I found the device unconnected again. Status light is pulsing green, seems okay. I still see the reserved IP address on my router dashboard but can’t establish a connection on iotawatt.local (or the assigned IP address).

Though it was weak wifi signal (~-70 dB) so I added an extender in the area. Now I get about -50 dB at the device but I still can’t access it.

Looking at my other network devices, I see that another AP has assigned it a second IP address and that one is not reachable either.

Any thoughts on the problem? I’m more of a mechanical guy than a network engineer so probably something I have setup wrong.

Fiber line comes in to house and to a Nighthawk CAX80. That feeds a Ring Alarm Pro base station (hard wired) with eero secondary AP. eero 6 extender is in basement next to IoTaWatt.

Could there be a conflict between the Nighthawk and eero network? Should I block the IoTaWatt on the Nighthawk and remove that reserved IP?

Any thoughts are appreciated, thanks!

-Jake

2

If the led is green, the IoTaWatt thinks it is connected. If you can get access again with the app, please capture the message log and post. It sounds like you have routing issues on your network. I had a mesh network at one time and plenty of problems. I now have ubiquitous wired APs and zero problems with as many as six or more units running at various locations and APs.

3

Yeah I think it’s certainly a network problem, I just can’t get it recognized again even when I try blocking it on the eero devices.

Is there a way to force a reset of network settings on the IoTaWatt? Otherwise I’m not sure if I’ll ever be able to get access to it again to retrieve the log.

4

Just got it back visibile on the main router, had to block and pause activity on the eero for IoTaWatt plus the two espressif instances.

Here’s the log:
8/25/24 14:41:12 dataLog: Last log entry 08/25/24 14:40:45
8/25/24 14:41:12 Updater: Auto-update is current for class MINOR.
8/25/24 14:41:14 historyLog: service started.
8/25/24 14:41:14 historyLog: Last log entry 08/25/24 14:40:00
8/26/24 14:39:47 WiFi disconnected.
8/26/24 14:40:04 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.1.157, channel=4, RSSI -62db
8/26/24 16:48:44 WiFi disconnected.
8/26/24 16:48:49 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -69db

** Restart **

SD initialized.
8/28/24 01:14:58z Real Time Clock is running. Unix time 1724807698
8/28/24 01:14:58z Reset Reason: Power-fail restart.
8/28/24 01:14:58z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/28/24 01:14:58z IoTaWatt 5.0, Firmware version 02_08_03
8/28/24 01:14:58z SPIFFS mounted.
8/27/24 21:14:58 Local time zone: -5:00, using DST/BST when in effect.
8/27/24 21:14:58 device name: IotaWatt
8/27/24 21:15:01 Connecting with WiFiManager.
8/27/24 21:15:06 HTTP server started
8/27/24 21:15:07 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -72db
8/27/24 21:15:07 timeSync: service started.
8/27/24 21:15:07 statService: started.
8/27/24 21:15:07 Updater: service started. Auto-update class is MINOR
8/27/24 21:15:07 dataLog: service started.
8/27/24 21:15:09 dataLog: Last log entry 08/27/24 21:14:45
8/27/24 21:15:09 Updater: Auto-update is current for class MINOR.
8/27/24 21:15:12 historyLog: service started.
8/27/24 21:15:12 historyLog: Last log entry 08/27/24 21:14:00

** Restart **

SD initialized.
8/29/24 16:02:30z Real Time Clock is running. Unix time 1724947350
8/29/24 16:02:30z Reset Reason: Power-fail restart.
8/29/24 16:02:30z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 16:02:30z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 16:02:30z SPIFFS mounted.
8/29/24 12:02:30 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 12:02:30 device name: IotaWatt
8/29/24 12:02:33 Connecting with WiFiManager.
8/29/24 12:02:38 HTTP server started
8/29/24 12:02:38 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -69db
8/29/24 12:02:38 timeSync: service started.
8/29/24 12:02:38 statService: started.
8/29/24 12:02:38 Updater: service started. Auto-update class is MINOR
8/29/24 12:02:39 dataLog: service started.
8/29/24 12:02:41 dataLog: Last log entry 08/29/24 12:02:00
8/29/24 12:02:42 Updater: Auto-update is current for class MINOR.
8/29/24 12:02:43 historyLog: service started.
8/29/24 12:02:43 historyLog: Last log entry 08/29/24 12:01:00

** Restart **

SD initialized.
8/29/24 17:48:32z Real Time Clock is running. Unix time 1724953712
8/29/24 17:48:32z Reset Reason: Power-fail restart.
8/29/24 17:48:32z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 17:48:32z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 17:48:32z SPIFFS mounted.
8/29/24 13:48:32 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 13:48:32 device name: IotaWatt
8/29/24 13:48:35 Connecting with WiFiManager.
8/29/24 13:48:38 HTTP server started
8/29/24 13:48:38 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -54db
8/29/24 13:48:38 timeSync: service started.
8/29/24 13:48:38 statService: started.
8/29/24 13:48:38 Updater: service started. Auto-update class is MINOR
8/29/24 13:48:38 dataLog: service started.
8/29/24 13:48:42 dataLog: Last log entry 08/29/24 13:48:15
8/29/24 13:48:42 Updater: Auto-update is current for class MINOR.
8/29/24 13:48:43 historyLog: service started.
8/29/24 13:48:43 historyLog: Last log entry 08/29/24 13:48:00

** Restart **

SD initialized.
8/29/24 19:30:57z Real Time Clock is running. Unix time 1724959857
8/29/24 19:30:57z Reset Reason: Power-fail restart.
8/29/24 19:30:57z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 19:30:57z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 19:30:57z SPIFFS mounted.
8/29/24 15:30:57 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 15:30:57 device name: IotaWatt
8/29/24 15:31:00 Connecting with WiFiManager.
8/29/24 15:31:03 HTTP server started
8/29/24 15:31:03 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -56db
8/29/24 15:31:04 timeSync: service started.
8/29/24 15:31:04 statService: started.
8/29/24 15:31:04 Updater: service started. Auto-update class is MINOR
8/29/24 15:31:04 dataLog: service started.
8/29/24 15:31:07 dataLog: Last log entry 08/29/24 15:27:00
8/29/24 15:31:08 Updater: Auto-update is current for class MINOR.
8/29/24 15:31:09 historyLog: service started.
8/29/24 15:31:10 historyLog: Last log entry 08/29/24 15:27:00

** Restart **

SD initialized.
8/29/24 19:37:58z Real Time Clock is running. Unix time 1724960278
8/29/24 19:37:58z Reset Reason: Power-fail restart.
8/29/24 19:37:58z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 19:37:58z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 19:37:58z SPIFFS mounted.
8/29/24 15:37:58 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 15:37:58 device name: IotaWatt
8/29/24 15:38:01 Connecting with WiFiManager.
8/29/24 15:38:07 HTTP server started
8/29/24 15:38:07 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -56db
8/29/24 15:38:07 timeSync: service started.
8/29/24 15:38:10 statService: started.
8/29/24 15:38:10 Updater: service started. Auto-update class is MINOR
8/29/24 15:38:10 dataLog: service started.
8/29/24 15:38:13 dataLog: Last log entry 08/29/24 15:36:35
8/29/24 15:38:14 Updater: could not parse versions.json file.
8/29/24 15:38:15 historyLog: service started.
8/29/24 15:38:15 historyLog: Last log entry 08/29/24 15:36:00

** Restart **

SD initialized.
8/29/24 19:40:11z Real Time Clock is running. Unix time 1724960411
8/29/24 19:40:11z Reset Reason: Power-fail restart.
8/29/24 19:40:11z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 19:40:11z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 19:40:11z SPIFFS mounted.
8/29/24 15:40:11 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 15:40:11 device name: IotaWatt
8/29/24 15:40:14 Connecting with WiFiManager.
8/29/24 15:40:18 HTTP server started
8/29/24 15:40:18 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -55db
8/29/24 15:40:18 timeSync: service started.
8/29/24 15:40:21 statService: started.
8/29/24 15:40:21 Updater: service started. Auto-update class is MINOR
8/29/24 15:40:22 dataLog: service started.
8/29/24 15:40:25 dataLog: Last log entry 08/29/24 15:39:55
8/29/24 15:40:25 Updater: could not parse versions.json file.
8/29/24 15:40:26 historyLog: service started.
8/29/24 15:40:26 historyLog: Last log entry 08/29/24 15:39:00

** Restart **

SD initialized.
8/29/24 19:44:08z Real Time Clock is running. Unix time 1724960648
8/29/24 19:44:08z Reset Reason: Power-fail restart.
8/29/24 19:44:08z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 19:44:08z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 19:44:08z SPIFFS mounted.
8/29/24 15:44:08 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 15:44:08 device name: IotaWatt
8/29/24 15:44:11 Connecting with WiFiManager.
8/29/24 15:44:17 HTTP server started
8/29/24 15:44:17 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -56db
8/29/24 15:44:17 timeSync: service started.
8/29/24 15:44:20 statService: started.
8/29/24 15:44:20 Updater: service started. Auto-update class is MINOR
8/29/24 15:44:20 dataLog: service started.
8/29/24 15:44:24 dataLog: Last log entry 08/29/24 15:43:55
8/29/24 15:44:24 Updater: could not parse versions.json file.
8/29/24 15:44:25 historyLog: service started.
8/29/24 15:44:25 historyLog: Last log entry 08/29/24 15:43:00
8/29/24 15:45:02 WiFi disconnected.
8/29/24 15:45:05 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -72db

** Restart **

SD initialized.
8/29/24 19:46:34z Real Time Clock is running. Unix time 1724960794
8/29/24 19:46:34z Reset Reason: Power-fail restart.
8/29/24 19:46:34z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 19:46:34z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 19:46:34z SPIFFS mounted.
8/29/24 15:46:34 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 15:46:34 device name: IotaWatt
8/29/24 15:46:37 Connecting with WiFiManager.
8/29/24 15:46:43 HTTP server started
8/29/24 15:46:43 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -72db
8/29/24 15:46:43 timeSync: service started.
8/29/24 15:46:46 statService: started.
8/29/24 15:46:46 Updater: service started. Auto-update class is MINOR
8/29/24 15:46:46 dataLog: service started.
8/29/24 15:46:50 dataLog: Last log entry 08/29/24 15:46:05
8/29/24 15:46:50 Updater: could not parse versions.json file.
8/29/24 15:46:51 historyLog: service started.
8/29/24 15:46:51 historyLog: Last log entry 08/29/24 15:46:00

** Restart **

SD initialized.
8/29/24 19:53:34z Real Time Clock is running. Unix time 1724961214
8/29/24 19:53:34z Reset Reason: Power-fail restart.
8/29/24 19:53:34z ESP8266 ID: 12687021, RTC PCF8523 (68)
8/29/24 19:53:34z IoTaWatt 5.0, Firmware version 02_08_03
8/29/24 19:53:34z SPIFFS mounted.
8/29/24 15:53:34 Local time zone: -5:00, using DST/BST when in effect.
8/29/24 15:53:34 device name: IotaWatt
8/29/24 15:53:37 Connecting with WiFiManager.
8/29/24 15:53:43 HTTP server started
8/29/24 15:53:43 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.1.157, channel=2, RSSI -72db
8/29/24 15:53:43 timeSync: service started.
8/29/24 15:53:44 statService: started.
8/29/24 15:53:44 Updater: service started. Auto-update class is MINOR
8/29/24 15:53:45 Updater: Auto-update is current for class MINOR.
8/29/24 15:53:45 dataLog: service started.
8/29/24 15:53:48 dataLog: Last log entry 08/29/24 15:53:15
8/29/24 15:53:49 historyLog: service started.
8/29/24 15:53:49 historyLog: Last log entry 08/29/24 15:53:00

5

Power cycling will reset everything but the SSID and Password. If you power cycle and it comes back up with a green LED, it is connected. If you have more than one SSID, you would need to have your browser connected to the same SSID to access the IoTaWatt. Have you tried power cycling your router and APs? Not that I think that is a workable solution, but may flesh out more information leading to what exactly is amiss.

6

Yes, power cycled everything.

Here you can see it shifting from the reserved 192.168.1.157 IP on the main router (normally a weaker signal) to the 192.168.4.90 IP assigned by the eero network on 8/26.
8/26/24 14:40:04 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.1.157, channel=4, RSSI -62db
8/26/24 16:48:44 WiFi disconnected.
8/26/24 16:48:49 WiFi connected. SSID=HappyHoundBrewing, IP=192.168.4.90, channel=6, RSSI -69db

However, it wasn’t until today that I added the extender close by the unit, so it seems both APs were fighting for it for the last several days.

I’ll keep playing around with network settings but I think the solution is to have it and the espressif’s blocked on main router and let the stronger mesh network devices pick it up. We’ll see…

7

Looks like we are crossing in the mail. Took a look at your message log:

The different APs and IPs are clearly the issue. WiFi topology and configuration can be a very complicated subject. You may have two different DHCP services running - one on the router and one in the mesh. That would explain the different IP assignments. There could also be an issue with the zeroconfig protocol (.local) that is being used to find the IoTaWatt - MDNS (Apple bonjour) or LLMNR (Microsoft). Both rely on being able to broadcast discovery messages regardless of where the unit is connected. Many routers have settings to inhibit that broadcast as a security measure. It’s usually a setting on the router(s).

1 Like