fix(gateway): respect explicit platform disable for Home Assistant in env overrides

[bwoliveira]

Summary

Checks on during env override processing when is present in .

Problem

When running Hermes in multiplexed gateway mode (), secondary worker profiles inherit process-level environment variables (including ). Without checking , env override processing force-enables Home Assistant even when is explicitly configured on secondary profiles, resulting in duplicate credential startup errors:
.

This matches the explicit-disable pattern used for other platforms (Telegram, Slack, API Server).

Validation

• Unit tests run via (passed cleanly).
• Verified on a multiplexed gateway setup with secondary worker profiles containing .

[bwoliveira]

Added regression test in verifying that explicit is honored for Home Assistant even when is present in .

[teknium1]

Thanks for isolating the Home Assistant correction into its own focused PR. Current main does unconditionally re-enable Home Assistant when HASS_TOKEN resolves (gateway/config.py:2081-2086), while the shared env-enable helper already preserves explicit disables (gateway/config.py:1820-1835).

Problems

• The new regression test does not model the stated multiplex path. Its autouse fixture pins multiplex mode off (tests/gateway/test_multiplex_credential_isolation.py:15-19), while a real GatewayRunner enables the fail-closed secret scope (gateway/run.py:5551-5558). With multiplex active, an absent scoped HASS_TOKEN does not fall back to os.environ (agent/secret_scope.py:150-156).

Suggested changes

• Either describe this as a general env-override precedence fix, or make the test activate multiplex mode and supply HASS_TOKEN from the secondary profile's scoped secrets before asserting enabled: false wins.

Automated hermes-sweeper review.

[bwoliveira]

Updated to explicitly model both ambient environment variables () AND active multiplex mode with scoped secrets ( + ), proving wins in both modes.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #54736. Both patches implement the same Home Assistant explicit-disable predicate in gateway/config.py; #54736 already covers the broader configuration shapes.

[bwoliveira]

Closing this as a duplicate — the same fix is already covered by several open PRs from other contributors:

• fix(gateway): respect platforms.*.enabled: false even when env vars are present #73724 (webtecnica): respect platforms.*.enabled: false even when env vars are present (all platforms)
• fix: respect config.yaml enabled:false for HomeAssistant/Email/SMS (#55113) #55447 (Stoltemberg): respect enabled: false for HomeAssistant/Email/SMS
• fix: respect disabled Home Assistant gateway config #54736 (stalingomez): respect disabled Home Assistant gateway config
• fix(gateway): stop HASS_TOKEN from overriding enabled: false #25089 (ms-alan): stop HASS_TOKEN from overriding enabled: false
• fix(gateway): respect explicit enabled: false in env credential bootstrap (#73289) #73376 (JonthanaHanh): respect explicit enabled: false in env credential bootstrap
• fix(gateway): respect explicit platform.enabled:false in profiles #61164 (gigakun3030): respect explicit platform.enabled: false in profiles
• fix(gateway): preserve explicit platform disables #73303 (CryptoDombili): preserve explicit platform disables

The auto-decompose half of the original fix (former #76864) is already covered by #57837 (srojk34). Closing mine to reduce queue noise — thanks everyone for the broader coverage.