I added a switch to one of my hubs and updated sharptools and everything went downhill.
Sharptools is not seeing my hub. I have tried to reconnect from the sharptools side but it always says the hub is not responding. I turned on logging and tried to refresh from habitat and it says that everything is fine. That everything is posting to sharptools successfully. I go to a page where a tile is communicating to my hub via maker.api and it is displaying fine.
I have connected to my hub remotely and that works fine. I have rebooted my hub a couple of times but nothing has changed.
I am not sure what else I can try.
It just seems like a one way problem from sharptools to the hub.
What Hubitat hub software version are you running?
There was a bug in one of the Hubitat releases about a month ago that caused issues with authorization but from what I remember the authorization screen from Hubitat would be blank rather than it reporting a connection issue.
What’s the exact error message you are seeing? Perhaps a screenshot would help?
What do you mean by this? What exactly do the logs say during an authorization?
The outbound events from the hub to SharpTools are normal during day-to-day operations, but during an authorization starting from your SharpTools User Page , you would expect to see a series of log entries on the hub regarding the authorization, posting the new token to SharpTools, and then the logs related to the actual device sync.
Based on what you’ve described I would expect to see the log messages about the hub communicating to SharpTools working, but I’m more curious if there are any logs related to SharpTools being able to communicate with the hub (paginated syncing of devices) and especially if there are any warnings or errors logged during the sync.
There is no new token sent. It seems to think that there is no problem or need for a new token. Any device updated for this hub is updated successfully on sharptools.
If I try to re-connect my hub from sharptools it takes awhile (seems to timeout) and gives me this:
The message displayed is coming straight from Hubitat’s authorization servers:
Hub is not responding, please verify it is running and connected to the internet
Is this with a Cloud Maker API endpoints or a local Maker API endpoint?
Just to confirm, do device commands to the hub from SharpTools fail too? It sounds like at the very least the Hubitat Authorization servers can’t talk to your hub but I wouldn’t be surprised if the Hubitat Cloud Relay fundamentally couldn’t talk to your hub.
Do you have other cloud authorizations like IFTTT, Alexa, or Google and have you tried reauthorizing / relinking those using their cloud authorization flow?
I can connect to my hub remotely from hubitat’s cloud remote access.
How do I send device commands to the hub from sharptools if my tiles are all just placeholders now? I mean, the devices work for any other hub, just not this one as there is no link right now.
I have 5 other hubitats, one homeassistant and one smartthings all connected to sharptools. I don’t have any other cloud connections except to alexa but from another hub.
I have not tried to reauthorize any of those. Kinda hesitant to try right now.
Thanks for the update. Glad to hear that things are back to normal.
It’s syncing devices whenever the SharpTools ‘app’ on the Hubitat hub is updated with new device configurations. It also performs the device sync when going through the web based auth flow.
The hand-off of authorization tokens is only done through the web based authorization flow starting from your SharpTools User Page .
Here’s a GitHub Gist with some diagrams and notes explaining the process:
