Skip to content
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

cant control frontend #730

Open
slaygirlz opened this issue Jul 18, 2024 · 3 comments
Open

cant control frontend #730

slaygirlz opened this issue Jul 18, 2024 · 3 comments

Comments

@slaygirlz
Copy link

My Home Assistant version: 0.XX.X

What I am doing:
chageing Frontend Settings

What I expected to happen:
show options to control each setting

What happened instead:
nothing is showing by pressing the arrow

Minimal steps to reproduce:
click on broswer mod
go to the Frontend Settings
presss the arrows

# The least amount of code or steps possible to reproduce my error

# Put your code/steps here

Error messages from the browser console:

// Select everything from the browser console and copy it

// Paste it here

By replacing the space in the checkboxes ([ ]) with an X below, I indicate that I:

  • [yes] Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).

  • [yes] Have made sure I am using the latest version of the plugin.

  • [yes] Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.

  • [yes ] 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.
    image

@pvillmann
Copy link

pvillmann commented Jul 20, 2024

Same here. It seems to be that the browser settings are completely removed and there is not option to change the settings again.
Browsers new registered, reboot, updated checked -> menus won't unfold.

@pvillmann
Copy link

#718

@villmatt
Copy link

thanks @pvillmann for providing a link to the fix. Just to make sure anyone else that needs to apply the fix, to delete your browser cache.

Same issue as described, the provided fix worked. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants