-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser_Mod stops working since a few hours / days #797
Comments
+1 my browser mod has broken also. Edit: Actually my issue was with WallPanel : j-a-n/lovelace-wallpanel#343 |
I habe the same Problems since A copple of days. |
Restarted the tablet and Fully and up and running again |
Not working for me, when I click Browser Mod on the side panel it opens a blank black screen. When I try it on my phone I get an all white screen. |
My Home Assistant version: 0.XX.X
Supervisor 2024.12.3
What I am doing:
All browser-mod entities are unavailable. The browser-mid is stoll on the menu on the right side, but clicking on it, the page shows nothing (blank)
Browser-mod 2.3.3
Core 2025.1.4
Supervisor 2024.12.3
Operating System 14.2
What I expected to happen:
Browser mod working
What happened instead:
All browser-mod entities are unavailable. The browser-mid is stoll on the menu on the right side, but clicking on it, the page shows nothing (blank)
Minimal steps to reproduce:
Cluck browser-mod menu on the right or check entities ... they are all unavailable
Error messages from the browser console:
By replacing the space in the checkboxes ([ ]) with an X below, I indicate that I:
[ x] Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
[ x] Have made sure I am using the latest version of the plugin.
[ x] Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
[ x] Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
The text was updated successfully, but these errors were encountered: