It would not have made a difference if you hadn’t migrated to a google account since that would only apply to users who already had an existing integration. Google killed the Nest API on Aug 31, 2019 so users are not able to create new integrations after that date.
Go the the menu (three bars in the upper left of the screen) select settings (the cog icon) and choose Connected services
OK, apparently I’m not as bright as you’d hoped… the Google Assistant icon was already there, and I went thru the device authorization (again?). What is the next step? My ST’s motion sensor was already showing up in Google Home, but I can’t set the motion sensor to trigger any of the lights.
I’m confused when you say Google Assistant “disappears” from the IFTTT selection list.
As far as I know, Google Assistant never has any available “actions” (the “that” in an IFTTT applet)—only “triggers” (the “if”). (That’s true of Echo as well.) It doesn’t have anything to do with selecting SmartThings as the If. Have you tried creating an applet with some other trigger like location just to see if Google Assistant does appear as a That candidate?
If you had an Echo, you could do what you want with an Echo routine. But as of this writing, January 2020, google assistant routines are not as robust. Google has promised to add more features to their routines sometimes in the future, but they’re not here yet.
I can see the Google Assistant option when I select the initial trigger, (the “IF”), so I know Google Assistant is part of my IFTTT environment, but once I select SmartThings as my “IF”, the option of selecting Google Assistant for my “THEN” disappears. I CAN select my KASA outlets / bulbs for the “THEN”, there’s just no way to have the motion sensor trigger my C by GE lights…
What you are trying to do is not possible with the Google assistant. Google assistant can only be used as a “trigger” in IFTTT. That means it will only appear on the IF side of IFTTT.
@alsterb, you definitely need a Google Assitant Relay to achieve what you want, look at this command.
You will need to tinker to create a WebCore piston when motion starts to send the right command to your Google Home, but it is not going to be a real device as the C by GE will not report back as being on or off when you control it with your real Google Home device. But you can chain it with your motion sensors to turn on or off through the Relay.
It’s up to each individual Device manufacturer whether to make their devices available as an “if” or as a “that” in IFTTT.
SmartThings can be used as either an “if” or a “that” in IFTTT.
Google Assistant can only be used as an “if.” in IFTTT. It can’t be used as a “that“ no matter what you pick for the “if.” Nothing to do with smartThings: that’s a decision by Google.
I’d heard that Google “kinda” broke Nest when they killed the Works with Nest platform, but being new to all this, I didn’t want to assume all that, and I felt that the ST community could either confirm my fears or show me that I was wrong and there was still hope.
I’m not sure what kind of hope your looking for. The motion sensor from the nest thermostat or smoke detector was never exposed. So if you were looking to use the nest thermostat or smoke detector to trigger an automation… it’s not been possible pre or post works with nest going eol. Works with nest also has nothing to do with “C by GE”. When it come to anything works with nest and smartthings… if it’s not already setup and working… it’s not ever going to work and officially it’s never been supported.