Feeder.device_records property is not populated correctly for PetKit Fresh Element

[Jellymath]

Hi. I wanted to try using homeassistant_petkit integration with dispenser-schedule-card, however, I found out that required sensor is not populated for my feeder

I tried to investigate a bit why that's the case and found that Feeder.device_records is not filled with the required info due to unexpected endpoint response format

Here are two responses that I got today (response value from _fetch_device_data, FeederRecord data class, FEEDER device type)

1. Breakfast success, Dinner pending:

[
  {
    'amount': 60,
    'day': 20250503,
    'device_id': 0,
    'items': [
      {
        'amount': 40,
        'id': 's36000',
        'name': 'Breakfast',
        'petAmount': [
          {
            'amount': 40,
            'petId': '100112726'
          }
        ],
        'src': 1,
        'state': {
          'completedAt': '2025-05-03T08:00:10.000+0000',
          'realAmount': 40
        },
        'status': 0,
        'time': 36000
      },
      {
        'amount': 20,
        'id': 's72000',
        'name': 'Dinner',
        'petAmount': [
          {
            'amount': 40,
            'petId': '100112726'
          }
        ],
        'src': 1,
        'status': 0,
        'time': 72000
      }
    ],
    'realAmount': 40
  }
]

2. Breakfast error (the feeder is empty), Dinner pending:

[
  {
    'amount': 60,
    'day': 20250503,
    'device_id': 0,
    'items': [
      {
        'amount': 40,
        'id': 's36000',
        'name': 'Breakfast',
        'petAmount': [
          {
            'amount': 40,
            'petId': '100112727'
          }
        ],
        'src': 1,
        'state': {
          'completedAt': '2025-05-03T08:00:29.000+0000',
          'errCode': 'food-0',
          'errMsg': 'Food low.',
          'realAmount': 0
        },
        'status': 0,
        'time': 36000
      },
      {
        'amount': 20,
        'id': 's72000',
        'name': 'Dinner',
        'petAmount': [
          {
            'amount': 40,
            'petId': '100112727'
          }
        ],
        'src': 1,
        'status': 0,
        'time': 72000
      }
    ],
    'realAmount': 0
  }
]

While the structure is similar to the expected one, there are some differences:

• There is no top-level feed property, we start with an array
• device_id is in snake_case while camelCase is expected
• petAmount is not parsed (probably not necessary tho)
• errCode in state is string while int is expected
• errMsg in state is not parsed

I tried doing some quick fixes like changing _fetch_device_data to have something like:

        if device_type == FEEDER and data_class == FeederRecord:
            device_data = FeederRecord(**{'feed': response})
        elif isinstance(response, list):
            device_data = [data_class(**item) for item in response]
        elif isinstance(response, dict):
            device_data = data_class(**response)

But this fails for records with errors like the second one

Ideally it would be nice to separate endpoint response types from library model types, but it's not that easy to do without knowing other endpoint formats and the required library model. So I decided to just open the issue first :)

[Jezza34000]

Hi @Jellymath,

Indeed, this question has already been asked by another user regarding support for older feeder models. The first question I have for you is: Which model are you referring to?

I own a recent model, the D4SH YumShare Dual Hopper, and from what I've observed, newer models have different API responses compared to older ones.

My library was developed using a recent model, so older models have only "partial" support. Since I don’t have those older models, I haven’t been able to fully work on their compatibility.

However, based on my latest investigations on the subject, several modifications would be needed:

• Endpoint handling,
• Adjusting containers for data specific to those feeders,
• Modifying the get_dispense_status function (in the integration repo).

Let me know the exact model you have, and I can give you more details on what was causing issues back then.

[Jellymath]

Hi @Jezza34000

Which model are you referring to?

PetKit Fresh Element, the old one (maybe the oldest? :D)

newer models have different API responses compared to older ones.

Maybe! I attached responses for my feeder in the initial text, I believe that should be the getDeviceRecord endpoint

Endpoint handling

Yeah, I think it would be nice to have some layer where you specify the data you need and the device model and it can select the correct endpoint, and parse the response to some format that's more related to the needs of the integrations (maybe keeping original response somewhere just in case, not sure)

Modifying the get_dispense_status function (in the integration repo).

I don't see this function being used, I think get_raw_feed_plan is doing all the heavy lifting :)