Add Hermes Connector ability

[Bradymck]

Summary

• Adds community/hermes-connector/ — routes voice/chat requests from an OpenHome ability directly to a self-hosted Hermes agent's OpenAI-compatible API server (POST /v1/chat/completions), then speaks the response back.
• No local bridge process needed at runtime — just two ability secrets (hermes_api_url, hermes_api_key).
• README is written in plain, simple English with numbered setup steps, aimed at non-native English speakers.

Test plan

• Deployed and tested live end-to-end against a real OpenHome DevKit + a self-hosted Hermes instance (exposed via Tailscale Funnel) — confirmed voice trigger → Hermes response → spoken back.
• Validated with openhome validate locally before submitting.
• get_api_keys() return value defensively normalized (handles both string and dict shapes seen in testing).

[github-actions]

🔀 Branch Merge Check

PR direction: add-hermes-connector → dev

✅ Passed — add-hermes-connector → dev is a valid merge direction

[github-actions]

✅ Community PR Path Check — Passed

All changed files are inside the community/ folder. Looks good!

[github-actions]

🔍 Lint Results

🔧 Formatting fixes available

This PR is from a fork, so fixes could not be pushed automatically. Download the python-lint-results artifact from the workflow run for the patch file, then run:

git apply autofix.patch

✅ __init__.py — Empty as expected

Files linted: community/hermes-connector/main.py

✅ Flake8 — Passed

✅ All checks passed!

[github-actions]

✅ Ability Validation Passed

📋 Validating: community/hermes-connector
  ✅ All checks passed!

[Pixelpushin]

Update: reworked this to use Local Link's built-in hermes backend instead of a direct HTTP call to a tunnel-exposed API server, per Uzair's review in Slack. It now goes through exec_local_command() targeting "target": "hermes", which runs hermes -z locally via the bridge — no public exposure, no API keys, no dashboard secrets. Just Hermes installed + openhome local start running. Much simpler setup, and matches how the existing openclaw template works.

[uzair401]

Thanks for the submission and updates, @Braddock and @Pixelpushin.

I have implemented Hermes ACP, which is the officially recommended way to communicate with Hermes from external tools while preserving conversation context and memory. The Local Link WebSocket is designed for this purpose, so users only need to run openhome local start or openhome local run; the remaining setup is handled automatically.
I am still approving this PR for users who prefer the API Server endpoint. You can also run the API server and connect to it through OpenHome Local Link by creating an updated ability from the template. Users can choose whichever approach works best and is easiest for them.

Once again, thanks for the submission.