Expose chores as separate entities

[iamkarlson]

Hello,
First of all, I hope this component would continue its life and will be returned to HACS!! Thanks for all of you for your work on this project!

Before trying out grocy for my chores tracking, I was using individuals input.boolean to track chores and it was very convenient to put them on a dashboard as individual entities. However, once I switched to grocy and this component, it's not possible as all the chores exposed as an attribute to just 1 entity. Would it be possible to reshape the integration and add every chore as its own entity or device?

[Raigen]

I am currently using this custom card to display various chores on my dashboard. I even have different instances per user only visible to them so everyone only sees their chores. Custom icon mapping is nice as well.
It is not exactly what you are asking for but so far the best solution for grocy chores I could find.

[arretx]

Here's how I did it:

I created sensors for each chore by creating a template that I can drop into the template editor in the dev tools. It loops through the attributes in the grocy chores and spits out a new sensor for each chore that it finds.

This is an example of a result:

  name: Chore Replace AC Filter
  resource: http://homeassistant.local:9192/api/chores/3
  method: GET
  scan_interval: 120
  value_template: >-
    {% set next_date = as_timestamp(as_timestamp(value_json.next_estimated_execution_time) | timestamp_custom('%Y-%m-%d')) | int %}
    {% set today = as_timestamp(now().strftime('%Y-%m-%d')) | int %}
    {% set due = ((today - next_date) / 86400) | int %}
    {% if due > 0 %}
      Overdue
    {% elif due == 0 %}
      Due Today
    {% elif due < 0 %}
      Not Due
    {% endif %}
  json_attributes:
    - last_tracked
    - next_estimated_execution_time
    - tracked_count
    - average_execution_frequency_hours
  headers:
    Accept: application/json
    Content-Type: application/json
    GROCY-API-KEY: !secret grocy_api

This is the template that I use to generate this result, as well as the rest of the yaml for all of the chores.

{% for chore in states.sensor.grocy_chores.attributes.chores %}{% set resource = "http://homeassistant.local:9192/api/chores/" %}{% set scan_interval = 120 %}
- platform: rest
  name: Chore {{ chore.name }}
  resource: {{resource}}{{chore.id}}
  method: GET
  scan_interval: {{scan_interval}}
  value_template: >-
    {{ "{% set next_date = as_timestamp(as_timestamp(value_json.next_estimated_execution_time) | timestamp_custom('%Y-%m-%d')) | int %}" }}
    {{ "{% set today = as_timestamp(now().strftime('%Y-%m-%d')) | int %}" }}
    {{ "{% set due = ((today - next_date) / 86400) | int %}" }}
    {{ "{% if due > 0 %}" }}
      Overdue
    {{ "{% elif due == 0 %}" }}
      Due Today
    {{ "{% elif due < 0 %}" }}
      Not Due
    {{ "{% endif %}" }}
  json_attributes:
    - last_tracked
    - next_estimated_execution_time
    - tracked_count
    - average_execution_frequency_hours
  headers:
    Accept: application/json
    Content-Type: application/json
    GROCY-API-KEY: !secret grocy_api
{% endfor %}

Once you copy the full result from your template renderer, create a grocy_chores.yaml file in your config (recommend creating folders for your integrations to organize.). The path to mine is /config/integrations/sensors/restful/grocy_chores.yaml

Any time you create a new chore in Grocy, just re-render the template and paste the new yaml into the grocy_chores.yaml file, overwriting the whole file.

There are many ways to configure your state results if you don't like my setup.

[shbatm]

I am taking a stab at this -- admittedly I hate myself a bit for not doing it by hand, but I'm testing Github Copilot's agent mode since I haven't had much time to mess with it.

Working version (with updated devcontainer and some tests added) available here: https://github.com/shbatm/grocy. I'll narrow the scope and do a PR after I get more time.

[iamkarlson]

Hey @shbatm , I actually went to the same path, and forked this repo and added to HACS as a new one. I incorporated this PR #354 which turned out to be perfect for my use case! Perhaps you can submit your changes to my fork as a new PR and I can work it out to add it, test it, and release.