TRIGGERcmds not refreshing in Google Home

Russ

@david-jones , ok, your devices are apparently orphaned. I suggest you disable and reenable the TRIGGERcmd Smart Home action. That should make it start over.
https://assistant.google.com/services/a/uid/0000002be4521c02

It might say unlink rather than disable.

Sorry about the trouble.

David Jones

@russ Just a note before I start any disable/re-enable etc anything, my changes are showing up at https://www.triggercmd.com/user/computer/list
.. and View Triggers therein
but not reflected in my Google Home

Also ran Google Home on another phone and everything there is the same as on the main phone.

David Jones

@russ OK so have done that.

In Google Home app press + at top left
The Setup Device
Then Works with Google
in Home control tab unlinked Triggercmd Smart Home there.

But then when I try to re-link it,

Press Allow in www.triggercmd.com page.
- Nb Correct Google account shows.
Get linking butcomes back saying
"Could not reach Triggercmd Smart Home, please try again"

Russ

@david-jones just now I found TRIGGERcmd Smart Home in my Home app under assistant settings, Home control. I tapped it and selected unlink. Then I search for TRIGGERcmd, tapped TRIGGERcmd Smart Home and relinked.

I'm not sure why you're having trouble linking. If you wouldn't mind sending me a screenshot of your error it might help.

David Jones

@russ Here is a link (on Onedrive) to a video of what I did.
https://1drv.ms/v/s!AvQCqwnHzXJLivJV0aaujm98LgUCnw
Thanks

Russ

@david-jones, nice, that video helps a lot.

I see you have 3 commands with the same voice word - wire. You also have one computer with no commands. Those are abnormal scenarios that might be causing the problem. Can you delete that computer with no commands, or add commands to it, and change the voice words so they're unique and try again?

I'll test those scenarios tonight and if I can reproduce the problem. If I can, I'll fix it by only adding the first command it finds for each voice word, and by ignoring computers with no commands.

EDIT: I verified you can have multiple commands with the same voice word. It will only run the first one it finds, but at least it allows me to link my account.

I also tried linking with a computer in my account that has no commands. That worked fine too, so I still don't know why it's failing on your account.

EDIT2: I see "Duplicated AgentDeviceId.DeviceId" in the logs on the Google Assistant side.
I was able to find your log entries based on the time on your phone in the video you sent.

The Google device ID's are based on your computer and command names, and you do have duplicate commands on your raspberry pi computer, but I don't think that should block linking though because I tried creating multiple commands with the same command name myself and I was still able to link.

I also see you do have some pretty long command names like this:
"DNETCoreGPIO Get-Temp with DHT22-i-Wire Single Value"

I tried that though and I was still able to link.

I hate to have to ask, but to rule out anything out of the ordinary in your commands.json, could you try linking with this super simple commands.json on your Pi?

[
 {
  "trigger": "echo",
  "command": "echo",
  "ground": "foreground",
  "voice": "test",
  "voiceReply": "",
  "allowParams": "true"
 }
]

David Jones

@russ Yeah Bingo, as Tarntino would say!
At about 2pm local time (GMT +11) if your lookinga t logs
I cleared out all of my commands.json file on Pi and put the echo command in.
I was able to relink TRIGGERcmd back into Google Home on phone.
Was able to say "Hey Google,run test on pi" and it works.
And all commands still in commands.com on other devices and this one on Pi show up in Google Home!

So it must be something in the Pi command.json.
I will try restoring it with simple command names(one word no spaces, hyphens etc.)
Thanks, This was beginning to really frustrate me.

David Jones

@russ I think the problem might have been having two commands on the Pi with the same Trigger Name .. which I've changed.

David Jones

@david-jones And yes, all of my Pi commands now work!

Russ

@david-jones, awesome. I'm so sorry for the trouble. Please email me a copy of that commands.json file so I can prevent that problem in the future.