Thanks @josh . I am not sure that this latest update fixed anything for me as I didn’t test the cloud dashboards before. I don’t use the dashboards and had to set one up to test this.
I am not aware of any Hubitat support email or way to open a ticket? If anyone has any suggestions then please do let me know. I know that @bobbyD @Hubitat_Staff are monitoring this based on posts above. Thanks for any help in solving this.
go to support.hubitat.com and even if you don't have a warranty click warranty support and put in a ticket.
Thanks, I will try that.
@josh I don't use Google, IFTTT etc. But I did add the built-in app for IFTTT as a test and went to my long dormant IFTTT account and attempted to add the service and got the 504 Gateway Timeout. So this doubly confirms that the issues is not with one external service but presumably all external services that use this approach.
I've never installed Sharptools myself, but under APPS/DRIVERS code, is there an oauth button you can click and see if that helps?
Thanks - it looks like this option only exists for third party apps, not built-in apps?
Ahh, I forgot it's built in, my bad...
And I have entered a warranty support ticket and it confirmed that it had been received on the web site so hoping to get some more insights.
I did try pinging ping oauth.cloud.hubitat.com and got no response. I have no idea if that is relevant or not?
Looks like that server does not respond to ping, same here.
But if you browse to the site you should get a blank white page https://oauth.cloud.hubitat.com/
Looks like it is serving up the blank page, so if it works then you can reach the server at least. If it was not working you would get an error of some sort.
Not sure how to to test the OAuth unless you have another app that uses it.
Well, I am getting the error when I try to authorize with Sharptools and IFTTT. What I am not clear about - is this just me? Or are others having the same issue. Since the thread from last year started this discussion I don't see many of the folks posting at this point.
As I understand it the authorization process is not completed each time a device is updated? This is only done when first connecting to the hub? So if this is correct then your devices can run fine on the third-party side until you try to add new devices or do something that triggers the authorization event? If so, then folks may have the issue but not necessarily know about it?
Also, when I run an event through a cloud trigger that works fine. Not sure if that adds any new light?
Yes the OAuth is only done when you first setup an app like this. I think somewhere in dealing with the DNS issue you must have tried to re-auth sharp tools? If you had not done that it would possibly still be working fine.
The OAuth problem has not been an issue lately that I have seen. For a while it was happening regularly but whatever was going on with that server back then they must have gotten it under control.
Do you have any sort of DNS based ad blocking setup on your LAN that could be blocking HE from getting to specific sites?
Not that I am aware of. I checked the content filtering section of my Ubiquiti UDM Pro and it shows that it is off. Ad Blocking is also turned off.
If this was the issue then it would have to be something that was changed or enabled recently? I haven't made any changes to my router in a long time. The last firmware update appears to have been June 30. So I don't think that caused any issues as it was working until recently.
See my private message...
It appears that this issue is specific to your hub, as there are no issues with the oAuth server. Have you tried resetting the hub's network? Also, if you reply to my message along with your hub ID, I can check if the hub is connected to the cloud.
I have not tried this. I am away until tomorrow night and will try this then and report back. Good to know it is just my issue. Thanks.
Not quite true. I had these issues 10 days ago when I started this thread.
I hope this is now rectified, for now, it seems so.
No need, you should be able to link the hub now to cloud services. Based on your hub's logs, it was not connected earlier, but it is now.
Same symptom, but may not have been the exact same underlying cause(s) if the platform update resolved things for you but not for @simon4.
I’m sure that’s one reason why it can be difficult for Hubitat staff to troubleshoot issues that manifest as cloud connectivity problems.
Potentially.
But also, my problem wasn't a case of "every day at 1pm, I can't access my dash".
But it has been a semi-regular problem which manifested after (I think) each update.
Once I can happily run for say, 6 weeks without issue, I'd be confide t saying "thanks for the fix".
I'd still be incredibly interested to know just how many people are involved in the beta program, because I'm absolutely stunned at how widespread this latest problem appears to have been, and how hard this needed to be kicked before it received any public attention.
I'm happy this appears to be fine, but I remain deeply disappointed in the way the team have handled this. All it would have taken was a "yes, sorry about this, we are aware". Instead, nobody bothered to comment in public. Possibly because nobody wanted to publically acknowledge the issue. Which has caused me to lose a huge amount of confidence in the brand.
Unfortunately. And no offence intended, I've always taken a very, very positive view of the brand in general. This however has really left a sour taste for me.
Currently, 559. And that's just unique users, many have multiple hubs. We are always interested in increasing the number. Anyone who is interested in helping us, can join our beta group.
Download the Hubitat app
