I tried reproducing in my dev envionment with release build of latest Frontend and canāt reproduce. All fine with media queries after restarting Home Assistant.
Thanks for testing. Did same more as well. First I saw that the other css is applies, eg vertical align. But then I saw, that the width is different on different pop-ups with different xx vw. But both far to small. So perhaps is, that everything is working from this perspective, perhaps even in checking media query, but in calculation of the width the vw is based on wrong dimensions?
During checking I saw, that the edit card popup is in this situation far to small in width compared to standard as well.
Curious. After cache refresh in companion app, sometime after app shut down and restart as well (but not always).
I have a problem with Browser Mod since I updated to 2026.2.0.
If I clear the cache on my iPhone or any web browser it just keeps refreshing the screen and I cant get to any pages. I have to restore my HASOS using the CLI.
I know itās Browser Mod because if I uninstall it everything is fine no refreshing.
Sounds like you have a Frontend setting that is causing the loop. When Browser Mod is installed you can use the kill switch to load Home assistant without running Frontend settings so you can get in and have a look.
As settings here may mean you get yourself locked out of Browser Mod panel in some way, there is a Frontend Settings Kill Switch available. Append
?disableBrowserModFrontendSettingsto the Home Assistant URL. e.g.http://localhost:8123/lovelace/0?disableBrowserModFrontendSettings
You can also rename ābrowser_mod.storageā in Home Assistant ā.storageā folder to remove any existing settings.
Thanks. I will have a go tomorrow.
Itās crazy how you learn things on here.
Itās all fine, from the last time I have updated my code you have added a lot of functionality, when I will have some time I will check the documentation and fix it if necessary.
Thank you,
1 Like
Thank you very much it worked.
I cleared ābrowser modā from the custom components folder and the .storage folder and the integrations then restarted HA.
Reinstalled from HACS but left out the āextra_module_url:ā part.
I now have my pop-ups back.
1 Like
Hey,
i observed the since the last āupdatesā that the browser_mod is not loaded correctly from time to time. So i need to refresh the dashboard manually to load my config correctly. I see it really fast because i made some changes on the sidebar order.
Anyone with the same issue? Or anyone idea for a fix?
Hi Darryn, thanks for maintaining this. 
I have a few questions:
- did I miss something since the default dashboard is ignored and I have to set it in the profile?
- the color scheme seems not be device related but to the user anymore?
Also Iām puzzled about the kiosk mode vs hiding header and sidebar.
Yes, change in Home Assistant 2025.12 has made Browser Mod setting legacy as it will not work once you set either Global/User settings in Home Assistant.
š¹ Browser_mod - turn your browser into a controllable device, and a media_player - #2648 by dcapslock. See my earlier post.
Are you referring to the Header colour? This was a change in 2026.2.
The Kiosk mode setting is used to set the internal Kiosk mode that is (will be) used by Companion Apps to set a Kiosk mode. The benefit of using Kiosk mode is that it just fires one Home Assistant internal event.
For Browser Mod, hide sidebar fires a different internal event to just not show the sidebar, but also removes the Hamburger menu DOM element so it does not show and the sidebar canāt be called up again. This DOM element removal can be seen as a hack that is subject to Home Assistant changing the element.
Both Kiosk mode and Hide sidebar do not hide the header, though not sure how the Home Assistant Kiosk mode may develop over time.
1 Like
Regarding this i wonder two things:
- i guess itās not possible to ācombineā these two - so that browser mod would also save itās settings into HAās section, right?
- where is ābetterā to change sidebar ā¦ settings? In HA or in BM ? Or, should i ask: what are ups and downs of one and other? Based on what should user decide?
A few reasons this is not possible.
- Home Assistant has Global and User support for dashboard, but no device support, so it does not fit the Browser Mod model of allowing for Global, Device, User.
- Home Assistant only has āsupportedā methods for setting Global and User setting, but not for clearing, so does not fit the Browser Mod model of being able to clear a setting.
For sidebar, if you stay with Browser Mod then this works, as there are only user settings, and no Global setting for Sidebar in Home Assistant. However, once you set any user sidebar settings in Home Assistant, to be able to clear that to let Browser Mod work, you need to then login as that user, go to the Browser Mod panel, where you will get a warning and option to clear the Home Assistant sidebar settings (NOTE: The clearning is not officially supported by Home Assistant but seems to work fine).
Browser Mod worked in the past as Home Assistant had read all sidebar and dashboard settings from localStorage. These are still used as fallback hence will work if Home Assistant settings are not set. This is why the dashboard setting did not get removed but marked legacy. So it is always good to keep this in mind. For these settings it is not that Browser Mod can do a blanket override, but it can set the localStorage settings so if you have only ever used Browser Mod then the settings will work.
@Mar1us can you describe more of what you are seeing? What do you mean by ālast āupdatesāā - what HA and Browser Mod versions.
Browser Mod needs to wait to have user info to apply Frontend settings, so on a low network, slow devices, this may come into play.
The only thing that comes to mind are far as a recent change is that in Frontend they are brining in lots of view transitions, including for sidebar, so it could be that what changed in an instant before now takes a small time as that is a transition in styling for Frontend. I believe global Frontend transition timing is set to 0ms if you set prefer reduce motion in your device. There will be a CSS var you can set as well I can check if you need.
1 Like
Ahaā¦ thatās what i wondered when reading your explanation. So, thatās āunofficialā but working way. Excellent.
What i just experienced yesterday: when i login on, say, a new tablet with non-admin account i canāt register that tablet in BM, unless i log out and log-in with admin account. I guess thatās intentional, correct? After all, iād say that no admin wantās for ālow-endā users to mess with HAā¦
OK, i solved this by adding a small button card with ābrowser_mod.change_browser_idā function and it worked well
( i think that maybe way in the past there already was a discussion about itā¦ ?)
Thanks!
Yes, intentional to put some security around it. However there is way to manage this by using one of two methods below.
- Have a dashboard element with action to call
[browser_mod.change_browser_id](https://github.com/thomasloven/hass-browser_mod/blob/4d3a95483662ce7743c4ffea9100019d981cb2ba/documentation/services.md#browser_modchange_browser_id)using a Browser Call (fire-dom-event). Se note below from readme - also works to set a new Browser Id. I note this is what you have done.
- If you wish for an interactive popup to change the Browser ID, call
browser_mod.change_browser_idleaving all parameters empty. The popup will include existing Browser IDs for selection fornew_browser_idwhich allows you to recover a Browser ID when it has been lost.
- Use a Browser Mod Tile or Badge to show Browser Id which will show
Browser not registeredas a generic error. You can then use this along withPriviledge userson the dashboard so that those users, who donāt need to be admins, will be able to change the Browser Id when they click on the Tile/Badge. This saves needing your own button/action.
1 Like
yes its hard to explain. I donĀ“t think this is an issue of slowness. This happens on multiple devices and multiple browsers but only sometimes. When it exactly started i donĀ“t knowl
wrong:
after page refresh:
@Mar1us I am thinking this may be due to perhaps having localStorge cleared in your Browsers. Currently, once localStorage is set for sidebar panels by Browser Mod, no refresh is attempted, so you have to do a manual refresh.
2.7.4-beta.1 is now available that will refresh the sidebar when settings change, including when setting localStorage on page load.
if your issue is what I suspect, then 2.7.4-beta.1 should help.
i installed the beta version and will test this now
I have tested it for two days now and have not encountered this issue once. Very rarely, I see the entire sidebar become visible again, but it refreshes āinstantlyā and the customizations are loaded.
I also updated to the final version this morning.
1 Like
Breaking Changes coming in 2.8.0 in line with Home Assistant 2026.3
Hi. A long range warning that in 2026.3 Home Assistant dialogs will all be webawesome (wa) based, with ha-dialog now being what has been ha-wa-dialog for a short while. Browser Mod uses ha-dialog for popups so this will be a Breaking Change for those who do advanced styling with --mdc-x CSS vars etc.
For anyone tinkering with dev Frontend builds, v2.8.0-alpha.2 is available for testing with dev builds. See Migrate Browser Mod dialogs to ha-wa-dialog Ā· Issue #1097 Ā· thomasloven/hass-browser_mod Ā· GitHub for more info. One main issue still to solve is refactoring how custom popup overrides more-info. As there is now default animation on dialogs including more-info, the open and close of the more-info dialog, before the custom popup opening, is much more visually prominent. I have a planned method to use so the more-info dialog does not open at all, similar to how Browser Mod intercepts the sidebar settings dialog.
If you wish to get a flavour of changes, and for other dialog mods you may have done with card_mod v4, have a look at my comment in the same issue thread.
The more-info issue listed above, other issues that may be found in my testing, and styling documentation will all be ready to be released in a 2.8.0 beta in line with 2026.3 beta in a few weeks.
If you are aware of any other custom elements that are use ha-dialog for dialog popups, please make them aware as since the ha-dialog element name stays the same, but is all new, not updating will be breaking for the custom element in 2026.3
UPDATE: 2.8.0-alpha.3 now available which fixes up more-info showing when using custom popup.