#I just watched the video that d sellers1

1 messages · Page 1 of 1 (latest)

tepid vault
#

I think that's the difference between hourly and daily scheduling

silent jacinth
#

ohh jeeze

tepid vault
#

it's not immediately intuitive

#

but there's a lot of options

silent jacinth
#

so you're saying if I have a monthly, or yearly task I'd like to track, I would set it for 720 hours and 8,760 hours respectively?

tepid vault
#

if you want the next schedule based on the last execution, I guess yes

#

monthly always schedules the same day each month, and yearly the same day each year

silent jacinth
#

yes

#

but I rarely get things done when they're supposed to

#

and because of that I set imaginary due dates which act more as reminders that it's time to think about doing the task

#

I think the hours interval is a big piece of the Grocy integration I couldn't get past

#

I think the video shows how to get each task to appear on the frontend, which was the other one

#

Thank you for your help

hexed shoal
#

I started watching the video and got sidetracked working with some card_mod... In regards to the frontend, I found a grocy-chores-card. Not sure if I will use it but it could be a good reference. I think it depends on what entities and attributes are available once the add-on is installed and then working with that.

tepid vault
#

yeah that's a good card, I use that. Note you need the grocy integration as well as the grocy add-on.
Once you get those setup, you will get a sensor.grocy_tasks and a sensor.grocy_chores, and those two sensors have huge attribute blobs containing all data about all chores and tasks needed for the card.

silent jacinth
#

I know it's been a few days but I'm back to working on this and was wondering...

If you both think the grocy-chores-card is a good path to take, how would using it affect using the restAPI sensor?

silent jacinth
#

Hey @tepid vault I was wondering if you could help me out with setting this up... I'm at 8:03 of https://www.youtube.com/watch?v=n8V4ToFWT18 but I already have a handful of chores in grocy. I don't know which one I created first so I don't know what /chores/1 would be, but the first comment below says "if you use manual and write the name it will automatically be named in HA and the ID will be human readable."

How do I "use manual"??

#

When I execute the GET /objects/{entity} from the grocy REST API the response has a whole bunch of chores that I didn't setup... almost like it's just an example and not my actual data

omg 🤦‍♂️ I was looking at an example, literally the demo.grocy. You have to click on the REST API browser from your own grocy in home assistant

silent jacinth
#

I found it. I went into entities and searched for grocy, found grocy chores, clicked attributes, and found the chores listed there with their id: 1 and name: listed under it

silent jacinth
#

then go back into the yaml file and add a unique_id: line to each rest sensor

silent jacinth
#

OK, so now I'm stuck.

For whatever reason when I try to change the period type to hours (so that the due date is determined based on when the last time the chore was tracked), and the interval to 336 (for every 2 weeks after the last time), when I click to save... nothing happens