Repository navigation
2026.10.5.2 — Readable action tool names
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.