Releases: thomasloven/hass-browser_mod
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. 😄
Breaking changes
browser_mod.close_popup
no longer closes standard more-info dialogs. To close a standard more-info dialog usebrowser_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.- Popup card can now override more-info for multiple entities, or entities of area(s), label(s) and/or device(s).
- 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 tobrowser_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
- Popup parameter
allow_nested_more_info
has been removed. It can be removed from yaml though will cause no issues if not removed. - 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
v2.5.0-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. 😄
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.- Popup card can now override more-info for multiple entities, or entities of area(s), label(s) and/or device(s).
- 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 tobrowser_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
- Popup parameter
allow_nested_more_info
has been removed. It can be removed from yaml though will cause no issues if not removed. - 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
v2.4.4
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
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.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
v2.4.4-beta.5
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
v2.4.4-beta.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.4 which should work fine on 'Reload'.
Fixes
- 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
v2.4.4-beta.3
Fixes
- EXPERIEMNTAL: Clear Frontend caches in
browser_mod.refresh
which is used by Version mismatch Reload action (Issue #943) - Hide header fix which may be only partially hidden, generally on slower devices. (Issue #947)
Full Changelog: v2.4.3...v2.4.4-beta.3
v2.4.4-beta.2
Fixes
- Hide header fix which may be only partially hidden, generally on slower devices. (Issue #947)
Full Changelog: v2.4.3...v2.4.4-beta.2
v2.4.4-beta.1
Fixes
- Hide header fix which may be only partially hidden, generally on slower devices and when used together with hide sidebar. (Issue #947)
Full Changelog: v2.4.3...v2.4.4-beta.1
v2.4.3
New Features
- Add activityType attribute to Activity sensor. While Activity is detected, activityType attribute will be one of
userInteraction
orfullyOnMotion
. After the activity cooldown actvityType will revert tonone
. (Feature Request #939) - Browser entity variables available for Frontend settings templates and for adding to action calls via
browser_entities: THIS
.
Fixes
- Fix BrowserID edit field display on small size screens after Frontend Home Assistant style change in 2025.7.
- Don't require audio interaction when media player disabled by user. (Issue #925)
- Only trigger activity on select fullyKiosk events. (Issue #927)
Full Changelog: v2.4.2...v2.4.3