Skip to content

2026.10.5.1 — Custom HTTPS addresses

Choose a tag to compare

@Jenik5 Jenik5 released this 05 Oct 11:03
08cb928

Grok Connector now supports public HTTPS addresses beyond Nabu Casa. Connect through your own domain or HTTPS reverse proxy, including a nonstandard port such as https://ha.example.org:8125.

The connector URL uses your configured origin:

https://ha.example.org:8125/api/grok_connector/mcp

Changes

  • Accept custom public HTTPS DNS hostnames and optional ports, alongside existing Nabu Casa addresses. Contribution by mirecekd in PR #3.
  • Preserve independent OAuth credentials, selected entities/actions and exact Origin/resource binding, including the port.
  • Tighten URL validation to reject embedded control characters, userinfo, malformed/empty ports, port 0, query/fragment delimiters and browser IPv4 representations.
  • Add custom-port OAuth/HTTP regression tests and a documented security assessment.
  • Update setup text and installation guides in English, Czech, German, Polish and Slovak.
  • Update GitHub Actions checkout and Python setup to v7 through PR #1 and PR #2.

Installation and compatibility

Update to 2026.10.5.1 through HACS and restart Home Assistant when appropriate. HA 2026.9.4+ is required. An update with the same configured origin preserves your configuration and OAuth grants; a version update alone does not require new pairing. Existing Nabu Casa addresses remain supported.

For a custom address, use a DNS hostname you control, public HTTPS with a valid TLS certificate and reachability from Grok. Enter only the origin in HA; append /api/grok_connector/mcp when creating the Grok connector. Changing the configured origin or port requires fresh pairing. See the proxy setup requirements.

Validation

80 Python tests, 5 JavaScript tests and package checks passed. GitHub CI also passed tests on Python 3.13/3.14, hassfest and HACS validation. Tests use framework adapters; compatibility through a particular custom proxy needs live verification. The contributor reported successful custom-domain pairing. This release was not deployed to a live HA instance during preparation; Tesla client acceptance remains separate.