@josh for SharpTool visibility. Threads everywhere on the forum are reporting poor cloud service. And surprisingly a reboot solves…I would point them to this thread until the Hubitat team steps up.
1 Like
So this issue seemingly impacted my Ring community integration (and my ring alarm system), websocket disconnected and only a re-boot fixed it. But yeah, my whole home arms and disarms etc. using this, so was pretty bad...
I have 2.3.9.164 available as a backup, any particular reason not to roll-back to this firmware?
That only rolls back your database and not the actual firmware. You need to go to the diagnostic tool to roll back the firmware and and your options are more limited (or drastic) to roll back all the way to 2.3.8.140. I suggest contacting support before doing that.
Here is the current firmware rollback versions:
2 Likes
Thanks for explaining 
You can also add earlier platform versions to the list if you want to go back further. See:
2 Likes
So my restart lasted about a week before the Ring Websocket went down again. It would be good to know if a fix for this is being worked on in the next update? Or whether there's some sort of workaround before I choose to roll the firmware back...
Staff are working on a fix, in beta testing.
1 Like
I am running 2.3.9.181 beta now on a hub and haven't seen any concerns in ~18h. 
4 Likes
I am seeing, what I believe is the this same DNS issue, for this HubiThings OAuth oauthCallback() error.
New issue for me since upgrading to 2.3.9.180 yesterday from 2.3.9.174. I have rebooted but the error remains. There have not been any changes to my routers DNS configuration.
How soon will the fix in beta testing be released?
Is it possible for me to get the 2.3.9.181 beta?
Info and link to join beta...since it's a Sunday might be Monday before you're added to the beta:
1 Like
That was released quite some time ago.
This thread has additional issues:
Within this thread, someone advised to roll back to an even earlier version. Worrying that the current informed advice is to roll back to a version released in April'24 to rid yourself of the problem.
However, it now seems these issues have finally hit some kind of critical mass and a beta sounds promising. Something clearly changed in 2.3.9 which has caused major issues for quite a few people, manifesting in a manner of ways, but somehow (I assume) wasn't picked up by the beta group?
I really don't wish to join, but I am curious as to just how many people are involved.
1 Like
I would reboot again. That is the DNS problem and that is the only way to clear. It is not really a time dependent thing, and could happen quickly. You might need to go back into the OAuth and reauthorize it, if things got to crazy.
Not sure on fix to production, but everything has been good on beta the last 30hrs.
3 Likes
It was released this morning.. hopefully this issue is fixed once you are on .181
2 Likes
I just installed new release 2.3.9.181 and was able to clear my “HubiThings OAuth oauthCallback() error” and have successfully authenticated. All good so far.
3 Likes
