"Cloud connection is unavailable" - Date:04.08.26

As of the past few hours? I have noted that
Hardware VersionC-8 Pro
Platform Version2.4.4.156
no longer has a Cloud Connection.

I only use a cloud connection for backups.

I have been updating home network infrastructure but I have been doing so for the past week and today is the first time I have noted a disconnect.

I have performed a sequential reboot of all networking devices to no avail. I have full access to the Hubitat and it performs locally as expected. The Hubitat has a fixed IP address assigned to it.

My initial question.
Is there a log accessible on the Hubitat that I might review to ascertain when this challenge first began. Given the problem I have no access to cloud backup history and was unable to find info locally or perhaps staring right through where data might be stored in this regard.

thank you

Ah the joys of making changes to networks :slight_smile: I am not aware of network log anywhere on the hub. Have you tried doing a network reset on hubitat hub, press in the button on the bottom of the hub for 7 seconds or so until it reboots? Other thought would be to remove the static IP assigned on the router for the hub, assuming you did not set it on the hub itself (in Network Settings/Switch to static IP), and then reset the hub, see if it gets a new IP and cloud connection.

If you are having a hard time finding the reset button, there is a link to a picture that shows the reset button in Network Settings/Switch to static IP.

Thanks for your input.
For the time being I am not going to make any changes to the Hubitat. It has a fixed IP set on the Hub itself. It has been this way since it was first installed some months/years ago. Further its IP address is 'positively reinforced' on the router. When I first noted the challenge/disconnect; I rebooted the Hub to no avail. In recent weeks I have upgraded my cable modem and router in baby steps watching and waiting for anomalies to rear their ugly head/s. Today is the first time I noted this issue. Given the changes that the network is undergoing and the possibility of my not catching all the nuances that may have resulted - my quest for a log independent from my old memory. The challenge I created may have existed yesterday but I ony noted it today after having to shut down everything to install/swap devices used for UPS. Fortunate to be unemployed/retired :slight_smile: to give it my time.

You have given me food for thought as to how the cloud connection is acquired.
Thank You.

1 Like

Just my 2 cents but I would set the static IP on the router only not on the hub and definately not both. I have found that trying to set static IPs on devices can cause some odd things to happen on the router, conflicts, NAT entry issues.....

The rest button on the bottom of the router will reset the network settings on the hub. Not the same a rebooting. This would be the way to erase the static IP settings on the hub.

2 Likes

You put 2 cents into a savings account and it grows interest.
Thank You

1 Like

Right and being retired as well, I will take any cents I can get (getting older I will take any sense too).

I second this suggestion.

3 Likes

I have removed the address reservation for the Hub from the router. I have rebooted both the Hub and Router in different sequences to no avail
I have recorded MAC addressed and Hub ID.
My next step from your respective words of advice is to go ahead and reset the Hubitat via paperclip.

What might I expect after doing so?
Will the router recognize the fixed IP address of the Hub or will the Hub loose its fixed address and revert to DHCP?

I can/will of course bite the bullet and press the button but >>>>>>. :slight_smile:

Pushing the button on the bottom of the hub will reset the hub’s network settings to use DHCP and then the hub will reboot. It doesn’t reset anything else.

Maintaining a DHCP reservation for the hub in your router’s settings shouldn’t cause any issues.

4 Likes

Thank You to CaptWoody and marktheknife for your responses/suggestions.

I applied them to no avail.

I should have dug deeper before posting as it ended up to be an error on my part and/or the way things are these days.

With the introduction of a new router. I also introduced the use of a VPN for outbound traffic. Though using a VPN for outbound traffic had been introduced several days ago with seemingly no consequence. Today it made a difference and was the reason for Hub being unable to connect to the Cloud.

Those of you who understand/apprecaiete the phrase "I remember when" understand of which I type.

2 Likes