My cloud APIs have all stopped working recently on my hub. When testing from my.hubitat.com I found out that remote admin does not work either to that hub. It still works fine for my OTHER hubs, just not this one any more.
I tried restarting the hub but that did not seem to help. It appears that something broke with the cloud link somehow after the latest firmware update.
How can I fix this?
If both your cloud API's, and remote dashboard access has failed, then It appears that your hub has lost connection with my.hubitat.com.
Test #1 Is your hub still communicating locally?
--I know that you restarted the hub, but you didn't specify how.
--Can you connect to your hub over the local network (i.e. 192.168.x.y)
Test #2 Can your hub communicate over the cloud (WAN)?
--Login to my.hubitat.com
--Click on registered hubs, and select the problem hub
--Click on details and make a note of the Last Check in Time
--Open the network testing tools on the hub (under Settings, Network Setup)
--Attempt to ping my.hubitat.com
Let us know the results of these tests.
--- d1tvawzvbxb9go.cloudfront.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 4.246/4.489/4.896/0.289 ms
I'm not sure what you mean. When you originally said your cloud API's were not working, I interpreted that to mean Cloud Endpoints. Perhaps that was a mistake on my part.
In your reply you said that your endpoints still work for the API's.
Do you mean Cloud Endpoints don't work, and Local Endpoints do work normally? Or do you mean the Cloud Endpoints do work when you are on your local network.?
What are you trying to control with these endpoints? Are you triggering rules with them? Are you requesting hub status info?
How are you issuing the call to the endpoint (E.g via Tasker). If you paste the endpoint into a browser, what response do you receive?
And one other question, can you access your dashboard remotely?
@MMK Press the network reset button on the bottom of the hub for 7 seconds with a paperclip or toothpick. (It's the only round hole out of all the square ones)
After that double check for the latest public platform (.197) Then check my.hubitat.com and see if it's connected.
Let me clarify that first part. My cloud end points are what sopped working, so you got that part right. When I said the endpoints still work fine for the APIs, I meant the local endpoints that start with 192.186.x.x. The cloud endpoints don't work at all, regardless of whether I'm on my LAN or not.
Yes, I'm trying to run rules in response to the endpoint trigger (I had about a dozen of them and they were all working perfectly fine until recently).
When I paste my endpoint in a browser it takes a while then shows: "No response from hub."
And no, the dashboard doesn't work remotely either. It's like any routing from cloud to my hub is broken.
I did the reset, and it restarted the device. My platform is 2.3.9.180 and checking for updates isn't bringing anything later.
my.hubitat.com shows my device just checked in after the reset, but I still can't connect to it.
in settings>>network setup is it speed set for AUTO?
Go through the diagnostic port (8081) and download the latest update from there. .180 did have cloud issues that were resolved in later versions.
Like you said, this latest information makes it look like a communication problem, rather than a problem with Endpoints
That also indicates a problem with Hub to Server communications. However your ping tests, and "Last Checkin" time indicate that hub-server communications are working.
I asked earlier what app/device you are using to make the Endpoint requests, in order to eliminate the device or app as being the problem. For example Tasker on an Android Phone, or the Hubitat Mobile App itself.
I suppose the easiest way to eliminate these items, would be to try and open the dashboard from my.hubitat.com as shown in the attachment. Assuming you have a Dashboard configured.
I don't have the cloud dashboard option. Looks like my dashboards are local only. As to how I make the calls, I use Apple shortcuts as well as directly opening links in browser for testing.
No. It's set to Fixed 100.
I'll give the update from the diagnostics port a try.
This seems to have done it! Updating to the platform worked. Thanks heaps, guys 
Set to auto
I'm glad you resolved your problem, and kudos to @rlithgow1 for making the winning suggestion. After the pinging tests were successful, and the checkin times were updating, I had ruled out a network problem. I suppose that if your network was only capable of 10 mbps, and you were trying to operate at 100 mbps, then smaller packets, like when pinging, would be successful, but not be successful at other times.
I wasn't aware that remote dashboards could be disabled. After reading your reply, it took me a fair amount of time to locate that option. So I ended up learning a couple of things from this discussion.
Download the Hubitat app
