Add a state card

[brunosabot]

Hello there!

I found your custom cards awesome and it changes the way I display my dashboard. There is however one thing missing for me: a basic state card. This can be used to display basic informations such as a room temperature, days before/since a date, a battery percentage, ... It could have been a custom button, but on this one the whole card would be colored, have default toggle action that does not really make sense and does not display the actual state value by default.

What do you think?

[Clooos]

Hi and thanks!

This is already on my todo list but I have a bigger project in mind for the (not too distant 🤞) future of Bubble Card. I’m planning to add a new card type that can be fully customized in the GUI editor to fit everyone’s needs, like a media player with buttons, a thermostat card or even a simple state card.

But for now I still have to focus on performance and stability, while the next release will introduce some nice new features and will be much faster 🥳

Edit: I did not realized that it was a pull request! I tought that it was a feature request! I will take a look a that probably monday. Thanks!

[brunosabot]

I can also dig into the performances into another PR if you don't have time right now 😁

[Clooos]

The performance issue is totally fixed on my side and this is so much faster now! I can't wait to release this new version but I still have some issues to fix first.

And finally I've tried your PR yesterday, it's a nice addition. But it could be better to add it as a new button_type don't you think? And it could be great if you could add the editor part too if it's not too much to ask 😁

Thanks a lot again for helping me!

[brunosabot]

But it could be better to add it as a new button_type don't you think?

I can change that, you tell me 😅

So you can understand why I chose that, my reasons were:

• Some default values are different (show_state, actions, ...), so i thought it would have been confusing for people
• There is a lot of code that we don't need to be executed, so it's just removed in this file
• To me these are different needs (pretty much as there is a "Entity" and a "Button" card by default in lovelace

The performance issue is totally fixed on my side

I worked for fun on this part, and I think there is an opportunity to do more. I'll share you an insight of this later. Edit: I made a pull request on my fork to explain what I did. Do not hesitate to ask questions on it!

add the editor part too if it's not too much to ask

Sure! I'll look how this works. Edit: Done!

[Clooos]

I've merged your other PR first and now there is a conflict. And I'm not sure of what to do, your help will be very appreciated 😅

[brunosabot]

No problem, I knew this would happen! 😁

I can do the fix, but what should I do with this pull request?

• I can redo this to include into the button component as you mention
• I can just resolve the conflict here and we're good to go
• I can resolve the conflict + add the performance improvements I showed you (and then start new PRs to make these improvements on the other cards, to make this one not too big)

I'll sticked to your vision and your choices for this project and then helping the most I can :D

Edit: the conflict is solved

[Clooos]

Thanks! And I really like your third option, but I guess that it could be better to add it as a new button_type, because it's still some kind of button and it shares a lot of similarities from them.

And one more time thank you! I'm really glad to finally have someone that can help me improving this huge project in the right direction!

[brunosabot]

I'm almost done with the PR adding state as a button and with the perf improvement we talked about. Is there a way I can find all the possible use cases to test them so I'm sure nothing is regressing? (I contacted you on Reddit about this, not sure where would be the right place to do so)

[Clooos]

Hi, I've answered on Reddit.

[Clooos]

Best PR in the world, thank you a lot again for this amazing and impressive work 🍻