Add TRIGGERcmd integration

[rvmey]

Breaking change

Proposed change

Add the new triggercmd integration.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: Add TRIGGERcmd integration documentation home-assistant.io#33575

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hi @rvmey

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Stale

[rvmey]

I don't know what "Collect information & changes data Expected — Waiting for status to be reported" means.

Do I need to provide that data and report status somehow?

[cgarwood]

GitHub won't run most workflows on a PR for a first-time contributor to a repository (to protect against people abusing their workflow runners for crypto mining/scams). I believe after someone gets their first PR merged, workflows will then run automatically in the future.

I went ahead and triggered the workflows to run 🙂

[cgarwood]

Couple initial review comments...

[edenhaus]

I'm not familiar with triggercmd but from the variable names I think we should create a device per computer

[rvmey]

I considered that, but I decided each triggercmd trigger should be represented as a device because the Alexa, Google Assistant, and SmartThings integrations create a virtual on/off switch device for each trigger. It makes it easier to educate triggercmd users if the integrations work similarly. I hope that's ok.

[edenhaus]

Nope, we should create one device per computer so all triggers of one computer are grouped in the UI, too.
A device includes additional features like disabling a device, which will also disable all entities for that device. It's common for users to disable devices for a certain time of the year (ex. Disable the sprinkler during the winter)