Redact encryption keys from debug logs - #1587
Merged
Ernst79 merged 1 commit intoSep 8, 2026
Merged
Conversation
Ernst79
approved these changes
Sep 8, 2026
Ernst79
approved these changes
Sep 8, 2026
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
2 participants
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
Prevent BLE device encryption keys from being exposed in Home Assistant debug logs.
Problem
Several config-flow debug statements logged configuration dictionaries directly.
These dictionaries can contain the device
encryption_key, either directly while adding a device or nested inside stored/imported device configuration.When debug logging is enabled, the key could therefore be written to Home Assistant logs and potentially exposed when logs are shared for troubleshooting.
Fix
Redact encryption keys before logging configuration data.
The redaction handles both direct and nested device configuration without modifying the original input or stored configuration.
Non secret configuration fields remain available in debug logs, and config flow behavior is unchanged.