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.
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?
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.