-
Notifications
You must be signed in to change notification settings - Fork 27
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
2024.7.0b* somehow breaks visibility of the card #117
Comments
Since I installed 2024.7 I also have the same issue. When I refresh it several times it goes up again but then it disappears again. |
Me too... Same behaviour |
Same, my template state switch cards are fine though, it’s only those based on entity state (on/off) |
Same issue. Following. |
same. fwiw, i don't think the issue started for me until updating to 2024.7.1 today. though maybe i just didn't notice it on 7.0 |
I noticed it at one of the early betas of 7.0. |
Me too... Same issue. |
Me too |
Same for me. |
Same issue 😗 |
all - my anecdotal experience from this afternoon is that the problem might be fixed (or at least less prominent) if you set a default state for each state switch card. i hadn't previously done that but i just replaced all the instances of auto populated "default: null" with "default: [your default state here]". something to check in your configuration...though again, it's entirely possible that i just haven't yet seen the issue recur after making that change but it will at some point ... |
Something is still broken, but thats a good call out as a help for now.
When I call out a default the page initially loads with the default, even
if its wrong for the condition but then fixes itself if I refresh... but at
least I have a work around ish now! Thanks!
…On Sun, Jul 7, 2024 at 11:02 PM robertoleonardo ***@***.***> wrote:
all - my anecdotal experience from this afternoon is that the problem
might be fixed (or at least less prominent) if you set a default state for
each state switch card. i hadn't previously done that but i just replaced
all the instances of auto populated "default: null" with "default: [your
default state here]". something to check in your configuration...though
again, it's entirely possible that i just haven't yet seen the issue recur
after making that change but it will at some point ...
—
Reply to this email directly, view it on GitHub
<#117 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHGRLNUKINJCDANMBHFWASTZLH6MBAVCNFSM6AAAAABKD5YB7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJSHA4DQMRRGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Same |
Updated yesterday to 2024.7 release, seeing same issues :-( Is someone with code skills working on this? |
Install layout-card whit HACS, edit view in your Dashboard. in view type choose "Horizontal (layout-card)" or "Vertical (layout-card)" or "Grid (layout-card)" ... depending on what you want. |
So we need to change all card that ere being used with the State-Switch to the layout card?? |
this makes me feel like i'm using state switch cards and layout cards all wrong. i use custom layout card already but it's not even sort of a replacement for how i use state switch cards .... separately, has anyone noticed their dashboard get suppppper laggy since this issue arose? my dashboard is fairly intricate but i'm running hass on a nuc with very little else --- so it's got plenty of juice. and it was fine until recently. i think that whatever is happening to make the state switch cards not appear until you refresh a few times is taking parts of my dashboard captive until all the stuff with the state switch card figures itself out and loads. |
I stopped using state-switch card, and used the builtin contifional card, one less Hacs for me now |
I can confirm the procedure, for me this was the solution. Thank you for finding the solution! |
I will give that a try when I get bored. 😉 |
Preloading a layout card above it did fix for me, but I moved everything to
the built in that I could except one that had a pretty complicated if, else
if that I need to be hierarchical.
…On Sun, Jul 21, 2024, 7:46 PM daemonenstall ***@***.***> wrote:
I stopped using state-switch card, and used the builtin contifional card,
one less Hacs for me now
I will give that a try when I get bored. 😉
—
Reply to this email directly, view it on GitHub
<#117 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHGRLNWIHQC3E2U3VMRIFYTZNRB4ZAVCNFSM6AAAAABKD5YB7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRHAYTQNBQG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I'm having a similar issue with not appearing, and it looks like this repo is no longer under active development as the last update is at least 2 years old. Has anybody tried contacting @thomasloven or any of the other people who have contributed to see if there is any active interest in going active again? Or perhaps somebody wants to fork and get that added to HACS? |
Maybe we should switch to the built in conditional card. |
If you set a default (see docs), it fixes the display issue. |
it does BUT i have since come to realize that the card still causes other issues. namely, it made the dashboard unusably slow on ios. the default workaround does make them show up right but i couldn't click anything on my phone for a good 15-20 seconds -- so i think whatever was causing the issue on the first place persists in the background even with a default option set. on my computer, it doesn't seem to be an issue, but on iphone -- everything is blocked while that issue sorts itself out over 10-20 seconds. so, sadly, i had to change all my state switch cards to the og conditional card. i liked the added functionality of state switch cards but it doesn't appear to be maintained and it's definitely not working right anymore, even with the set default bandaid. for now, unless there's an update to state switch, id recommend everyone giving default conditional options (or the other custom conditional card) a shot -- it might fix issues you didn't even realize were related. |
Yea, I must admit, switching to the build in conditional card saved me a lot of trouble. I used to run this card: Old config:
new (and imo better/easier) config:
|
System information:
lovelace-state-switch: 1.9.5 (also tried master branch)
layout-card: 2.4.5
Core 2024.7.0b5
Supervisor 2024.06.2
Operating System 12.4
Frontend 20240627.0
Since I have updated to the latest beta version of HASS, the card is not shown correctly.
The card should look like this,
but is shown like this:
When I use the visual editor, surprisingly the card is shown correctly in the right preview panel.
By playing around with the panel settings, I have noticed this:
The standard setting for the panel is "raster" and is not working. When I change the setting to "horizontal", "vertical" or "grid" (provided by layout card), the card is working properly again.
The text was updated successfully, but these errors were encountered: