New features

• New service browser_mod.change_browser_id. See SERVICES.md for more information.
• Browser ID edit field on configuration page now a combo-box which includes existing known Browser IDs. This may be useful to reset a Browser ID that has been lost.

Fixes

• Fix interact console error on touch devices. (Issue #1016)
• New service browser_mod.change_browser_id by @dcapslock in #1018

Full Changelog: v2.5.2...v2.5.3-beta.1

Updated

• Make Full user ineteraction a Frontend option with default off (Issue #1010)

Full Changelog: v2.5.1...v2.5.2

New features

• Home Assistant Sidebar settings are now blocked for non-admin users. If a non-admin user tries to use a Home Assistant method to change their siderbar settings, they will get the notification Sidebar settings are managed by owner/admin using Browser Mod integration. (FR #996)
• User interaction check has been updated and now includes a full interaction phase if the Browser requires clicking play on a media element rather than just a standard screen click/touch. See User interaction for more information. (Issue #989)

Fixes

• Fix browser_mod.notification with no action_text causing error in Home Assistant 2025.9.0b0, or a blank button in earlier versions. (Issue #1003)
• Fix console warnings when Browser is not registered.

Documentation

• Update documentation to better describe the difference between Server calls and Browser calls for Browser Mod services.
• Clarify best practice for managing Browser ID updates in an enviroment where they may reset from time to time. (Thanks @Yinmeout)
• Update Browser Title jinja template example (Thanks @Mariusthvdb)
• Update some popup example images clarifying that standard popups are not vertically centered.

Thank you to contributors and reviewers

@Mariusthvdb - @Yinmeout

Full Changelog: v2.5.0...v2.5.1

New features

• Home Assistant Sidebar settings are now blocked for non-admin users. If a non-admin user tries to use a Home Assistant method to change their siderbar settings, they will get the notification Sidebar settings are managed by owner/admin using Browser Mod integration. (FR #996)
• User interaction check has been updated and now includes a full interaction phase if the Browser requires clicking play on a media element rather than just a standard screen click/touch. See User interaction for more information. (Issue #989)

Fixes

• Fix browser_mod.notification with no action_text causing error in Home Assistant 2025.9.0b0 or blank button in earlier versions. (Issue #1003)
• Fix console warnings when Browser is not registered.

Documentation

• Clarify best practice for managing Browser ID updates in an enviroment where they may reset from time to time. (Thanks @Yinmeout)
• Update Browser Title jinja template example (Thanks @Mariusthvdb)
• Update some popup example images clarifying that standard popups are not vertically centered.

Thank you to contributors and reviewers

@Mariusthvdb - @Yinmeout

Full Changelog: v2.5.0...v2.5.1-beta.3

New features

• Home Assistant Sidebar settings are now blocked for non-admin users. If a non-admin user tries to use a Home Assistant method to change their siderbar settings, they will get the notification Sidebar settings are managed by owner/admin using Browser Mod integration. (FR #996)
• User interaction check has been updated and now includes a full interaction phase if the Browser requires clicking play on a media element rather than just a standard screen click/touch. See User interaction for more information. (Issue #989)

Fixes

• Fix browser_mod.notification with no action_text causing error in Home Assistant 2025.9.0b0 or blank button in earlier versions. (Issue #1003)

Documentation

• Clarify best practice for managing Browser ID updates in an enviroment where they may reset from time to time. (Thanks @Yinmeout)
• Update Browser Title jinja template example (Thanks @Mariusthvdb)
• Update some popup example images clarifying that standard popups are not vertically centered.

Thank you to contributors and reviewers

@Mariusthvdb - @Yinmeout

Full Changelog: v2.5.0...v2.5.1-beta.2

In version 2.5.0 the method of displaying popup dialogs has been refactored to use the Home Assistant dialog manager. This change fixes a myriad of z-index issues that have been managed or worked around in the past. It also allows for multiple popups by popup tag. 😄

Breaking changes

• browser_mod.close_popup no longer closes standard more-info dialogs. To close a standard more-info dialog use browser_mod.more_info with no paramaters.

New Features

• New Panel sensor providing all information about the current Panel in view whether it be a lovelace panel, other Home Assistant Panel or a custom panel. Sensor value is the panel's name, including the current view when the panel is a lovelcace panel. Sensor attributes are PanelTitle, PanelUrlPath, PanelComponentName, PanelIcon, ViewTitle, ViewUrlPath, FullUrlPath, PopupOpen.
• Popup card (custom:popup-card) has two significant upgrades. See Popups section in README for more information.
  1. Popup card can now override more-info for multiple entities, or entities of area(s), label(s) and/or device(s).
  2. Popup card can now have a popup card ID which can be used in browser_mod.popup service allowing for popup cards to be used as template, saving lots of yaml crafting. Parameters supplied to browser_mod.popup override anything in the popup card.
• Support multiple popups per popup tag. See Multiple Popups section in POPUPS for more information.

Fixes

• Media player sometimes unavailable for versions 2.4.3 and 2.4.4
• Refcatoring of popup dialog means that all previous z-index issues with standard more-info dialogs and form pickers are no longer an issue.

Important

1. Popup parameter allow_nested_more_info has been removed. It can be removed from yaml though will cause no issues if not removed.
2. Refcatoring of popup dialog means mean that if you have styled the z-index/position CSS properties of popups to workaround form selector issues, these should now be removed as they are no longer required and may now cause their own z-index issues.

Thank you to @j9brown who provided his time for review of the changes for 2.5.0.

Full Changelog: v2.4.4...v2.5.0

In version 2.5.0 the method of displaying popup dialogs has been refactored to use the Home Assistant dialog manager. This change fixes a myriad of z-index issues that have been managed or worked around in the past. It also allows for multiple popups by popup tag. 😄

New Features

• New Panel sensor providing all information about the current Panel in view whether it be a lovelace panel, other Home Assistant Panel or a custom panel. Sensor value is the panel's name, including the current view when the panel is a lovelcace panel. Sensor attributes are PanelTitle, PanelUrlPath, PanelComponentName, PanelIcon, ViewTitle, ViewUrlPath, FullUrlPath, PopupOpen.
• Popup card (custom:popup-card) has two significant upgrades. See Popups section in README for more information.
  1. Popup card can now override more-info for multiple entities, or entities of area(s), label(s) and/or device(s).
  2. Popup card can now have a popup card ID which can be used in browser_mod.popup service allowing for popup cards to be used as template, saving lots of yaml crafting. Parameters supplied to browser_mod.popup override anything in the popup card.
• Support multiple popups per popup tag. See Multiple Popups section in POPUPS for more information.

Fixes

• Media player sometimes unavailable for versions 2.4.3 and 2.4.4
• Refcatoring of popup dialog means that all previous z-index issues with standard more-info dialogs and form pickers are no longer an issue.

Important

1. Popup parameter allow_nested_more_info has been removed. It can be removed from yaml though will cause no issues if not removed.
2. Refcatoring of popup dialog means mean that if you have styled the z-index/position CSS properties of popups to workaround form selector issues, these should now be removed as they are no longer required and may now cause their own z-index issues.

Thank you to @j9brown who provided his time for review of the changes for 2.5.0.

Full Changelog: v2.4.4...v2.5.0-beta.2

This version requires Home Assistant 2025.8.0 or later

IMPORTANT: If your device suffers from a 'Reload' loop on version mismatch, you will not benefit from new code included to clear application caches until the next version release as your device is still using old browser_mod.refresh code. In this case you can use the workaround as decribed in this Wiki Article to clear application caches on the device.

New Features

• Allow for styling of popop buttons via variant and appearance using new button styles introduced in Home Assistant 2025.8. See SERVICES and POPUPS documentation for more information. (FR #958)

Fixes

• Update mwc-button to ha-button in line with ha-button changes in HA 2025.8 which drops mwc-button.
• Disable Register and Browser ID for non-admin users in Browser settings. Informative alert will show if user is not an admin. (Issue #783)
• Clear Frontend caches in browser_mod.refresh which is used by Version mismatch Reload action (Issue #943)

Full Changelog: v2.4.3...v2.4.4

IMPORTANT: If you are testing clearing Frontend caches to manage recurrent version mismatch errors, please note that you need your browser/device to have at least v2.4.4-beta.3 working (no version mismatch) before clearing Frontend caches will start working with 'Reload'. So a good test is to install v2.4.4-beta.3, clear cache using workaround, then install v2.4.4-beta.6 which should work fine on 'Reload'.

New Features

• Allow for styling of popop buttons via variant and appearance using new button styles introduced in Home Assistant 2025.8. See SERVICES and POPUPS documentation for more information. (FR #958)

Fixes

• Update mwc-button to ha-button in line with ha-button changes in HA 2025.8 which drops mwc-button.
• Disable Register and Browser ID for non-admin users in Browser settings. Informative alert will show if user is not an admin. (Issue #783)
• Clear Frontend caches in browser_mod.refresh which is used by Version mismatch Reload action (Issue #943)

Full Changelog: v2.4.3...v2.4.4-beta.6

IMPORTANT: If you are testing clearing Frontend caches to manage recurrent version mismatch errors, please note that you need your browser/device to have at least v2.4.4-beta.3 working (no version mismatch) before clearing Frontend caches will start working with 'Reload'. So a good test is to install v2.4.4-beta.3, clear cache using workaround, then install v2.4.4-beta.5 which should work fine on 'Reload'.

Fixes

• Update mwc-button to ha-button in line with ha-button changes in HA 2025.8 which drops mwc-button.
• Disable Register and Browser ID for non-admin users in Browser settings (Issue #783)
• Clear Frontend caches in browser_mod.refresh which is used by Version mismatch Reload action (Issue #943)
• UPDATED: Hide header fix which may be only partially hidden, generally on slower devices. (Issue #947)

Full Changelog: v2.4.3...v2.4.4-beta.4