Any update on the “t.setConfig is not a function” error? I was hopeing it would have been fixed with the new grid card but im still getting it. Getting “t.setConfig is not a function” every time its in any nested card.
So it loads 100% of the time if i go into edit mode and move the tab its on either left or right then move it back. This works for about a day then something internal refreshes and I then get the error again, this also causes a annoying issue of triggering the notification that the frontend has changed and needs to refresh.
Love this card and I’m using it to swipe between two picture-elements cards for my groundfloor and first floor floorplan.
On these I have different light entities that I can control by a long-press (which calls the browser_mod service) which shows different controls.
Used this card two combine those two views into one swipe card.
However the long press on an entity on each of the picture elements cards doesn’t respond anymore.
Anyone knows how to fix this?
Hy, thank to your works.
I try it with card type: picture-entity but every picture in swipe card appear in black and white ?
How i can visualizze in color?
Has anyone figured out a way to make the swiper card switch to a specific card? I would love to have a button or UI element switch to a different card than is currently displayed (ie. card 2 out of the 3). I believe the underlying code used by the card supports it, but have no idea if anyone has figured out how to do it from lovelace.
I don’t think it’s possible, since a button would need a service call to envoke swiper card, which swiper doesn’t have. It would need to be a custom component instead of only a custom card.
But honestly, what’s the point in using swiper card if you want to use buttons or other UI elements. That defeats the whole purpose of swiping the card (it’s in the name).
You are better off using state-switch card in your case. I use that myself as well for some elements. That card allows you to switch to different cards/views and use hash and entities to envoke it. See -> https://github.com/thomasloven/lovelace-state-switch
Well, I am trying to set up a swiper card that contains three picture-elements cards that represent floors of my house. You are free to swipe between them. The picture element cards have buttons that represent going up or down stairs (among others). When they are clicked I wanted the swiper to switch to the corresponding card.
I have been playing around with this to replace three separate lovelace pages that have buttons with navigation actions. The swipe action seems like a nice way to swap pages. Oh well.
I will take a look at the lovelace-state-switch card you mentioned. That’s yet another card that I wasn’t aware of.
Thanks for taking the time to respond. I really appreciate it.
Then state-switch is definitely the way to go. I use that as well to switch between different layouts. It takes some practice and reading the docs, but once you get started it’s pretty straight forward. In your case the hash option would be best.
Make sure you create buttons with tap action that navigate to a hash url and you can switch views with a press of a button Also you can add transitions if you like an animation.
What’s there to not work? I have all kinds of cards inside a swiper card (mini graph, media player, horizontal-stack, weather card, markdown). Unless there is some bug, which you should report, it should work like all other cards.
First try the apexchart-card on it’s own. My first guess is that you have apexchart-card not setup correctly (since I use numerous advanced nested cards inside swiper card withou issues).
Thanks alot, i just learned how to build a a nested card. Never really understood it, still learning yaml. But now i understand you have to set it up according to the card config
Great! Once you get the hang of nested cards and work a lot in YAML, it get’s very easy and you see them as blocks you can just nest and build your UI with