-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add scene domain and associated tap-action #164
base: main
Are you sure you want to change the base?
Conversation
Please hold. Depending on the response of @AalianKhan at #160 (comment), we might introduce the chipscard. If so, we can apply the chipscard for activating scenes as suggested at #135 (comment). Also, I'd like to finish #157 with you first. |
@DigiLive absolutely. |
Scene entities don't require templating, so the entity-card type is a better match. Also, the entity card doesn't require a title or icon to be defined. It gets this information from hass.
* Not all scenes should be activated at once. The controller-card for this domain is now disabled by default, which makes properties `iconOn` and `iconOff` obsolete. * property `offService` is obsolete because scenes can't be turned off.
If a controller-card doesn't have cards to control entities, it has no use to add one to the view. This fix adds a check and only adds the card to the view when there are entities to control.
Since the controller card doesn't control anything, it has no use to add it to the view.
@w531t4 Please validate the current state of the branch. (Don't merge the current |
@DigiLive Bought a dog at the beginning of December, my attention has been rather occupied as of late. I apologize for leaving you hanging here. I should have some time in the next few days to close these things out. |
Resolves #135 Request 1.