I have been using my C8, connected via ethernet, without problems. I decided I want to connect the Hub to my network via WiFi rather than ethernet. While connected via ethernet, I connected to my WiFi and the Hub Network page shows I am connected to both Ethernet and WiFi. I then disconnected the Ethernet. After rebooting, my router shows that the Hub is connected via WiFi, but when I enter the IP address, it just Times Out. If I plug the ethernet cable back in, it will let me log in just fine, using the IP address of the WiFi, and again show that I am connected to both ethernet and WiFi. What is the problem? Why can't I login in via WiFi if the ethernet cable is not connected?
Note: I saw someone else post this same exact problem, but nobody replied.
The hub's IP address on wifi will be different from the IP address on ethernet... When on wifi (ethernet cable disconnected), are you trying to access the hub from its wifi IP address or the ethernet IP address?
I am aware that both the MAC address and ip address are different for Ethernet and wifi. I can see both of these devices on my router. And when i am on the hub, it acknowledges both devices. But it won’t respond to the WiFi unless the Ethernet is connected.
The path to your C8 is through your Wi-Fi router. If you connected both Wireless and wired to the same router vlan you made a forwarding loop (broadcast storm) for which the router or the C8 fixed by disabling the higher cost wifi path. Unplugging the Ethernet didn't enable the Wi-Fi path. So with it plugged in so you can talk to it issue a reboot then unplug the Ethernet. See if it comes back on the WiFi for you.
OK, this getting weirder. Been trying to do some of the things recommended above. No luck.
But now, here is what is happening. After disconnecting WiFi on the Hub, at the top of the screen it shows that I am attached to Ethernet on one of my LAN IP addresses. Works great. I ask the Hub to connect to my WiFi. It says it successfully connected. At the top of that screen, it now says it is connected to Ethernet at the same local IP address, and it also says I am now connected via WiFi to 169.254.6.94 (or 172.16.1.1) which is not in my subnet. Last night when I was trying this, it was showing that I was connected via Ethernet to my subnet, and the WiFi was connected to an IP on my subnet. This strange behavior started when I finally followed the link on the screen that said not to just unplug the Ethernet cable. Now I can't get my Hub to connect via WiFi to my Router.
With Ethernet disconnected, I tried the URL you provided, and it DOES find my hub, and at the WiFi IP address I expect. But when I click on "connect to hub", it just times out. Tried adding ":8081", still times out.
When I hear someone use the term "subnet" rather than just "LAN", they usually have a more complicated network. Subnets usually imply that they are isolated from one another by routers/firewalls or VLAN's. Since you referred to both "subnets" and "LANS", can you describe your network setup.
Is you WAP built into the router, or is a separate device.
Do your 2.4 Ghz and 5.0 Ghz Wi-Fi networks have the same SSID. In other words can your hub always connect reliably to the 2.4G network.
Is it possible that you are connecting to a "Guest" Wi-Fi network.
For the sake of future discussion, what is your LAN network address, or subnet addresses.
The "non-subnet" addresses you listed above (at least the 169,x,x,x) are usually used by a NIC when it cannot obtain a DHCP address from the router.
Is your Ethernet connection configured for DHCP or did you give it a static IP in the hub. Is your router DHCP server enabled? Do you still have addresses available in the pool?.
So just tried having the Hub connect to my WiFi and it said it OK. But the IP address shown on the Hubs Network screen still shows Ethernet at 192.168.1.212, and WiFi at 169.254.6.94. I ignored it, shut down the Hub, pulled the power cable, disconnected the Ethernet cable, reinserted power cable into Hub. Router shows the WiFi MAC address of the Hub is connected as 192.169.1.37, and Ethernet MAC address is no longer connected. The Router shows a few packets (<100) going back/forth to the WiFi MAC. BUT, when I try to Ping 192.168.1.37, it says "Destination Host unreachable". ???
Simple straightforward network. All devices on 192.168.1.x
Router connected directly to WAN.
WiFi frequencies do not share SSID.
Router DHCP is enabled and working.
YES, I am trying to connect to my "guest" network, which is where all of my IOT devices are connected.
Did you hear that? The sound of me hitting myself on the head.
So it only now occurs to me that with all other IOT devices, I never actually try to connect to and interact with them. But with Hubitat, I want/need to interact with it on a regular basis.
So I now realize that the Hub really is connected to my LAN, and I just never waited long enough to verify it was working (Rules executing, etc.). I can connect to it directly by just logging into the same SSID (Guest network) via WiFi.
I tried to connect the Wi-Fi to my 192.168.200 subnet.
The first image is what I saw. Notice the address 169.254.10.222 which does not match my subnet.
Also notice the message "Do not just unplug Ethernet cable while hub is running. Please shut down Ethernet first. I clicked on that link, and became disconnected from the hub.
I connected to findmyhub,hubitat.com, to find the Wi-Fi address that the hub was using, and then connected to that with my browser.
The 2nd image shows that Wi-Fi is working properly.
