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
Popups with Buttons in Grids are empty #568
Comments
Same here, I couldn't see any related logs either. |
Same problem for me after 2023.4 update |
Digging a bit deeper, I can see some exceptions in chrome when I open the popup, the exceptions don't show up in a different dashboard I have with the same buttons but without browser-mod:
|
I noticed that only the popups related to the "type: light" are displayed but not the "type: button" |
Having the same issue with the button cards. The problem only occurs if there is an entity specified in the button. Just specify a tap action with a service call and don't specify an entity within the button as a workaround! |
the same phenomenon has been happening to me since the update to 2023.4... almost all popups no longer work or nothing happens with the tap action. In the upper part of my dashboard are several chips with auto-entities in the popups. these continue to work.
The other popups on my dashboard unfortunately no longer…
|
I try thanks |
I have a similar issue - reported it here - home-assistant/core#91124 |
I'm using tile cards instead of button cards in my grid pop outs as a workaround if anyone is needing something. The problem is definitely when an entity is assigned to the button. If you want I show states with your buttons, tile or mushroom cards can be used as alternatives |
Same issue here, buttons are not shown anymore. |
I also have the button card missing problem in popups - still missing in 2023.4.3 Using the Tile Card workarround for now - would prefer the Button Card. |
I restored to Core 2023.3.6 and now everything still works, I will wait to update when the problem is solved |
Big issue for me with lots of pop-up cards with buttons missing in grids. |
Same error. Temp workaround worked with custom button card.
|
I have the same problem. I use bootstrap grids on my pop ups and any button that is not a custom buttoncard doesnt display for some reason. |
Same error with button cards:
tried to emulate @artipixel's example above, but no dice with this either:
|
Same problem:
Swapping "type: button" to "type: custom:button-card" in the popup fixes the issue, as a temp solution. Home Assistant 2023.5.2 Browser Mod: 2.2.1 |
Same problem. Even a basic popup with just a button in will reproduce the error
|
Same problem..... version core-2023.5.3 |
Any fix for this? |
Same problem here. Just commenting so i can get an update on any fixes. |
Same problem here. Just commenting so i can get an update on any fixes |
1 similar comment
Same problem here. Just commenting so i can get an update on any fixes |
ja również mam ten problem, zmieniłem okienka na custom button i działają w chrome i aplikacji towarzyszącej, natomiast w wallpanel nie działają mi akcje tap_action. Może ktoś się spotkał z tym dodatkowym problemem i zna rozwiązanie. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Not stale at all. This bug is very much alive and kickin'. |
My Home Assistant version: 2023.4.1
What I am doing:
I updated to HA 2023.4(.1)
What I expected to happen:
Pop Ups should be displayed.
What happened instead:
Pop Ups containing a Grid with Buttons is showing nothing
Minimal steps to reproduce:
I just updated.
By replacing the space in the checkboxes ([ ]) with an X below, I indicate that I:
Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
Have made sure I am using the latest version of the plugin.
Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
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: