Can't access iotawatt with new router

I updated my router & can’t access the iotawatt now. I got it connected to the new network (2.4Ghz), my router is showing that it is connected. I tried iotawatt.local and the ip address assigned to it. I also assigned a fixed ip, but that doesn’t work either.
My computer is on the same network.
It’s using WPA2/WPA3-Personal authentication. wifi-7 mode is disabled.

If I ping it, it says Destination Host Unreachable.

The led is green, kind of pulsing, but I think that’s the way it was when it worked on the old router.

Any ideas?

Same issue here from this morning, I recently changed from a Asus RT-AC68U to a Asus RT-BE86U and I had a lot of issues setting up this router. Originally I had the iotawatt in the metal power box which the new BE router didn’t like so I’ve moved it adjacent the metal box and into a plastic box so now it has a nice stable -60db connection which was fine up until this morning. I can no longer connect to iotawatt.local or the 192.168.50.49 address like I used to but it is showing in the router client list as connected with a nice strong signal.

This is a WiFi issue and there is very information to take a guess at what it might rbe beyond something to do with the new router settings. Same for @Damon problem.

Random thoughts:

When IoTaWatt has green LED, it is connected to WiFi. The type of authentication would be relevant if it didn’t connect (red led), but you are beyond that.

There are a lot of variations in router functionality and features. More sophisticated setups allow inhibiting the zeroconfig mechanisms (.local) but you say that you cannot reach it with an assigned IP.

The IoTaWatt doesn’t work well with changing channels or changing IP address. I would suggest powering off the IoTaWatt, restart the router and then restart the IoTaWatt.

May seem like stupid questions but I have to ask: Is the old router still running? Are you using the same SSID with the new router? Does your router support, and are you using, multiple VLANS?

@Damon, nothing has changed from the IoTaWatt end. No new firmware. My units are all still responding to .local access and I tried another remote unit that I monitor and it is up and running fine. So probably a WiFi thing. Did your router switch channels?

The old router is not still running.

New SSID with the new router.

In addition to my main network, I have 2 vlans, but the iotawatt is on the main network.

I did the restart procedure you suggested, but no change.

I see a lot of this sequence in the router logs. This is the MAC of the iotawatt. Is the signal too weak? Sometimes minutes apart, sometimes seconds apart.

Jun 8 09:22:22 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind DC:4F:22:5D:D0:71, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jun 8 09:22:22 wlceventd: wlceventd_proc_event(662): wl0.1: Disassoc DC:4F:22:5D:D0:71, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jun 8 09:22:22 wlceventd: wlceventd_proc_event(685): wl0.1: Auth DC:4F:22:5D:D0:71, status: Successful (0), rssi:0
Jun 8 09:22:22 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc DC:4F:22:5D:D0:71, status: Successful (0), rssi:-71

I could get the old router back online, is it possible there might be something helpful in the log? I’m thinking about setting that up as an access point if I can’t get this working with the new router.

I got mine online. There is a setting in the router: Advanced-Wireless-Professional-Roaming assistant-Disconnect clients with RSSI lower than :xx dBm

It was set to -70, I changed it to -80 & it seems to be working now.

1 Like

Yep this worked. @papab what router are you using? I’ve been a long time fan of Asus but their BE series routers have serious issues, very unstable.

I have the RT-BE82U

As I said on 6/10, I got it working, but last week or so, I noticed I had no wifi connection again. I power cycled iotawatt, but that didn’t seem to fix it. I didn’t try a router reboot. I checked today & it is up and running normally.

I noticed a couple things in the iotawatt log.

It takes over 4 minutes after reboot to connect to wifi. Is that normal?

It looks like after that power cycle it failed to connect wifi, so restarted, then connected. Then there were 2 restarts due to degraded Heap Memory. Total time with the restarts was 23 minutes, so It’s very possible that when I power cycled that I didn’t wait long enuf to see data.

Any thoughts?

** Restart **

SD initialized.
7/18/26 02:10:12z Real Time Clock is running. Unix time 1784340612
7/18/26 02:10:12z Reset Reason: Power-fail restart.
7/18/26 02:10:12z ESP8266 ID: 6148209, RTC PCF8523 (68)
7/18/26 02:10:12z IoTaWatt 5.0, Firmware version 02_08_03
7/18/26 02:10:12z SPIFFS mounted.
7/17/26 20:10:12 Local time zone: -7:00, using DST/BST when in effect.
7/17/26 20:10:12 device name: IotaWatt
7/17/26 20:10:15 Connecting with WiFiManager.
7/17/26 20:13:15 Did not connect after power-fail. Restarting to reset WiFi.

** Restart **

SD initialized.
7/18/26 02:13:17z Real Time Clock is running. Unix time 1784340797
7/18/26 02:13:17z Reset reason: Software/System restart
7/18/26 02:13:17z Trace: 34:10[2], 34:5, 34:5, 34:5, 34:6[1], 34:10[3], 34:5, 34:5, 34:5, 34:6[1], 34:10[9], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[12], 3:100, 3:101, 3:102, 31:105, 31:105, 31:106, 11:40, 11:45, 11:50, 11:55, 11:70
7/18/26 02:13:17z ESP8266 ID: 6148209, RTC PCF8523 (68)
7/18/26 02:13:17z IoTaWatt 5.0, Firmware version 02_08_03
7/18/26 02:13:17z SPIFFS mounted.
7/17/26 20:13:18 Local time zone: -7:00, using DST/BST when in effect.
7/17/26 20:13:18 device name: IotaWatt
7/17/26 20:13:18 HTTP server started
7/17/26 20:13:18 emoncms: Starting, interval:60, url:http://emoncms.org
7/17/26 20:13:18 timeSync: service started.
7/17/26 20:13:18 statService: started.
7/17/26 20:13:19 dataLog: service started.
7/17/26 20:13:20 dataLog: Last log entry 07/17/26 20:09:40
7/17/26 20:13:23 historyLog: service started.
7/17/26 20:13:23 historyLog: Last log entry 07/17/26 20:09:00
7/17/26 20:17:31 WiFi connected. SSID=Cottonwood, IP=169.254.114.208, channel=10, RSSI -73db
7/17/26 20:17:31 Updater: service started. Auto-update class is MAJOR
7/17/26 20:22:51 Heap memory has degraded below safe minimum, restarting.

** Restart **

SD initialized.
7/18/26 02:22:52z Real Time Clock is running. Unix time 1784341372
7/18/26 02:22:52z Reset reason: Software/System restart
7/18/26 02:22:52z Trace: 1:3, 1:6[1], 1:6[2], 1:6[2], 1:6[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[5], 31:120, 21:100[31], 21:101, 31:120, 31:122, 31:123, 31:123, 21:110, 21:110, 31:1, 1:6[6], 1:3, 1:3, 1:6[1], 1:6[2], 1:6[3], 1:5[21], 1:6[4], 21:0, 21:1, 21:10, 21:10
7/18/26 02:22:52z ESP8266 ID: 6148209, RTC PCF8523 (68)
7/18/26 02:22:52z IoTaWatt 5.0, Firmware version 02_08_03
7/18/26 02:22:52z SPIFFS mounted.
7/17/26 20:22:53 Local time zone: -7:00, using DST/BST when in effect.
7/17/26 20:22:53 device name: IotaWatt
7/17/26 20:22:53 HTTP server started
7/17/26 20:22:53 emoncms: Starting, interval:60, url:http://emoncms.org
7/17/26 20:22:53 timeSync: service started.
7/17/26 20:22:53 statService: started.
7/17/26 20:22:54 dataLog: service started.
7/17/26 20:22:55 dataLog: Last log entry 07/17/26 20:22:50
7/17/26 20:22:58 historyLog: service started.
7/17/26 20:22:58 historyLog: Last log entry 07/17/26 20:22:00
7/17/26 20:27:06 WiFi connected. SSID=Cottonwood, IP=169.254.114.208, channel=10, RSSI -72db
7/17/26 20:27:06 Updater: service started. Auto-update class is MAJOR
7/17/26 20:32:31 Heap memory has degraded below safe minimum, restarting.

** Restart **

SD initialized.
7/18/26 02:32:33z Real Time Clock is running. Unix time 1784341953
7/18/26 02:32:33z Reset reason: Software/System restart
7/18/26 02:32:33z Trace: 1:3, 1:6[1], 1:6[2], 1:6[2], 1:6[3], 1:5[31], 1:6[4], 31:0, 31:1, 31:2[5], 31:120, 21:100[31], 21:101, 31:120, 31:122, 31:123, 31:123, 21:110, 21:110, 31:1, 1:6[6], 1:3, 1:3, 1:6[1], 1:6[2], 1:6[3], 1:5[21], 1:6[4], 21:0, 21:1, 21:10, 21:10
7/18/26 02:32:33z ESP8266 ID: 6148209, RTC PCF8523 (68)
7/18/26 02:32:33z IoTaWatt 5.0, Firmware version 02_08_03
7/18/26 02:32:33z SPIFFS mounted.
7/17/26 20:32:34 Local time zone: -7:00, using DST/BST when in effect.
7/17/26 20:32:34 device name: IotaWatt
7/17/26 20:32:34 HTTP server started
7/17/26 20:32:34 emoncms: Starting, interval:60, url:http://emoncms.org
7/17/26 20:32:34 timeSync: service started.
7/17/26 20:32:34 statService: started.
7/17/26 20:32:35 dataLog: service started.
7/17/26 20:32:36 dataLog: Last log entry 07/17/26 20:32:30
7/17/26 20:32:39 historyLog: service started.
7/17/26 20:32:39 historyLog: Last log entry 07/17/26 20:32:00
7/17/26 20:33:09 WiFi connected. SSID=Cottonwood, IP=192.168.50.10, channel=10, RSSI -71db
7/17/26 20:33:09 Updater: service started. Auto-update class is MAJOR
7/17/26 20:33:10 emoncms: Start posting at 06/10/26 15:06:00
7/17/26 20:33:11 emoncms: stopped, Last post 06/10/26 15:05:00
7/17/26 20:33:12 Updater: Auto-update is current for class MAJOR.
7/19/26 16:37:49 Updater: Invalid response from server. HTTPcode: -4
7/23/26 23:01:03 timeSync: No time update in last 24 hours.