The Network Setup settings page, accessible from Settings, allows you to:
This page is available on hub models C-5 and later only. Earlier models use DHCP and do not offer further customization.
To override the hub's default DNS settings, expand the Override DNS Settings section and enter one or more DNS server IP addresses under DNS name servers override, comma separated. To use multiple DNS servers, separate the IP addresses with a comma.
184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
To configure a static IP address, expand the Switch to static IP section, then:
NOTE: We suggest using a DHCP reservation on your router instead of this option, as it does not require any special configuration on the hub, leaves little room for error, and gives a similar result. Having a non-changing IP address — however it is done — can be helpful, though neither is required.
If assigning a static IP, ensure it is outside the DHCP range for your router and that you know what other settings are appropriate for your network. Incorrect settings can cause your hub to be unable to connect to the Internet or an inability for you to connect to your hub on your own network. A network reset may help you re-gain access if needed (see below).
Select Save and switch to static IP.
You must reboot the hub for the changes to take effect.
NOTE: Static IP/DHCP configuration applies to the built-in Ethernet port only. Wi-Fi will always use DHCP.
If you are accidentally blocked from accessing your hub due to an incorrect or unknown IP address setting, turn the hub over and use the point of a pen to press the small button just beneath the surface of the hub casing for at least 7 seconds.
The LED on the front of the hub will blink, then the hub will reboot (at which point the LED will turn blue as part of the normal boot process before again turning green once the hub has fully booted).
To change back to DHCP (and let the router assign an IP address to your hub via its MAC address), expand the Switch to DHCP section, select the Switch to DHCP now button, and reboot the hub the hub from Settings.
Hubitat model C-8 includes built-in Wi-Fi. Models C-5 and C-7 can also connect via Wi-Fi by adding a compatible adapter.
Expand the Wi-Fi Drivers section, then select the Install Wi-Fi drivers button. Ensure the installation succeeded (you will see a note on the page) before continuing.
Shut down the hub.
Connect a USB OTG + power cable (not included) to your hub. This type of adapter cable feeds power to the hub while simultaneously providing a USB data connection for USB devices. An example:
Plug a compatible Wi-Fi adapter into the USB port on the OTG adapter cable. A list of known compatible adapters is provided on the Network Settings page. The TP-Link Archer T2U Plus is likely to have the best range among the supported options and is recommended if the size of the adapter is not a concern.
Plug in the micro-USB power cable to the port on the OTG cable. The hub will begin booting.
NOTE: For maximum reliability, connect Hubitat Elevation to your network with an Ethernet cable rather than Wi-Fi if possible.
If you have configured Wi-Fi and want to restore hub connection via Ethernet:
Some advanced network settings are currently not available via the UI but can be changed via HTTP endpoints if needed.
Modifying these settings is not recommended for most users. Use caution, and only modify settings that you understand and know are necessary on your network.
Select the Network Test link at the top of the Network Setup page to open a page offering four utilities you can use to test your hub's network connectivity:
For example, if you are unable to use Settings > Check for Updates or uploading a cloud backup fails, you may have problems reaching the Hubitat servers due to incorrect network configuration. To test:
cloud.hubitat.com, select the Ping button, and wait a few seconds to verify the server is reachable. Example of acceptable output:
If ping fails, a common cause is misconfigured DNS servers. Two possible solutions are specifying valid DNS servers or reverting to DHCP rather than static configuration.