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)

@trinib, I can't reproduce the problem with version 1.0.47. For me, within 10 seconds, it always transitions from "Waiting for internet" to the full menu after I re-enable wifi. It get the same result whether I rebooted without wifi or just closed and re-opened the agent without wifi.

I don't use the background service (aka the TRIGGERcmdAgent windows service). I'll enable that and do more testing, but that shouldn't effect the tray icon because it's only for the foreground agent.

FYI, the background service is not necessary unless you want to be able to run command while you're logged out. Most people don't need it.

@Leron-Tolmachev,
I just realized you're not saying the command doesn't run. So please confirm: the command runs when you trigger it from HA, but it doesn't log "Command ran" in the runs list, correct?

If so, that's a known issue with sending triggers direct from HA to the agent. The agent doesn't report that the command ran if the trigger came from HA. There wasn't an efficient way to report it because the ID of the command isn't available in this direct local LAN offline context. If you need to see Command ran logged, you should disable the offline HA integration in the agent config.

HA does still send the trigger to triggercmd.com though (which is logged in the Runs list) so cloud integrations (Zapier, Alexa routines, IFTTT, Make, etc) will still trigger if HA can access triggercmd.com when the command is triggered.

@Leron-Tolmachev, if you have parameters enabled, please try turning that off because that might explain why it works when you click the green Trigger button on the triggercmd.com website and it doesn't when you run the command via Home Assistant locally.

If parameters are enabled, Home Assistant will send on or off as the parameter, so " on" or " off" will be appended to the end of your command, which could be producing an invalid command.

Alternatively you could fill in the Off Command field, and that command will run when you toggle the HA switch off.

@Leron-Tolmachev, awesome. Thank you for confirming that works.

For the offline config, did you generate a long-lived access token from this page?
http://homeassistant.local:8123/profile/security

And you pasted that into the that Home Assistant Token field in your Home Assistant Offline Configuration page?

Also, you can check your ~/.TRIGGERcmdData/debug.log file for clues.