FYI - SharpTools is already working with Hubitat. You can cross that one off your wish list! 
I have two Hubitat hubs running fine at my home. One for 'Production' and the other for 'Development'. They both work fine. Do you have any specific concerns about running multiple hubs?
Thanks, I haven't had a chance to keep up with SharpTools but just got access to the rule engine a few days ago. I have had correspondence with Joshua in the past and he is a very competent programmer. My biggest concern is how Hubitat is going to integrate with Google home. Currently my two hubs can't be accessed via my one Google home account. SmartThings forces you to pick one Hub or the other. That's why I'm currently running Amazon at one home and Google at another. The only current workaround is to use a separate Google account but that forces me to get double subscriptions to things like Google Music. Not an issue on a family plan but not ideal. Is Amazon able to access both hubs with the same account?
That is a very good question! Maybe @patrick would know the answer? I don't use Alexa on the development hub, just the production hub.
I'll jump on the metoo bandwagon and say I'll be quite pleased once Google Assistant support is added without the need to go through and add individual commands via IfTTT. I don't have the time to migrate all the lights and switches over using that method so I'll keep using ST+GH until it's avail in Hubitat.
Me too, it’s the only thing stopping me moving and porting over other apps I have written... My heart drops everytime I come back to the forum to check.
Would be good to know what the hold up is, at least if we knew it was pending with google or something then would give us more confidence. Until then will keep checking back as I do want to move over..
its pending with google, that was last week, then they advised of some additional reporting requirements that didn't exist until recently, now we have to develop those requirements into the app, then poke the cert agency to review again.
Believe me, no one wants this app completed more than I do, not because I'm a user of it, but because so many of you want it, and the task sits on my shoulder like a rabid parakeet...
From what I've seen, Google takes a painfully long time with stuff like this.
Also: 
This type of transparency is absolutely and completely appreciated (at least by me). I come to the community every day to look for any shred of news; good or bad. Thank you very much for the update.
Thanks for the openness mike much appreciated! Will keep checking back on the status of the parakeet and working with Google sounds like a right PITA compared to Amazon! Good luck!
Until the Google Home integration comes along, i have been using IFTTT and webcore to turn stuff around the house on and off. It uses just a single recipe from IFTTT and a single piston on webcore. Below is how i set things up:-
Over on IFTTT, the "$" in natural language form will be either on or off and then followed by the device.
and the action for IFTTT to push to your webcore piston:-
And finally, the webcore piston itself:-
In the variable called 'multiple1' and 'multiple2', this would be a group of lights that you want controlled.
The silence is haunting me.
When's google integration happening? 
When Google approves it. We've never been through this process before, so we don't know how long it takes. They have everything and it all tests OK, so we're waiting also...
So sorry, I was being jovial towards codahq. But thanks for the answer anyway, i'am looking forward to it happening, must get annoying answering the same question over and over. 
I don't suppose anybody had asked the Google contact how long they normally take to approve these types of things?
I'm frustrated with Google already. They removed two of my apps from the store for not recompiling against a newer target SDK and one of my apps for impersonation that is based on an open source project. "Jill" at Google doesn't understand what that means but insists I'm using other's intellectual property because somebody else also has a compile of the same open source project and we share a lot of the same code base.
Any way... I'm flagged by their automated app copy deterrent system and "Jill" won't take the time to understand why. I can't escalate because Google doesn't do that. Minimum wage "Jill" is their first and only line of defense. If you don't like it Google doesn't care. They used to appreciate hobby devs.
This long approval process is just making my frustration with Google worse.
Of course we have. You obviously understand the drill. We wait, and remain optimistic.
Hopefully there aren't additional steps to expose HE devices to all of whatever it takes to be controlled by their new devices... Specifically the home hubs as someone who has a thermostat hooked to HE I'd love the ability to let my wife get access to the Tstat via home hub..
Is it possible that their approval is delayed due to the release of the new Google Home Hub?
One could argue that the Hubitat is somewhat of a competitor to the GH Hub.
I think it's a distinct possibility that the approval is related to the new Google Home Hub and the probable new API that it and their new overhauled Home app bring. I haven't looked but I'm guessing they changed their API. I don't think I would view the HE hub as a competing product. I don't think Google does either. They don't provide lighting or any other devices or solutions. They just aggregate other companies' services and devices so far.
But I think you are right that the delay could be related. They might not want to approve a new integration on the old API if new data is required for the new API. Maybe that's what our HE guys had to supply a few weeks back.
Incidentally... Google's new UI in the overhauled Home app is going to make not having an Android app for HE a lot easier pill to swallow. It's not horrible looking and it will control most of my devices.
Download the Hubitat app
