I recently purchased the Hubitat Elevation C8 Pro. Each night, the hub loses connection to the cloud. As a result, the app will lose connection and smart home integration with Google Home stops. I attempted several solutions including: Switched to static IP in hub; reserved IP with DHCP Reservation in Linksys router, settings in router to always stay connected to internet for Hub, Hub connected via ethernet, not wifi and other measures that have not worked.
Just to be sure, do you mean that devices on the hub cannot be controlled by either the phone app, or by Google Home, but you can connect using a web browser on the local network?
Does the phone app only fail when "Cloud" connected, or with "local" connections as well?
Does this occur at the same time every night?
What do you do to resolve the issue?
What color is the LED when the problem is occurring?
Have you used the "network test" tools to verify you have lost internet access?. i.e. have you tried to ping my.hubitat.com from the hub when the problem is occurring?
How sophisticated is your network? Do you have VLAN's or managed switches, etc.?
Does your router have parental controls that could be used to limit the access of certain devices to certain hours?
Just to be sure, do you mean that devices on the hub cannot be controlled by either the phone app, or by Google Home, but you can connect using a web browser on the local network? I can control devices using the web interface of the hubitat, but not the app unless I reboot Hubitat. It is only after I reboot Hubitat that I can control devices using the app or Google Home or Alexa
Does the phone app only fail when "Cloud" connected, or with "local" connections as well? The connection on the app to the local network occurs only if I reboot the Hubitat. Without the reboot, the app cannot find the hub either locally or through the cloud ip
Does this occur at the same time every night? Not sure. I pulled up the past logs from last night and it gave no clues or error messages.
What do you do to resolve the issue? Reboot the Hub
What color is the LED when the problem is occurring?Green
How sophisticated is your network? Do you have VLAN's or managed switches, etc.? Router is a Linksys Veloop mesh with one child node connected via a Netgear switch
Does your router have parental controls that could be used to limit the access of certain devices to certain hours? It does, but I have the parental controls turned off...Thanks for the help by the way!
Have you used the "network test" tools to verify you have lost internet access? No, not yet. i.e. have you tried to ping from the hub when the problem is occurring? **No, not yet **
That doesn't seem right. If you can access the Hub using a browser on the local network (from the same mobile device) , then the app should also be able to connect when it is on the local network.
Can you confirm that the app says local as shown in the screen capture?
Since the problem occurs "each" night,, please make a note of the actual time the problem begins to see if we can determine a pattern.
Also use the network tools to test that if you really have been blocked from the internet.
That doesn't seem right. If you can access the Hub using a browser on the local network (from the same mobile device) , then the app should also be able to connect when it is on the local network.
Can you confirm that the app says local as shown in the screen capture? No, it does not say, "Local". I can't even get to that page in the app. It spins and eventually goes to a "Select a hub" page which is not functional.
Since the problem occurs "each" night,, please make a note of the actual time the problem begins to see if we can determine a pattern.I'm asleep at night.
Also use the network tools to test that if you really have been blocked from the internet.
I am trying to upload screenshots here, but I receive an error message. Basically when running a ping test during the problem, it says Ping Host: PING 1.1.1.1 (1.1.1.1): 56 data bytes
ping: sendto: Network is unreachable. Ping Gateway: invalid IP address or server name
However, after a hub reboot, these ping messages go away and are replaced with success, the app then works and connects to the (Local) hub.
I will keep the live log open tonight and check it out in the morning.
After all these changes, your hub likely has conflicting configurations. For example it may be configured to use both ethernet and Wi-Fi , and both static and DHCP addressing.
I think that confirms a bad configuration.
I think it would be best to reset your hub's network settings to default. Press the hidden reset button for more than 7 seconds, and then release it. The hub should be connected to the router via ethernet.
After the hub reboots, it should be accessible at the DHCP address you previously reserved for it.
I have raised your community forum permissions to "member"; you should be able to post images now.
Thank you for the trouble-shooting. I also think this is a bad configuration - it is possible that hub is flipping between wired and wireless networks.
The hub is NOT connected to wifi, only Ethernet (always has been). I only switched to a static IP because of this issue. It was occurring BEFORE I made these configuration changes by choosing a static IP and default gateway. After doing the reset (pressing for 7 seconds), the hub rebooted, but still shows the same configuration on the Static IP fields (it did not wipe the fields clean...was it supposed to?). I will see again if the issue happens tonight. FYI, this morning, again, the hub had local web interface control, but no cloud connection, and the app was inoperable.
No, the hub is not nor has ever been connected via wifi, only wired Ethernet.
You clipped off the top of your screen capture.
Can you confirm if you are currently using Static or DHCP (see my example). Also you don't have to mask your local IP address. It would be useful to see that value to confirm you have assigned a proper address for your network.
If you confirm that you are using DHCP, and the "every night" problem just started with the new router, it may be because of the DHCP lease expiry timer.
EDIT: Just realized I am mixing your thread up with another one where the problem began with the installation of a new router. But still, a scheduled DHCP renewal, could be responsible for your seemingly "scheduled" problem.
You could try to extend the lease timer, or just set the hub to use a static IP.
I'll will defer to @Ricktronic and @aaiyar (who are much savvier on network ism's than I am), but I'm pretty sure that it's not necessary (and may even be troublesome) to have both a DHCP Reservation (set in router) and a Static IP (set in Hubitat) -- just do one or the other, and for that vast majority of folks, a DHCP Reservation is the way to go.
I've learned enough about networking from this forum to know that messing with Static IPs is going to (sooner or later) burn most average-joe folks (like me!)... I do not use Statics IPs at all anywhere on my oh-so-very-intentionally-flat network, but I do have DHCP Reservations set for just about everything (including Hubitat), and that approach has served me well for many years now.
Yes, my router is not new, but my Hubitat is. Yesterday I did a soft reset hoping it would clean out any infected code, etc. But the hub disconnected from the cloud overnight anyway. I'm only tech-savvy enough to be dangerous, so I appreciate your help. I am new to the Hubitat world, but my network, pre-Hubitat, has always been stable. I switched the hub setting to static IP several days ago, hoping it would solve the problem, but it did not solve it. Aside from this screenshot, I'll post a couple from my router for you to see if there is anything amiss.
When you used the network reset...can you confirm the description below happened on your hub when you did the network reset?
- Use the point of a pen (or other small, blunt object) to press and hold this button for at least 7 seconds.
- Release the button, and the LED on the front of the hub will blink. (If the LED does not blink, return to the previous step and try again, paying attention to the timing.) After a few more seconds, the LED will turn solid blue as the hub reboots. Finally, after a few minutes, the LED should return to green, at which point the hub has finished rebooting and should again be accessible.
Yes, from what I remember, that is what happened. The hub blinked (red), turned solid blue, and then green.
The problem is not accessibility. The problem is that it is losing connection with the cloud each night. Once I reboot, everything returns to normal.