Skip to content
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

Feature request or a way to categorize items #141

Open
d3jong opened this issue Mar 17, 2023 · 1 comment
Open

Feature request or a way to categorize items #141

d3jong opened this issue Mar 17, 2023 · 1 comment

Comments

@d3jong
Copy link

d3jong commented Mar 17, 2023

Feature request, NOT a bug

Good day,

Just found out this integration. Looks very useful!

However, I would like to categorize the basic stuff, for example birthdays, weddings/jubilee, regular car checks, tax etc.
So in the case of birthdays, you do not have to write: xname's Birthday over and over again.

anniversaries:
  sensors:
 -  type: birthday: #something like this maybe?
   - name: Arnold
     date: '1900-01-01'
   - name: Henk
     date: '1900-01-01'
   - name: Joep
     date: '1900-01-01'
 - type: jubilee (wedding date) #something like this maybe?
   - name: Henk & Ingrid 
     date: '2020-12-12'
 - type: uncategorized_recurring:
   - name: Car inspection
     date: '11-29'

Maybe is the idea above something or is there already something possible like this?
Or is it just me who wants to have clean consistent yaml files 😬

@BebeMischa
Copy link

I already figured a way to do this with the possibilities we have.

When making a new anniversary, you can make your own prefix for the sensor name.

Examples:

concert:
sensor.anniversary_concert_depeche_mode

birthday:
sensor.anniversary_birthday_Annabel

wedding:
sensor.anniversary_wedding_John_and_Maria

Like this, you can filter on the prefix in most common tasks and dashboard cards. ;-)

afbeelding

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants