Google Home
-
@Atmosphere, I'm going to try to make it so when you link your Google account to your TRIGGERcmd account it doesn't replace the link, it adds a link. That way you could have her link her Google account to TRIGGERcmd in the Home app, and you'll both be able to use the same TRIGGERcmd account.
Please confirm that would work for you.
Sorry this is taking forever. It's a difficult thing to do, but I'll make it a priority now. Your feedback helps.
EDIT: I started looking at the code and it's not going to be practical to allow multiple Google accounts to link to the same TRIGGERcmd account, so now I'm looking into the idea of being able to share a computer with another TRIGGERcmd user.
In the meantime, you could use her IFTTT account to trigger your TRIGGERcmd commands. I know it's a relative pain to set that up though.
EDIT2: I'm making progress on the ability to share your computers with other TRIGGERcmd users. @Atmosphere, when it's ready, you'll be able to share your computers with your wife's TRIGGERcmd account, and she'll be able to link her Google Home account to her TRIGGERcmd account.
EDIT3: I'm very close. I have a system for sharing your computer so another user can trigger your commands. So far the commands on the shared computer can only be triggered via the website though. I'll update the live system when I test it more and I get Google Assistant working.
EDIT4: It's ready to use now. You can share your computer with your wife's TRIGGERcmd account, then she can trigger the commands on your computer via Google Assistant. She can make one of the computers you share her default computer too. Alexa and Cortana work with shared computers now too.
-
@paskal, @Atmosphere, and @Da-Panda, I finally built a solution for this Google Home voice match problem.
Please try the new computer sharing feature.
-
@Russ Sorry for the late answer, I was travelling. If I understand it correctly, the sharing solution is equivalent to the originally intended linking solution in the sense that it solves the issue for the situation when everybody uses the voice recognition but it does not help if some members of the household use it and others don't. Unfortunately, that is my situation, so while this appears undoubtedly a large step in the right direction, I am afraid it still does not solve the problem in general. Please correct me if I am wrong.
-
@paskal, I'm finding that if anyone using the Google Home device uses voice match on a device, then only people who've setup voice match on that device can use TRIGGERcmd on it, and they have to use their own individual TRIGGERcmd accounts.
BUT, I was able to have myself and my wife use my TRIGGERcmd account on one of my Google Home devices by tapping "Remove Voice Match" in the Device settings for that Google Home device. I also had to make sure "Personal results" was enabled.
So basically, if you want everyone in your household to use a Google Home device to run commands on a computer, your options are:
- Disable voice match on that Google Home device.
- Enable voice match for everyone, create TRIGGERcmd accounts for everyone, and share the computer with each individual TRIGGERcmd account.
-
@Russ Thanks for the clarification. That was my understanding as well - to share TRIGGERcmd for all, either everybody has to use Voice Match or nobody can use it. Unfortunately, the children really want to use the Voice Match (required to teach Google Home important things such as names of our cats etc) while both me and my wife are strictly against Voice Match for us. That means that the children could share TriggerCMD but no solution for the adults. And we'd need TriggerCNS exactly mainly for the adults...
I understand it's a relatively specific situation though, so probably no solution will be available. I was hoping for something similar to Spotify (that works also for non-VoiceMatch members of the household) but I understand it may be difficult to achieve. Thanks for your efforts anyway!
