Yep, that’s exactly how I feel as well
1 Like
well, ofc you’re free to copy anything you like, but my advice would really be to actually finally start understanding the things that are happening.
In the end, it is as simple as saving the backend file somewhere in your backend configuration and the frontend files in your Dashboard setup.
the rest is automatic. (so any instruction to ‘run’ your automations is just silly, because that is what automations do)
put this way, the user has 2 things to do:
- decide what the Dashboard should look like (which selectors you want, how you want to show a scene etc etc)
- understand how to realize and organize that using the available source material and HA functionality. Frontend and Backend.
copying anyones, mine or Matt’s, configuration blindly wont help you achieve that. as I suggested before: start with the templating, and understand what that does. Ive tried to document the whole development from the first template I made atop, to the later changes that became possible with HA templating developments and card evolutions.
Templating is the crux of this card, because that is not only used in backend, but here, brought to the Frontend by means of the auto-entities card.
Keep up with the HA developments: I’ve moved all of my helpers to the UI, which allows for in UI editing and is safer in the end. less yaml, more secure and robust.
as a matter of fact, only last week have I changed my templates to incorporate new developments.
I hope you get what you want, but keep in mind: HA changes constantly, you need to grasp what that means for (y)our configs, or you wont be able to keep it working long term.
Well said.
I’d also add that each use case is different, so what works well in one installation may be unnecessary or not work at all on the next.
For example, lighting automation isn’t important to me. Eye candy and touch friendliness are.
Sure, the slider card might be problematic, but it works great for my narrow use case.
And you’re right; after diving into the templates, I quickly realized that I didn’t really need any of the automation stuff.
Doesn’t mean I’m any less appreciative of your code leading me down the right path 
From what I can tell, a big part of what makes the HA project such a success is how the HA community can build upon one another’s accomplishments.
2 Likes
Hi all, quick question before I embark on trying to get this to work. Will HA ‘remember’ which scene is the active scene or just activate the scene using this method? I have a current workaround with binary_sensors tracking xy colours. This is working well to highlight the ‘active’ scene at the moment. If this solution will enable the tracking of which scene is pressed and is active, then I would swap over. Apologies if this is obvious, I just don’t have much time to delve deeper right now. thanks in advance for any help you might be able to offer.
not sure what you mean with ‘remember’, but yes, it does indicate the active scenes on lights/groups like this.
Note I also added the NU scening card, which I suppose might be even closer to what you are looking for?
- type: custom:auto-entities
card:
type: entities
title: Nu scening
show_empty: false
filter:
include:
- attributes:
dynamics: dynamic_palette
Hallo ihr Lieben,
Ich selbst bin noch nicht lange bei der Home Assistant dabei und habe in einigen Sachen Probleme oder auch das zu Verstehen.
Danke für die Arbeit @matthonig
Das ganze mit den HueSzenen ist genau das was ich gesucht habe. Ich bin genau jeden Schritt nachgegangen aber es gibt aktuell 2 Sachen die ich nicht verstehe. In der Anleitung unter Punkt “4. Gehen Sie zu Einstellungen → Automatisierungen und führen Sie die beiden Automatisierungen aus, um die Front-End-Listen zu füllen.” Kann das einer für mich konkret erklären? Wenn ich bei Automation bin, kann ich eine neue Automation erstellen, und dann?
- Wenn ich im Dashboard eine Karte erstelle mit “manuell” und ich den Code einkopiere bekomme ich den Fehler, siehe Bild. Obwohl ich Gruppen habe.
Ich weis nicht ob es wichtig ist welche Version der Home Assitant hat, ich habe die aktuelle von Oktober 2024,
Danke im voraus und für die Geduld
in English please, thanks.
those red errors can mean 2 things:
you need to install custom card fold-entity-row
you need to create a helper input_select.hue_group