I have a sensor created using the rest platform which uses GET to pull project tasks from Todoist through their API.
This particular sensor brings in all of the completed tasks for my account. In this sensor, the status is of no consequence. The attributes are what I use on my front end.
I have a simple Markdown card that uses a template to simply display all tasks that have been completed for today.
What I would like to do is keep a running total of ALL tasks ever completed, and then some other metrics by week/day, etc.
I can figure that part out.
QUESTION:
Over time, as the attributes list grows and grows, it seems unsustainable to have a sensor.tasks_completed entity with an infinitely long list of attributes.
Part 1: Is there a way to create that sensor initially to only display data based upon a date range?
Part 2: What would be a reliable method to keep a count of ALL tasks completed based upon the number of actual completed tasks in Todoist, even if the sensor is limiting results?
I suppose I could use an incremental counter to count the number of state changes to that entity, but that would also include task deletions, or “uncompleting” a task as well.
Ideas? Thanks!