I'm using a C8 and on ethernet an am still seeing the Wifi Beaconing away (MyNewHubitat) and is interfering with an adjacent WiFi access point. Please indicate the procedure to completely turn it off (No Beaconing or presence).
Thanks..
Press and hold the network reset button on the bottom of the hub with a paper clip of a toothpick for 7 or more seconds. It will be the only round hole out of all the square ones.
Same issue here, and resetting network had no effect. I can connect to the WiFi and log in, even though I'm connected to ethernet with a static IP. Any other way to actually force it to disable WiFi? I just upgraded to the latest firmware (2.3.9.200) hoping that it would fix this issue, but no change.
If you mean that you can connect to your hub by using either the Ethernet IP, or by using the Wi-Fi assigned IP, then that is certainly possible. I'm new to Hubitat, so I don't know if that causes any problems, but I haven't noticed any yet. I suppose it may cause some problems with cloud access, but I haven't tested that theory.
If you don't want to have a Wi-Fi connection, simply disconnect the Wi-Fi. These images might help. Note that the first image shows that my Ethernet and Wi-Fi are actually on different subnets.
No, the WiFi doesn't have an IP, because it's not connected. It's only connected to ethernet, but I can connect to the MyNewHubitat SSID, hit 172.16.1.1, and log into the hub. I do not want that, because it's an extra network taking up airtime, and because it's an open SSID that's dual-homed to my non-open network. I want my hub to be wired-ethernet-only, and several posts say that once it's connected to ethernet it will turn its WiFi radio off, but that doesn't appear to be the case.
It's been several months since I originally setup my hub, so I don't recall the steps that I took.
Did you ever have your hub connected via Wi-Fi? Perhaps you are unable to turn off the Wi-Fi until it is a actually running.
All I can suggest is to configure the Wi-Fi to obtain an IP on your network. At that point your hub will be in a known state rather than the unusual state it is currently in.
Once that is accomplished, you should see the Disconnect Wi-Fi button become available. Press the button and see if only the Ethernet remains connected.
At the very least, as long as your Wi-Fi is connected to your LAN, you will have eliminated the open network until you find a better solution.
After a bit that should do to sleep.
Just closing the loop on this, it never shuts off. The only way to get it to shut off is to join it to WiFi, even though it's also connected to a wired network on the same VLAN.
Same issue, same "solution".
First reported it when I got my C-8 (when it was released) and still not fixed by Hubitat.
Huge security concern for you hub and rest of the home network, as anyone can just use it as a jump box!
HUGE security hole.
It broadcasts the standard HUBITAT SSID for all to see and allows connection with NO PASSWORD! And only at 2.4GHz so any 7th grader can see and operate/unlock your whole house! No 5GHz, no 6GHz. C'mon, Hubitat...
I connected by wifi and set the SSID to . and a gibberish password, saved, and it disappeared. Now looking at it over the LAN it shows nothing for WiFi settings and it's not broadcasting SSID. Hope this holds.
Maybe I'll remove the antenna away from the USB as good measure.
Otherwise a superb product.
What release were you on? They did make some fixed in recent versions to prevent that SSID from getting stuck on and always broadcasting.
It only broadcasts that SSID if the hub is not on ethernet, and not setup for Wifi. This is a pretty standard onboarding design for IoT devices. Now if it lets you into the main hub UI while connected to that onboarding SSID that could be a possible security risk if it does start broadcasting unintentionally, but your hub would have to be totally offline.
This can of course be easily avoided in any scenario if you setup the hub login security feature.
1 Like
I've been on 2.4.1.167 for several days.
Well it didn't work.
How could it let you in if it's totally offline.
Do a factory reset and try it. It nakedly broadcasts MyHomeHubitat to the whole neighborhood, with zero security, drunkenly passes out a 172.16.1.* to whoever associates with DNS and gateway 172,16.1.1, and everyone is free to connect and unlock yer door.
Just sayin'...
Take off that antenna away from the USB port.
To stifle Zigbee? (Wi-Fi is all internal.) It is not recommended to power the hub on without both antennas properly connected, in any case.
3 Likes
What didn't work? If you want to have the issues possibly resolved you need to provide more detailed information. A bulleted list of specific steps to reproduce would be the most helpful I think.
Because you have connected to the onboarding SSID, while the hub is otherwise offline. Which is supposed to be the only way the onboarding SSID is broadcast (when hub is offline or not yet setup).
If you factory reset the hub, how would you then unlock a door, all the devices would be removed?
That's not the Wifi antenna, Wifi is internal...
By the way, the bug this original thread is about I am fairly certain was resolved earlier this year. Must have been discussed in another topic, possibly in beta somewhere.
Thats why I asked what build you were on.
2 Likes
I think it was addressed in the release notes when v. 2.4.1 came out:
I agree that specific steps to reproduce would be much more helpful than hyperbole.
ETA: it was this thread that was acknowledged by staff in January.
5 Likes
