[Feature Request]: Luma Bathroom history

[crbarahona]

Device model name

Luma

Device model number

PLLB001

Device type

Other

Feature name

Record Litterbox Usage Data for Pets

Describe the feature

The Petlibro Luma litter box provides history on linked pets. Recording this usage and waste type can be very useful in understanding pet behavior and assist in identifying medical conditions.

What problem does this feature solve?

Review pet bathroom usage patterns

Available to help with the feature development

• I agree to help with testing or providing relevant information for this feature request

[dennismdejong]

The Luma already has several sensors for waste management state (rubbish_full_state, clean_state, garbage_warehouse_state, weight sensors), but per-pet bathroom usage history (frequency, waste type per pet) would require fetching work records from a different API endpoint.

The current get_device_work_record API method is hardcoded for GRAIN_OUTPUT_SUCCESS events (feeder-specific). To implement bathroom history, we would need to:

1. Find the correct API endpoint/parameters for litter box usage events
2. Parse per-pet usage data from the response

If you can capture the API traffic from the Petlibro app when viewing bathroom history, please share the endpoint URLs and response formats. This would help implement the feature.

[crbarahona]

I've actually already implemented this myself and been using it over the last month.

Relevant endpoints are

/data/petCare/bathroom/history
/data/pet/potty/today

I can also submit a pull request for review.

[dennismdejong]

Great work @crbarahona! That's a really clean implementation. Would you be open to submitting a PR for this? If you share the code (even as a draft), I can help review it and get it merged. The endpoints you found (/data/petCare/bathroom/history and /data/pet/potty/today) are very useful — thanks for documenting them!

[dennismdejong]

Proposal: coordinate the Luma bathroom history PR

@crbarahona has already built this and has been using it for over a month (screenshots in this issue). The relevant endpoints are:

• /data/petCare/bathroom/history
• /data/pet/potty/today

As I noted in my earlier comment, I'd love to review and merge this. Concrete plan:

1. Ask @crbarahona to open the PR (draft is fine) — they already offered.
2. On review, make sure:
   • The existing get_device_work_record() (hardcoded to GRAIN_OUTPUT_SUCCESS for feeders) is not disturbed.
   • The new endpoint calls become separate methods in api.py (bathroom_history, potty_today).
   • Bathroom usage data is exposed as pet-level sensors, mirroring the today_fountain_drinking_* pattern from Feature/Per-Pet RFID Fountain Drinking Sensors (#92) #229.

@jjjonesjr33 — shall I nudge @crbarahona with a concrete PR checklist, or are you happy to coordinate directly?