-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
feat(area-card): Adding new area/room summary card #1624
Open
dmick92
wants to merge
10
commits into
piitaya:main
Choose a base branch
from
dmick92:area-card
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implement the AreaCardEditor component for managing area card configurations. This includes defining a form schema for area, appearance, and interactions, and handling configuration changes through events. The component enhances user experience by providing a structured interface for editing area card settings.
Adds the HaFormExpandableSchema interface to enhance form abilities.
Remved accidental addition of code being used as an idea.
dmick92
changed the title
feat(area-card)
feat(area-card): Adding new area/room summary card
Jan 8, 2025
@piitaya I'm having some trouble defaulting the chip content into to "none". I've set the getStubConfig for the chips but when a new chips is added it's still defaulting to "state". Any change you could shed some light one this? public static async getStubConfig(
hass: HomeAssistant
): Promise<LightChipConfig> {
const entities = Object.keys(hass.states);
const lights = entities.filter((e) => e.split(".")[0] === "light");
return {
type: `light`,
entity: lights[0],
content_info: "none",
};
} |
Never mind, realized that when the chip was being added it wasn't using the correct prefix and was using the chip card stubs. |
Updated default layout do be more inline with other cards
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added an area card with support for configurable chips.
Area card chips are a clone of the functionality provided by the Chips card. The chips in the Area card are restricted to light entities and generic entities. The card currently only supports 4 chips due to screen sizes, although could be updated to remove the restriction or add a override toggle.
Related Issue
This PR fixes or closes issue: fixes #55
Motivation and Context
The card request dates back a couple years and I wasn't happy with the need to use another library or yaml editing to achieve the desired results. Due to the GUI focused nature of Mushroom Cards rather than yaml editing, and my personal desire along with the communities to have a area/room card, this feels like a solid addition to the repo.
How Has This Been Tested
All Changes are isolated to the new card and don't affect other aspects of the code base.
Card was built and tested using the development image of hass provided by the repo.
Types of changes
Checklist