Over the last few weeks, I have been having issues with the integration between Sharptools and Hubitat failing and my dashboards only show placeholders. To rectify, I would have to go into Sharptools to re-authorize my Hubitat Hub. When I just tried to reauthorize my Hubitat hub today, I receive this error. Anyone else having this issue?
Hi @darlenetboggs - thanks for posting. Were you able to click the link included in the warning message?
It has a pretty good description of what's going on: the short version is that Hubitat's OAuth servers have been experiencing performance issues for the past few weeks which causes issues authorizing Hubitat to resources like SharpTools, Google Home, Alexa, IFTTT and more.
I've included a copy of the link below for reference:
Hubitat OAuth Connection Issues - #2 by josh - SharpTools.io (web) - SharpTools Community
As for the placeholders, we released some improvements to the background sync process on Friday that should avoid your location getting deauthorized during background syncs (Friday's post). That being said, if you manually go through the authorization flow, you're still at the mercy of Hubitat's OAuth servers. Some people have mentioned that they've had some success by waiting a few minutes and trying the authorization again.
Yes, I actually saw that post. It took about 10 minutes (including a reboot of my hubitat just to be on the safe side) to get my dashboards up and running again. If the fix to avoid getting deauthorized was in place last Friday, it didn't work for me today....
Thanks for the feedback and sorry to hear that happened. I checked the logs and I see that the fallback process also failed for your account for some reason. We'll get some more logging added, so if it happens again, we'll be able to better understand what happened.
Edit: We've identified the issue that caused the fallback not to work and have pushed an update that should resolve it. Thanks again for reporting!
2 Likes
Sounds like I have similar issues for the last two weeks.
Can you describe your issue in more detail?
Twice in the last 2 two weeks, sharptools dropped my authorized connection to Hubitat. Most of the devices showed up as placeholders. Reboot and reauthorization helped. Never happened before.
@josh Just started having an issue with my Sharptools dashboard icons not working. I tried reauthorizing from within Sharptools and this is what I'm getting.
Getting Placeholder icons now for everything coming from Hubitat
Rebooted the hub many times, as well as my router/modem. I also tried adding/removing a couple items to the Sharptools app within Hubitat and it "appears" like it's sending over to Sharptools, but something is definitely not linked anymore. It doesn't seem to be the OAuth issue based on everything I've read, but I'm not sure what to try next.
I'm nervous to remove and readd Sharptools in Hubitat in hopes I don't have to redo every tile on the ST dashboard, but do these even have the chance to repopulate with a reconnection?
Thanks for the tag. This is different than the issue originally reported at the start of the thread.
The original issue in this thread was that the Hubitat OAuth servers were fundamentally having issues in July '23. Once Hubitat resolved the underlying issues with the Hubitat OAuth Servers, that resolved the issue.
As shown in the screenshot above, your issue appears to be around communication with your hub (using Hubitat's Cloud Relay). Hubitat is reporting the message:
"Hub is not responding, please verify it is running and connected to the internet"
Does your Hubitat Admin Interface show any notifications about cloud connectivity? If I remember correctly, it usually shows in the little message icon in the top-right, but someone who has seen it recently might be able to confirm.
And have you tried other cloud-to-hub communication: Cloud Link for Hubitat Maker API, Authorizing Google Home / Alexa / IFTTT?
That's an outbound communication from your Hub to SharpTools. So your Hub is able to send messages to SharpTools. But SharpTools (+Hubitat Cloud Relay) isn't able to send messages to your Hub as noted by the "Hub is not responding..." message.
I would also take a moment to think if anything else has changed about the hub or your network configuration recently (new apps / drivers, platform updates, driver updates, configuration changes, etc) as those could be impacting your hub's ability to communicate with the Hubitat Cloud Relay.
SharpTools keys off the Location ID (Hub ID) + Device ID for uniquely identifying a device. So you can once your Hub communication issue is resolved, you could reauthorize the hub and the devices should repopulate.
Similarly, you could remove and reinstall the app if you wanted as long as the Hub ID doesn't change (eg. new hub). Your settings / selections would be removed and your issues with the Hubitat Cloud Relay would need to be resolved before you could reauthorize though.
Hi Josh,
No messages up in the corner
I don't have Maker API installed (and it looks a tad overwhelming lol), but I was able to add a new device to Alexa and see it in the Alexa app (reauth via Hubitat).
With Google Home, the new device I tried didn't show up in my Google Home app. When I tried to "Check for new devices" in the GH app settings, it won't authorize either...although I don't know what the parameter "state"... message is alerting me to.
I'm not sure how else to check the cloud connection. In terms of things that have changed since yesterday- Last night I removed a deprecated Kasa user app to replace it with the built in app, but everything was working after that. I had to re-build my ST dashboard with the replaced Kasa devices, but still everything worked once complete. I updated to 2.3.9.166 after all that, and to be honest I'm not sure what would or would not have been working after that.
It sounds like your hub is having issues connecting to the Hubitat Cloud Relay or something along those lines.
Have you tried reaching out to Hubitat support?
The Alexa test isn't particularly helpful for our purposes if it was all done from the hub itself. It's likely that the outbound communication from your hub to Alexa is working fine too. It's just the inbound communication from the cloud to your hub that seems to be the issue. I was referring to authorizing starting from the Alexa app so it would test the cloud connection. (You may have to unlink and relink in the Alexa app if you wanted it to test that)
The Google home authorization failing further points to it being a cloud connectivity issue.
As for the Maker API, you wouldn't necessarily need to get into the weeds with that. Just a basic app install and checking one of the cloud links that is automatically provided.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
