I am perplexed here. I just received my C8 Pro today and I’ve been having problems from the get go. At first, I plugged it in and when the lights were flashing green/red I went to my iPhone WiFi and connected to the “MyNewHubitat” SSID, entered the home WiFi network information, download the latest firmware, and finish the set up. I added me as a user for security purposes (planning on the fam to have user accounts) and everything was fine for an hour. I decided to input a static IP (used the DHCP assigned IP for simplicity purposes) and I entered the information to do so, including gateway and DNS information. It rebooted and then I couldn’t connect to the device. I tried going in on port 8081 to diagnose it; no avail. Still could not be reached. So I did a network reset again figuring maybe I mistyped something. Well now when the green light is solid and I connect to “MyNewHubitat”, I just get a blank white screen on the Captive Wi-fi portal. It connects, but just get a white popup where the wi-fi info form used to be. I have tried resetting it several times to no avail. Same thing. I checked my gateway and it does not show the device on it (searched by MAC) , so I know for a fact it is not connected to my network and a reset on the hub was done. I’ve tried connecting on my iPad, nothing. I tried it on my laptop and it too connects, but nothing pops up. I’m at a loss here. The find device page finds it by MAC address even when it is not connected to my network (site stores last IP info?). Very frustrating. So somehow I bricked it. Any suggestions?
Can you check on your router and see what IP address it thinks it has been assigned? Also try connecting it via ethernet to trouble shoot as that may also be helpful.
Setting a DHCP Reservation (for the Hubitat hub) on your router is preferable to messing around with Static IP settings within the hub.
Unless you really know what you're doing (and I do not!), Static IPs tend to be pretty troublesome. But a router-based DHCP Reservation is easy and works great.
You're talking about the almost invisible button on the bottom of the hub right? Behind the round hole? -- the only thing that button does is reset WiFi,
The MAC address on the bottom of the Hub is related to the ethernet connection, not the WiFi, which has it's own MAC.
Yep. The invisible sneeze-and-you’ll-miss-it, on the bottom button.
You know, I haven’t tried wired yet. Should have eliminated that right off. Just didn’t think of it because my use would have to be WiFi (no ethernet even close to the center of the house and most of my wireless devices like matter, Zigbee, zwave, and Lutron are all over the house from one end to the other.
I’ll move it to an available port and see what happens wired and keep y’all updated.
BTW, anyway of getting that WiFi MAC without getting into the device? I have a disconnected device named “linux” which could be it. But it is not the only previous Linux device that is/was connected to the same AP. I know when I was connected and working on my network at initial setup, and findmyhub found it by the printed MAC address rather quickly while on WiFi.
I don't know of a way, but I haven't used WiFi for a Hubitat hub in years. I put a spare C-8 on WiFi this morning and found the MAC... it starts with: 50:20:65..... Which is likely to be what yours starts with too.
In an effort to find a solution to your problem, I disconnected the Ethernet cable (my normal connection method) and pressed the button, to reset network settings.
After a few moments the "MyNewHubitat" SSID appeared and I connected to it.
The light remained blue, while I was connected, and about 30 seconds later the light turned green. When opening my browser, it automatically directed me to the captive portal, which was an entirely white screen.
So I experienced exactly the same symptoms as you, on a hub that had been working perfectly a few minutes earlier.
I plugged in the Ethernet cable, and immediately regained access on the original IP.
By the way, as long as the "MyNewHubitat" SSID is visible, it is pointless looking for it on your router, or trying to configure DHCP reservations.
I'm sure an Ethernet connection will get you access where you can configure your WI-FI credentials. It would still be nice to figure out what is going on.
I did just that. Was able to access it via ethernet. I redid the WiFi credentials and was able to reconnect wirelessly (hub shows it’s connected to my SSID). Something’s up to just throw a blank white page when you reset the WiFi. It makes it to where you may be able to set it up by WiFi once, but afterwards you’ll need to fix WiFi issues by wire. At least it was duplicable.
For reference, at least on my Dream Machine, the name shows up as “Hubitat Elevation” when connected to ethernet and just “Linux” on WiFi.
That said still having issues on WiFi. The assigned IP on the wired was xxx.xxx.xxx.216. The assigned IP on the WiFi is xxx.xxx.xxx.174. When plug into the ethernet, I can access the hub pages on 216 and 174 from my laptop. The laptop is connected to the same SSID as the hub. But when I unplug the ethernet, I can’t connect on 174 nor 216. Takes too long to respond and errors out. The WiFi (174) and wired (216) show active on the gateway when ethernet is plugged in and only the WiFi (174) when ethernet is unplugged, as expected. So it seems to be an issue on WiFi only. It is set to using the DHCP (it said static only effects wired connections only anyways). When plugged in, FindMyHub finds “two” hubs: the 216 and 174. But when unplugged, it discovers nothing. Odd.
I take that back. It is discoverable on just WiFi (174) in FindMyHub, but it still doesn’t connect to the hub.
The static IP config is for Ethernet only, not Wifi, so thats why it could not connect via Wifi after setting that up.
I would do a network reset again. Once back in do not change to static IP or mess with any of those settings. Just get the Wifi working and connected and then shut down the ethernet as suggested in the UI. Reboot the hub and unplug the ethernet cable. It should reboot and connect to the Wifi.
If you want a fixed IP for the Wifi you need to set it as a DHCP reservation on the router.
Reverted to DHCP in previous post, no avail and I’ve done several network resets.
Think I found the problem. From this point forward I have not retried setup through WiFi, just ethernet. For giggles I did a soft reset to see if that worked. It did not. Did the same as above (unplug ethernet cable) with same results. So I decided to revert the firmware to its stock v2.3.7.146. I bypassed the auto update and shut down and unplugged the ethernet. Was able to connect by WiFi. Rebooting it, shutting it down, and even just unplugging it it kept the WiFi.
I then searched for updates and downloaded v2.4.0.136 (the version I was having problems with). And lo and behold, still had WiFi. I didn’t plug in the ethernet slightly before nor after the update. So I tested it plugged in, unplugged, rebooted, shutdown, and killing the power. Kept the WiFi (so far). I’m leaning towards a corrupted firmware when it auto updated at setup. Since this is doesn’t have any devices connected, I’m going to reset the network again and see if I can get back to the captive Wi-Fi portal.
I’ll do it in a bit because I have to get my daughters to school, so I’ll post and update in a few. But leaning towards corruption of v2.4.0.136 when updated.
Daughters still getting ready so I decided to try.
Nope. Captive Wi-Fi portal still producing a blank white screen. So while I solved my WiFi problem with y’all’s help, my initial problem still persists. I’m gonna revert to the stock again and see if I can access it. Possibly be a firmware issue in v2.4.0.146, but can’t confirm until I revert back to stock.
Ok can confirm it is v2.4.0.146. Reverted to v2.3.7.146 and got the portal, updated back to v2.4.0.146 and no portal. So for now, on that version, you cannot setup WiFi without using ethernet, or you can just skip v2.4.0.146 and keep running the old v2.3.7.146 firmware until it’s fixed.
@gopher.ny I think this one belongs to you. Sounds like @sdwhwk already did some pretty extensive testing to verify the issue is on the current platform, and it works fine on an older platform.
