Already followed suggestion by fellows on this thread to assign duplicated devices to another home on Google side, worked for about a month.
Now the problem occurs when I tell Google to turn on my Chromecast connected TV. It now says “Sorry, it looks like Samsung 6 series isn’t available right now”
In the past i was always able to ask Google to turn on TV for me, because Chromecast is using HDMI ARC, and on my main home it’s a Chromecast device. In fact, when I ask Google to play music, play videos “on TV”, it’ll work, even when TV is off, and you can see Google now understands I want to turn on “Living room TV”:
Google now even confuses itself when I tell it to turn on “Living room TV”, so apparently even “turn on Living room TV” doesn’t work, only tell it to stream something or casting does.
I am pretty sure this issue is because of duplicated devices, and for some reason even I assign that “Samsung 6 series” to a different home, Google still tries to turn on the switch “Samsung 6 series”
Small update, today I managed to ask Google to turn on my TV even when it’s off, by saying “turn on living room TV” on Google home. On my phone, still doesn’t work.
Still it is so frustrating given I only have one TV connected, and it’s broken because of duplicated devices
Where are the routines from the smartthings classic app. These routines ran my house, now they are no longer useable? The scenes in the new smartthings app are nowhere near as customizable. There’s no control over smart home monitor in the new app’s scenes. Is there a work around? When will these routines finally be available again?
Any idea why I keep having to “reconnect account” for SmartThings in my Google Home settings? Everything will be working fine and then randomly I’ll start getting “something went wrong” and “not responding” errors in Google Home. If I go into SmartThings everything works fine … simply reconnecting Google and SmartThings seems to fix the problem for a while, but it keeps happening. Sometimes I go for days or even weeks and then out of the blue, it’s broken again. And sometimes it will happen multiple times in one day (like today).
It was really a semi-rhetorical question and was geared towards someone at smartthings who might actually have an answer. I certainly was not at all expecting to get one, but thanks for trying to answer it anyway.
Samsung has been saying they’re going to eliminate the classic app for over a year. So if the new app doesn’t have equal or greater functionality, it’s a step backwards. Routines are a very big part of our ecosystem, and to not have that functionality with google is a big downfall.
Scene + Automation = Routine. For purposes of Google integration you don’t need a routine (which in classic app had automation built in). You just need scenes that can be triggered by the Assistant.
It has been several months since I looked at a Routine and I can’t recall if they only had the location pre-conditions/restrictions which Automations now have. If not, then there are Routines that can’t be implemented quite the same.
It is certainly the case that Automations can include actions that Scenes can’t. Until it is possible to write any Automation just using Scenes as actions, there is no real equivalent to executing Routines as you can’t activate Scenes instead. Messing around with virtual switches and things should not be required.
Dang, well guess its time to switch platforms…I just don’t understand how ST thinks going from a mature platform to removing feature after feature is somehow an upgrade. Seriously guys, finish the new app and functionality first, then release it, enough of these half-arsed updates that break our smart homes.
Routines had location mode filter/condition. Adding that to the automation creator in the new app was bringing the new app up to parity with Classic routines.
I have the simplest of desires. All i want to do is connect my google home to smartthings via my samsung account. I’ve been working on it for 3 days. Everytime i attempt to add a new devices/works with google/ select smartthings/ login to my samsung account, it looks like it is going to work. But at the last moment it puts me back into the add new device / works with google menu, and i check the list of services and smartthings not samsung is there. Repeat 1000 times. Tried a different google account, different samsung account, different phone, tablet everything. Oddly google assistent does list samsung afterwards, and smartthings list google as linked, but nothing ever in the google home app.
Odd that the only function i wanted is to say ok google lock my doors, and this cannot be achieved.
QA is really questionable. I’ve seen my problem in a couple forums
Locks are not supported in either the old Groovy Google voice integration or the new integration unfortunately. If you PM me your account email I’ll check if I can find the reason for you not being able to link (if you have other supported devices than a lock that you want to use that is). If you do not have any supported devices, Google home app will not show your SmartThings action as linked.
This is not true at all. Routines in the classic app are much more customizable than scenes in the new app. I can’t control the smart home monitor from scenes in the new app, that’s just one of a few examples. Yes, there are workarounds, but the point is I shouldn’t need to constantly tweak things because their “upgrades” remove functionality.
If you want to combine it with scenes, have the scene turn on a virtual switch and have the virtual switch trigger the automation that changes the security.mode.
I’m not saying it’s pretty, but it is doable. And most people won’t need a scene at all for this particular purpose.
I realize there’s a specific date. So, are they telling us when we can expect to lose features? Is that what’s happening?
My point is, they’ve had years to refine this new app and bring it up to par with the classic. If the new app doesn’t support the routines (among other features) that many people have spent a great deal of time creating and implementing, it’s a big step in the wrong direction.
As I said, I realize there are workarounds. But, like I also said, I don’t feel I should have to constantly tweak things because they remove features. It’s pretty simple, the new app should be as good or better than the old. That is not yet the case apparently.
