IP Ban Manager 1.1.2

Fixed

• Replaced the dynamic GitHub license badge with a static AGPL-3.0-only Shields badge so HACS does not render a broken license image in cached README views.

Note

HACS update/download dialogs may still show the generic "icon not available" placeholder for custom integrations because HACS currently reads those icons from the public brands CDN instead of Home Assistant's local custom-integration brand API. IP Ban Manager ships the correct local brand assets under custom_components/ban_allowlist/brand/ and repository-level brand/.

IP Ban Manager 1.1.1

Fixed

• Added repository-level brand/icon.png and brand/logo.png assets so HACS can show the IP Ban Manager icon on repository and update cards.
• Bumped the manifest to 1.1.1 so HACS installations refresh cleanly from the public release.

This includes all 1.1.0 features: managed blocked networks, allowlist precedence over managed blocks, automatic-ban notification controls, setup/config polish, and blocked-network diagnostics.

IP Ban Manager 1.1.0

IP Ban Manager 1.1.0 adds the big missing piece: managed network blocks. You can now block whole CIDR networks or IPv4 wildcard ranges from the same Configure screen, while exact IP bans still stay in Home Assistant's native ip_bans.yaml workflow.

Added

• Blocked networks for CIDR ranges like 203.0.113.0/24 or IPv4 wildcard shorthand like 203.0.113.*.
• Allowlist precedence over managed network blocks, so trusted addresses can stay available inside a blocked subnet.
• Native exact bans stay native: single-IP bans continue to use Home Assistant's live ban manager and ip_bans.yaml.
• Notification control for Home Assistant's automatic ban/login persistent notifications.
• Diagnostic sensor coverage for managed blocked networks.

Improved

• First-run setup stores the automatic-ban notification preference correctly.
• First-run setup uses a clean Automatic ban notifications checkbox heading instead of exposing the internal option key.
• The options form can submit successfully with an empty Blocked networks field.
• Documentation now clearly explains the difference between exact Home Assistant bans and IP Ban Manager's managed network blocks.

IP Ban Manager 1.0.0

v1.0.0

IP Ban Manager 1.0.0 is the first public release of the expanded integration. It keeps Home Assistant's native IP ban file and ban manager in charge, then adds the UI and safety rails that were missing: setup from the UI, live allowlist edits, live ban review/removal, automatic-ban controls, diagnostics, and scriptable services.

This is still intentionally marked as a HACK because Home Assistant does not expose a supported public API for every part of this workflow. The implementation keeps that internal touch point small, tested, and reversible on unload.

Highlights

• Config flow setup with automatic YAML import for existing ban_allowlist configuration.
• Polished UI setup shows automatic-ban controls and allowlist safe-default checkboxes for 127.0.0.1 and Home Assistant's detected local subnet.
• Live Allowed IPs and Banned IPs management from the integration options, with safe defaults, inline guidance, and readable ban timestamps.
• IPv4 wildcard shorthand for allowlisted networks, such as 192.168.1.*.
• Immediate ban and allowlist updates without restarting Home Assistant.
• Banned IP timestamp display as readable local times, with timestamps preserved when existing bans remain.
• Atomic writes to Home Assistant's native ip_bans.yaml file.
• Oldest-first ip_bans.yaml rewrites so new bans appear at the bottom.
• Safety warnings that reject all-Internet allowlist entries, banning allowlisted IPs, typo removals, allowlist networks containing active bans, and unconfirmed clear-all ban service calls before anything is written.
• Consistent live hook installation even when the integration starts with an empty allowlist, plus clean hook restoration when the integration is unloaded.
• Services for adding, removing, and clearing IP bans and allowlist entries.
• Diagnostic sensors for active bans, allowlisted networks, and failed-login sources.
• Cleanup of stale Home Assistant ban/login persistent notifications when the matching IP is unbanned.
• Integration icon, README screenshots, and updated HACS/repository metadata.

Notes

• Visible integration name is now IP Ban Manager.
• Documentation now clearly warns that this integration is a HACK because it wraps internal Home Assistant HTTP ban manager behavior.
• Documentation and issue links now point to Wheemer/ip-ban-manager.

Compatibility

• Existing ban_allowlist: YAML configuration is still imported.
• Service IDs remain under ban_allowlist.* so Home Assistant service metadata continues to work with the integration domain.