@mvevitsis
HomeAssistant running HomeKit Controller allows adding HomeKit devices to HomeAssistant. HomeAssistant can then use MQTT to share these to Smartthings.
1 Like
Nice share…
I tried home assistant about a 1-2 years ago and with all the projects going on I didn’t have time to learn the beast that was Home Assistant 
I was bored one night last week and decided to install HASS.io on my ESX server at home and I have to admit it’s much more approachable now. Creating rules and automations is simple now and doesn’t require you to mess with config files for every single aspect of the configuration.
The ST integration is also pretty impressive and uses the new API so you can use all your ST devices, scenes in Home Assistant.
I suppose that’s a solution but I found my life was happier after ditching google nest and going with zwave devices or at least devices with a native cloud ST integration.
The only hangup is the smoke detectors, nest’s are better.
This one?
yep that’s the same API
1 Like
It would likely need entirely re-coding, that’s likely why @tonesto7 hasn’t done it and I don’t blame him. If it were easy, it would have been done already and the chances are, if it was done, the user base of ST is large enough that there’s a risk that Google might just take note and find a way to block it because it’s a little sneaky, thus making all the effort wasted while at the same time, you’ll have upset a lot of Home Assistant users as well…
Google isn’t going to spend the time remaking their entire web app because of an unofficial smartthings integration. It would take too much time and cost too much for no benefit to themselves.
The only reason it hasn’t been done is NST manager would have to be re-coded from the ground up, and badnest can’t be ported to smartthings as-is unlike say a hubitat dth.
In any case, screw nest. I’m done with them.
1 Like
I’ve moved over from HomeAssistant to SmartThings and have a clientId and secret for Nest working with HomeAssistant. Is there a way to modify the code to force these credentials into NSTManager?
No, there isn’t
Do you still have the token that was generated under homeassistant?
Do you mean clientId and secret? I have them
So I haven’t migrated my old Nest account to Google, but I do need to reestablish the token with NST Manager by logging in to Nest from the NST Manager app. When I enter my credentials, that works, and provides me the “Works wit Nest” screen, but when I click on ALLOW, at the top of the screen it displays “Oops! We’ve encountered an error. Please try again.” - does this token refresh also end my integration with Nest now ? I thought it was only me moving to a Google account. Thanks.
Sorry, once you migrate to a Google account… game over as far as using NST Manager.
2 Likes
But I haven’t changed to a Google account yet. Just trying to reassociate my Nest credentials in the NST Manager app. I get all the way to the Works with Nest screen where it asks me to confirm, so it’s taking my valid creds, but just fails when I try to confirm the share in Works with Nest.
You can no longer login to that Nest account from NST Manager. Google has closed that down.
Well _____ … !#$! … I didn’t know just having to reenter my credentials would permanently break it … I thought changing to a Google account/login was the thing to avoid. Crap.
I don’t know if there another way to pin a message for this thread because this is getting a bit annoying.
If you have to re-authenticate NST Manager for absolutely any reason at all whatsoever, you’re screwed, you won’t be able to get it working again so there’s no point in asking.
1 Like
This includes if. You setup two factor auth if you didnt previously have it. So when they force it later this year… RIP
Hey Anthony, would appreciate your feedback as to whether it’s possible to use the ID and secret from home assistant for the smartapp?
Well I bit the bullet last night and uninstalled all things NST Manager and cleaned-up/removed all the rules. webCoRE got very unresponsive last night, but this morning it’s back to normal and I have to say everything is much more responsive for some reason. Maybe freed up a bunch of memory, not sure.