Skip to content

Releases

2026.11.13.1 — Non-blocking OAuth page startup

Choose a tag to compare

@Jenik5 Jenik5 released this 13 Nov 19:56

Fixes issue #10: Home Assistant could warn at startup because the OAuth pairing page read its SVG logo from disk when the module was imported on the event loop.

The packaged SVG is now loaded once in Home Assistant's executor during integration setup. Pairing requests render the same inline logo from memory. The existing Content Security Policy, pairing flow, permissions and OAuth grants are unchanged.

Update through HACS and restart Home Assistant to load the new version. No re-pairing is required solely for this upgrade.

Validation: 113 Python tests, 5 JavaScript tests, package and syntax checks, plus GitHub Actions on Python 3.13/3.14, HACS and hassfest. The regression checks reproduce the old import-time read and verify that startup loads the logo outside the event loop and rendering needs no file read. The maintainer did not deploy this release to a live Home Assistant instance.

2026.10.25.1 — OAuth refresh, pairing preservation and nine languages

Choose a tag to compare

@Jenik5 Jenik5 released this 25 Oct 18:02

Grok Connector 2026.10.25.1

Stable release with OAuth refresh interoperability fixes, optional preservation of existing pairings when permissions change, and four additional languages.

Nine complete languages

Add Catalan, French, Italian and Spanish. The connector now supports English, Czech, German, Polish, Slovak, Spanish, Catalan, French and Italian across Home Assistant configuration, the OAuth pairing page and MCP descriptions. The language selector discovers the new locales automatically.

Keep pairing when adding entities or actions

Enable Configure → Keep access after changes to keep existing Grok pairings valid for updated permissions, including newly added entities and actions. Removed items become unavailable. This option is off by default; with it disabled, permission changes continue to revoke access and require pairing again.

Active MCP sessions are invalidated on permission changes, so the client must initialize a new session to reload its tools. This does not require a new pairing when preservation is enabled. Unfinished authorizations, unredeemed authorization codes and unused pairing codes are canceled in either mode. Revoke Grok access always invalidates existing credentials.

OAuth refresh and diagnostics

  • Accept refresh requests without a repeated resource only when the valid saved grant belongs to the matching client and unchanged connector resource. Explicit mismatches and saved-grant migration to another origin remain rejected.
  • Return error="invalid_token" in rejected Bearer-token challenges while preserving initial OAuth discovery.
  • Add bounded Boolean refresh diagnostics without logging credentials, their hashes, client IDs or request bodies.
  • Preserve the 600-second access-token lifetime, original 30-day refresh deadline, rotation and replay revocation.

These changes address reproduced server behavior. The specific ten-minute disconnect reported in issue #6 still needs reporter-side logs or a live retest. See the troubleshooting guide.

Updating

Update through HACS and restart Home Assistant to load the new integration version. Keeping the same configured origin and permissions preserves existing configuration and OAuth grants. No new pairing is required solely for this upgrade.

HA screens follow the HA user's language, the public pairing page follows the browser, and the configured MCP language controls descriptions shown to Grok. Stable releases do not require beta versions to be enabled in HACS.

Validation

111 Python tests, 5 JavaScript tests, package and syntax checks passed, along with GitHub validation on Python 3.13/3.14, HACS and hassfest. All nine language pairs were checked for completeness and placeholder parity.

Tests use the shipped code with framework adapters and simulated actions. This release has no new maintainer live HA, native browser/editor, physical-device or Grok/Tesla acceptance evidence. See validation details.

Includes PR #7, PR #8 and PR #9.

2026.10.6.1 — Styled OAuth pairing page

Choose a tag to compare

@Jenik5 Jenik5 released this 06 Oct 12:24
549aa5f

The OAuth pairing page now displays the Grok Connector logo in a responsive card and automatically follows the browser's light/dark theme. All five languages and the pairing process remain unchanged. Thanks to @mirecekd for PR #5.

Security review found no weakening of authentication or permissions. The only CSP exception permits the exact packaged stylesheet through a SHA-256 hash; no unsafe-inline, scripts or external assets are introduced. The packaged SVG contains only passive geometry, and the anonymous page still shows entity/action counts only.

  • Added regressions independently verify the served style hash/CSP in all five languages and reject active or external content in the logo.
  • Local validation: 91 Python tests, 5 JavaScript tests, package and JavaScript syntax checks passed. GitHub validation includes Python 3.13/3.14, HACS and hassfest.
  • Existing configuration and OAuth grants are preserved when updating with the same origin and permissions.

See the security assessment and validation evidence. No maintainer live HA deployment or Grok/Tesla acceptance test was performed for this release. Install the update through HACS and restart Home Assistant to load it.

2026.10.5.2 — Readable action tool names

Choose a tag to compare

@Jenik5 Jenik5 released this 05 Oct 16:13
c0d96e7

Grok now receives readable action tool names instead of opaque identifiers. For example, an action named Otevřít bránu is exposed as otevrit_branu. The original title and description remain available.

Changes

  • Derive ASCII tool names from configured action names, normalizing diacritics and limiting the base name to 48 characters. Contribution by mirecekd in PR #4.
  • Keep legacy action_<id> calls working for clients with cached tool lists.
  • Prevent duplicate names from dropping an action or redirecting a legacy alias to another action. Status, legacy identifiers and literal names are reserved; suffixes are checked until unique.
  • Cache retry results by the stable action ID, preserving the existing OAuth grant/session/request-ID scope. Retrying through the other alias returns the cached result rather than executing twice.
  • Retain empty input schemas, fixed action sequences, existing OAuth permissions and private diagnostic categories.
  • Update English, Czech, German, Polish and Slovak guides.

Update and compatibility

Install 2026.10.5.2 through HACS and restart Home Assistant when appropriate. Home Assistant 2026.9.4+ is required. An update with the same configured origin and permissions preserves configuration and OAuth grants; updating alone does not require fresh pairing. Custom public HTTPS addresses introduced in 2026.10.5.1 remain supported.

Clients with cached tool lists may display old names until their tool list is refreshed. Legacy calls continue to work. Renaming an action remains a permission change and still revokes access, requiring new pairing.

Validation

89 Python tests and 5 JavaScript tests passed, with package checks. GitHub CI also passed Python 3.13/3.14 tests, hassfest and HACS validation. New regressions reproduced four failure cases before the fix and verify collision handling for all 64 actions, legacy alias routing, mixed-alias concurrent retries, authorization, fixed arguments and diagnostic privacy. See validation evidence.

Tests use actual connector modules with framework adapters and simulated action runners. This release was not installed into a live HA instance during preparation; Grok/Tesla display behavior and physical actions need separate live acceptance. The contributor's report of live use is distinct from maintainer-verified evidence.

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.

2026.10.4.1 — First stable release

Choose a tag to compare

@Jenik5 Jenik5 released this 04 Oct 20:28

First stable release of Grok Connector for Home Assistant, based on the
accepted 0.1.0b7 implementation.

Features

  • Install through HACS and connect Grok through Nabu Casa using independent
    OAuth credentials; no Home Assistant long-lived token is given to Grok.
  • Select arbitrary entities whose states Grok may read.
  • Expose named actions using Home Assistant's native editor: lights, scripts,
    automations, scenes and sequences with conditions you define.
  • Consistent entity/action editors with icons, immediate icon refresh and
    scrolling lists. Successful settings saves close automatically.
  • English, Czech, German, Polish and Slovak, with extensible translation files.
  • MCP session-scoped request IDs, preventing collisions between separate
    commands such as turning a light on and then off.
  • Bounded diagnostics without credentials or raw MCP session IDs.

Validation

77 Python tests, five JavaScript tests, package and JavaScript syntax checks.
GitHub CI
passed HACS, hassfest and Python 3.13/3.14 for this release commit. The preceding beta series
passed live HACS installation, native HA editor and Grok web acceptance over
Nabu Casa; the user confirmed both light-on and light-off after the session fix.
Tesla client support requires separate acceptance testing.

Installation and update

Add Jenik5/GrokConnectorForHomeAssistant as a custom HACS repository of type
Integration, select 2026.10.4.1 and restart Home Assistant. Stable releases
do not require beta versions to be enabled. Requirements: Home Assistant
2026.9.4 or newer and Nabu Casa remote access.

Existing b7 entity/action configuration and OAuth grants are preserved; version
promotion alone does not require re-pairing. Changes to configured permissions
continue to revoke existing access and require fresh pairing.

0.1.0b7 — MCP session request-ID fix

Pre-release

Choose a tag to compare

@Jenik5 Jenik5 released this 04 Oct 20:12

Fixes Request ID already used when Grok starts a new MCP session for another
command, such as turning a light on and then off. Reusing a request ID in a new
session now executes the requested action instead of colliding with the previous
session's reply.

  • Initialization returns a secure, OAuth-grant-bound MCP-Session-Id.
  • Duplicate requests within one session retain the bounded reply cache. IDs in
    different sessions are independent, including deliberate repeats of one action.
  • Stateless clients remain supported. Without the session header there is no
    reliable deduplication; check state before deliberately retrying an uncertain
    command.
  • Expired, unknown or foreign sessions are rejected. Sessions never replace
    OAuth bearer authentication and are cleared on revoke, policy change or unload.
  • Diagnostic logs now distinguish session presence/validity and RPC errors
    without recording session IDs, credentials or action details.

Validation: 76 Python tests, five JavaScript tests, package and JavaScript syntax
checks. CI validates HACS, hassfest and Python 3.13/3.14. Tests use simulated actions
and do not operate household devices.

Update through HACS and restart Home Assistant. Existing entity/action settings
and OAuth grants are preserved; this update alone does not require re-pairing.

0.1.0b6 — immediate icon refresh and scrollable lists

Choose a tag to compare

@Jenik5 Jenik5 released this 04 Oct 19:03

Action icons update immediately after saving the native action editor, including icon-only edits. This presentation fix retains native values, validation and handlers.

Entities and actions now use the same permanent overflow container, limited to min(400px, 45vh). Scrollbars appear when the content exceeds that height; Add and Submit controls remain outside the scrolling list.

Validation: 64 Python and five JavaScript regression tests, package/syntax checks. GitHub HACS, hassfest and Python 3.13/3.14 checks pass.

Update through HACS, restart HA and refresh the browser to load the versioned presentation module. Configuration and connector access are retained.

0.1.0b5 — unified lists and editable action icons

Choose a tag to compare

@Jenik5 Jenik5 released this 04 Oct 16:33

Entity and action dialogs now share filled rows, close icons for removing items and matching Add buttons with a plus icon. The descriptive field titles move to the main heading, and help paragraphs/redundant labels are removed.

Each action gains HA’s native optional icon picker. Existing actions remain compatible and use the play symbol until an icon is chosen. Icon-only changes preserve connector access and scripts.

Successful Grok options saves automatically finish the native dialog; errors remain visible. Initial configuration, other integrations and chained flows retain HA’s normal behavior. Native forms remain usable if the presentation module is unavailable.

Validation: 64 Python and four JavaScript regression tests, package/syntax checks and all GitHub CI jobs passed.

Update through HACS, restart HA and refresh the browser (force refresh if necessary) to load the current presentation module.

0.1.0b4 — reliable native action list

Pre-release

Choose a tag to compare

@Jenik5 Jenik5 released this 04 Oct 15:32

Opening Configure → Actions now uses Home Assistant’s native object list. Existing actions and Add/Edit/Remove remain usable even when a cached page has not loaded the presentation module.

The scoped module keeps the entity-style appearance and localized Add action label, and its asset URL includes the integration version. No global HA components or event handlers are replaced.

Validation: 59 local tests, package/JavaScript checks and all GitHub CI jobs passed. Installed through HACS on HA 2026.9.4. An already-open browser page displayed all four actions and native Add without the new module. Ordinary menu navigation after refreshing displayed the requested appearance; Edit and Add opened the correct native forms. Configuration, stable action IDs, the Grok grant and the original gateway were preserved. No physical commands were executed.

Update through HACS and restart HA. Close an existing Actions dialog and refresh the HA page (force refresh if necessary) to load the current appearance module. HA’s service worker may initially serve older HTML while refreshing its cache; the native list remains usable meanwhile. No special URL or new pairing is required for this editor update.