Has anyone looked at building an ESPHome display based mini-dashboard for ChoreOps?

[PedanticAvenger]

I have some esphome powered devices with screens in my kids rooms acting as environmental/presence sensors and alarm clocks. I would like to add another page to the system to display, say, top 3 chores (based on due date) for the relevant child and an ability to mark them as done. Especially for my younger, I don't want them to have to open a tablet to see their chores (and get distracted by other things) and he isn't big enough to use our wall mounted dashboard screen. This doesn't leverage the HA dashboard capabilities and I haven't dug too deeply yet so wondering if anyone has taken a stab at this yet?

[PedanticAvenger]

Maybe a static sensor on the lines of sensor.<user>_choreops_chorelist that has an attribute or a status of the specific chore IDs due that day? I'm not currently seeing a way through this without some more custom entity presentation on the HA side so I can build the list of labels and buttons to handle things.

[ccpk1]

I haven't tried to do anything with an esp like you mention, but accessing the data getting a limited list of entities like sensors and buttons is pretty straightforward.

Tell me more about what you need and what format it needs to be in and maybe I can help. Can you use a jinja template?

[PedanticAvenger]

So from the esp side I can poll defined entityIDs pretty easily, but not hosted templates, etc. From what I'm envisioning I need to start at a common fixed point and get data back to display. So on one of these devices I can pull sensor.child1_choreops_list.status and could get back a json or comma separated list of entityIDs for the chores for child1 that were due that day, then iterate through those to build labels and "done" buttons to update as the attributes and whatnot that are relevant are pretty statically defined already, for example update sensor.child1_choreops_chore_status_take_garbage_out status without other devices being involved.

[PedanticAvenger]

It's pretty small and often very interactive in nature for transactions given the smaller available processing power and possible variety of displays being used. https://esphome.io/components/sensor/homeassistant/ might help as a starting point. Also a variety of ways people would likely be interested in displaying this information on say (like I'm using) a 320x480 pixel capacitive touch display, or a e-paper touch display, etc.

[ccpk1]

If you are able to access a sensor and process json, the main dashboard helper sensor has almost everything you need to know for a particular user. i.e. sensor.kaden_choreops_ui_dashboard_helper

I put together this wiki "cookbook' about several of the patterns you can use to access common data in ChoreOps, maybe it will help point you in the right direction? https://github.com/ccpk1/ChoreOps/wiki/Tips-&-Tricks%3A-Template-Cookbook-for-Chores,-Rewards,-and-Approvals

It sounds like a cool use case and honestly one of the reasons I wanted to do this all native in Home Assistant so add data is available. Let me know if there is something specific I can assist with.

[PedanticAvenger]

Oh I hadn't seen that sensor yet. Yes, very close to what I'm looking for at first glance. I'll dig into the attribute details to make sure I understand it properly. Thanks you!