I noticed once recently that my hub had randomly disconnected from the cloud. I rebooted, it reconnected.
Obviously it’s unsatisfying, and if it’s happening frequently to someone, frustrating.
But they’re trying to identify and resolve what they can.
Just copying my message from the other thread here as some additional context to the original error message you mentioned and also the clarification around inbound communication via the hub's cloud relay connection (which it looks like this thread already acknowledges pretty well).
Sounds like you are on the right track engaging with the Hubitat community and working to engage with Hubitat support. If you haven't already, you might also consider sending an e-mail to Hubitat support -- I'm not sure which methods of communication they prefer, but sometimes it's helpful to do it through the official support channels so it's easier for them to track and reply to.
Lovely to hear (now from a number of sources) thd support team are apparentky aware of the issue and it's a "top priority'.
That gives me even less motivation to attempt to engage. Please don't anyone suggest I try to reach out to them via emails etc. For" private reasons" the team cba to respond in a thread.
.for reference, 5 days ago:
Since potential fixes are likely to be in beta firmware builds, you could consider requesting to join the beta group and evaluate whether things improve as you apply updates.
Sorry, yes I did reboot the hub as well. Thanks.
As Mark said:
And just because you're in the beta group you don't have to take beta updates, and you can roll back from them if you do try one out and don't like it.
I will stay away from selecting the beta approach for now. Too much going on in my house to risk messing up something else.
It’s bad enough that my sharptools touchscreens are down. Luckily I am away right now so not walking past the screens with question marks on them!
If someone sees an improvement in beta could they post here? At least we would know the fix is coming and could even mess with the beta.
I appreciate I could potentially acquire more information if I were to join the beta group. Not something I'd like to consider. Sorry.
The issue here is the public thundering silence from the (usually-active) support team regarding this serious, widespread issue.
As I said earlier - this is the first time I've ever had a problem with the way a topic had been handled (or rather publically ignored). It's bordering on insulting. There are multiple users adding their own experiences and saying the same whilst the only hint of recognition of the problem is covert references to private conversations from (two?) users I suspect have comms with the powers-that-be. Not good enough.
Not the actions I'd come to expect at all. Reminds me of the smartthings days. Extremely, extremely disappointing and has caused a personal loss in confidence. Right now, I'd be hesitant to upgrade when the time comes. I never thought I'd feel that way, having been repeatedly impressed by the public input from the team in the past.
.
.
Anyway, nothing else I can do or say and unfortunately I just need to sit and wait, hoping that some future change log quietly hints towards a fix.
Yes, we did already in another thread:
Thank you for your patience and understanding. A fix is currently in internal testing and will be soon released in beta, first.
Thanks for the update. Appreciated.
Thanks for confirming the team is working on this. Is there a known stable firmware version that can be reverted to in the meantime to avoid the cloud disconnects?
Hopefully the next one. The last few updates have had reasonable attempts to fix edge cases and it seems like while fixing one, made it worse for others. Network fine-tuning is always a challenging task for engineers because there are so many variables. It would be nice if everyone would use one router with identical settings. Only then, everyone would have a consistent experience.
Update installed - no loss of cloud. Yay.
Ta.
I just installed the update and it still doesn't work. It is still returning a 504 Gateway Timeout when I try to authorize my Sharptools.
Since you said above that a reboot did not fix the issue then there is something else going on with your situation. One easy way to test cloud access is to open a dashboard cloud URL and see if it works. If a cloud dashboard works then your hub is connected to the HE cloud system.
You may want to try rebooting all your network hardware also, that has been known to fix mysterious issues before.
Yep, I rebooted the hubitat, and powered down my router and switches. Accessing a cloud dashboard does work. But everytime I try to authenticate from Sharptools I get the following response from:
504 Gateway Time-out
Have you posted in the sharp tools forums?>
The 504 Gateway Timeout is coming from the Hubitat OAuth servers.
I would still post there to see what they have to say..
I'm the founder of SharpTools. 
It sounds like it could be slightly different than the broader issue that was impacting DNS caching, etc and was causing the connection to the Hubitat Cloud Relay to fail for many people since Simon can use a Hubitat Dashboard Cloud URL now. It sounds like it might be limited to something with the Hubitat OAuth Servers. @simon4 have you tried reaching out to Hubitat support so they can take a closer look? Perhaps their internal diagnostics and logging would reveal something about your hub / connection.
Copying my comment from another thread that's relevant:
Download the Hubitat app
