feat(homeassistant): split tool and platform env config#21676
Closed
StartupBros wants to merge 1 commit into
Closed
feat(homeassistant): split tool and platform env config#21676StartupBros wants to merge 1 commit into
StartupBros wants to merge 1 commit into
Conversation
This was referenced May 14, 2026
Author
|
Superseded by the split:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
HASS_TOOL_URL/HASS_TOOL_TOKENfor the Home Assistant tool surface.HASS_PLATFORM_URL/HASS_PLATFORM_TOKENfor the Home Assistant websocket platform.HASS_PLATFORM_DISABLE=1to allow tool-only Home Assistant setups.HASS_URL/HASS_TOKENas the shared fallback for both surfaces.Why
Some deployments want Hermes tools to talk to a local Home Assistant proxy while not enabling the gateway websocket platform, or want the platform and tools to use different credentials/URLs. Today both surfaces are forced through the same
HASS_URL/HASS_TOKENvalues.This keeps existing behavior by default while allowing safer tool-only/proxy deployments.
Test plan
Result:
139 passed, 1 existing RuntimeWarning about _async_call_service.