Hmā¦iām dumbā¦canāt make it workā¦ i have a second option (HACS):
i found and replaced that in www/community/button-card/button-card.js
i deleted .gz file
here iām stuckā¦if i go to resources, ābutton-cardā has url : ā/hacsfiles/button-card/button-card.jsā . if i change that into : ā/hacsfiles/button-card/button-card.js&patch=2023.03.30ā HA says button-card not found. Iām not a programmer, but i kinda donāt understand why i should change that entry since i didnāt change button-card.js nameā¦ i just altered a piece of programā¦or ?
Iām not on discord, so i canāt see thereā¦sorry
you can however add the edited file to another folder I your www, and point to that in the resources dialog?
/config/lovelace/resources and add the new resource
that error doesnāt make sense, that means the āstate machineā is loaded (because thereās no error on states) but it canāt find that single state, which in general is not possibleā¦ Are you sure you have a correct entity_id in that js template?
that erorr was only a part of itā¦ if i removed ā.stateā from template definitions it was gone, but then templates stop workingā¦
but, now i restored my test HA with my production image (i never do testing on my live HA!). Then i only replaced above āquerySelectorā line in existing button-card.js with new content. Lastly i updated to 2023.4b and now it seems that button-card works! So, it was obviously āsomethingā on my test HAā¦ sorry for that, guys!
Only error remains for decluttering card:
(EDIT: was just solved on githubā¦)
FYI: some formatting was lost when coping text.
The first revison was striked out as it would make it compatible with beta
The second one works with stable as well.
Also some cards had already been updated by their own devs to work.
EDIT: beta4 has changed things again. mwc-drawer is dead, long live ha-drawer
The code above has been updated to address that.
do you by any chance also use Kiosk-mode? we can not apply the same fix there, but I did try to replace app-drawer-layout by mwc-drawer I the resource. No such luck though, seems more is required there.
Nah.
But same quick patch wonāt work with all the cards (including Swipe Navigation) as there are more changes in frontend. It doesnāt look like a one liner fix and Iāll leave it to dev - since @NemesisREhe is active it will likely be fixed before stable release.
As you can see, additionally i am struggeling to remove the Border of the embedded Card. Because i already used some Card-Mod to remove Text from the Card, the Example Code from the Docs doesnāt work. I will take care of that Problem, after the Placement-Issue with Card-Mod is solved.
Just mentioning, if this is an easy-peasy-Thing, iād be even happier
But my Main Problem right now is Controlling the Order / Layering of Elements.
Would be awesome if you know the magic Line i couldnāt find!
Awesome! That was it. Just the z-filter i didnāt find. Didnāt think of. Works awesome!
Now i can basically nest any card inside Custom Button Card, with the Benefit to set fixed sizes, and āoverlayā any other Fields i can think of.
When I updated to 2023.4.0, all my custom button cards errored out with the ānullā warning and reading āt.configā. I then found the version 3.5 on github, updated, and on PC, it started working again, but on devices (iphones/ipads), using the HA app, the error still remains. Tried refreshing, reboots, everything I could think of, nothing helped.
You need to clear cache on mobile as well. On iOS I believe itās in the companion settings panel. On Android you need to clear caches through the Android settings page (where you have all apps listed)
But I donāt understand why everyone here jumps on 2023.4 the minute itās released. There are numerous reports in here that cards like button card, decluttering and kiosk mode are broken because of some major changes.
Just wait a few weeks till they get new releases and bugfixes of those releases and 2023.4 gets more bugfixes anyway. Running 2023.3.6 for a few weeks longer will not stop the earth from spinning.
there were numerous of updates of cards to comply with 2023.4. But, (at least on windows) you must totally clear all: in chrome or edge: press F12 (to enter developer mode), then right-click on ārefreshā icon and select āempty cache and hard refreshā. Only then it shows correctly - only CTRL+F5 doesnāt help.