That's interesting @gajahduduk. I'll need to do some research. I didn't know about this issue until you mentioned it here, so thank you for telling me.

As always, I recommend you switch to the TRIGGERcmd Smart Home skill unless you have a specific use-case for the Trigger Command skill.

@Cristian-Dindinelli, yes so far I haven't been able to get it working after the recent change Samsung made.

@TheDreamer68, give me some time to look into this. I'll get back to you soon. So far it seems SmartThings broke this integration recently. I'm finding their new system does not synchronize with the "My Testing Devices" list in the SmartThings app.

I created a new Schema App and found it doesn't show up in the SmartThings app under "My Testing Devices."

I also migrated one of my existing Schema Apps using the smartthings schema:update command, but it doesn't work. I also renamed it and the new name doesn't show up in the SmartThings app under "My Testing Devices."

@Fabrizio-Holstein, does it start if you run it manually?

If not, please try renaming your c:\Users\(your user)\.TRIGGERcmdData folder, and then re-run the triggercmd agent. It will prompt again for the token.

Well, it will update most things anyway.

winget upgrade --all

Thanks @Leron-Tolmachev .

@Leron-Tolmachev, I don't know why the direct from HA path isn't working. I'll see if I can reproduce the issue, but in the meantime I suggest disabling it so you can trigger commands from HA via the Internet. It seems like the connection from the agent to HA isn't working. Maybe I need to add logging to determine that.

@Leron-Tolmachev, I'm not sure why it's working via the Internet but not direct from HA.

Can you try triggering a different command? Like the built-in calculator command?

Also, if your command has parameters enabled, please try disabling parameters. I'm worried the "on" or "off" parameter is getting tacked on to the end of your command and messing up the command, although I'm not confident in that because if that was the problem, it should happen either way - direct from HA, or via the Internet (via the triggercmd.com cloud system).

FYI, that "Ignoring duplicate trigger" is saying it got a trigger via triggercmd.com but ignored it because it originally came from HA, and you have the direct HA integration enabled.

Can you share your command? Or ideally a screenshot from the GUI Editor? I'd like to see if I can reproduce it on my Mac.

@Xander, awesome. I'm glad that worked.

@Russ ‍️Not sure what the bottleneck was but I've been distracted prepping for a short camping trip.

I just realized I didn't restart the PC and, lo and behold, the install went fine. Not sure what was preventing the installer from running.

(Distracted enough that I never hit Submit on this until I just got back)