Xiaomi Smart Pet Food Feeder 2 has duplicate sensors

[KVinS]

Device model / 设备型号

xiaomi.feeder.pi2001

Component version / 插件版本

1.1.4

HA core version / HA版本

2026.3.3

Integrated mode / 集成方式

Automatic (自动模式)

The problem / 问题详情

There are four sensors with the same name "eaten_food_measure" of which only one ("eaten_food_measure_3") works

Entity attributes / 实体属性

eaten_food_measure
eaten_food_measure_2
eaten_food_measure_3
eaten_food_measure_4

[github-actions]

This is a known issue with the Xiaomi Miot Auto integration where certain devices create duplicate entities for the same MIOT property. For the xiaomi.feeder.pi2001 model, the eaten_food_measure property is being mapped multiple times from different service instances (SIID/PIID combinations), resulting in four redundant sensors.

Workaround: Use Device Customization

You can suppress the duplicate sensors by adding device customizations in your configuration.yaml:

xiaomi_miot:
  device_customizes:
    xiaomi.feeder.pi2001:
      exclude_miot_properties: 
        - eaten_food_measure_2
        - eaten_food_measure_3
        - eaten_food_measure_4

Or more effectively, you can specify which properties to include as sensors:

xiaomi_miot:
  device_customizes:
    xiaomi.feeder.pi2001:
      sensor_properties: "pet_food_left_level,fault,eaten_food_measure,desiccant_left_level,desiccant_left_time"

This ensures only the intended properties are created as sensor entities.

Root Cause

The integration's built-in profile for xiaomi.feeder.pi2001 (as shown in the source code) only lists eaten_food_measure once in sensor_properties. However, the device likely reports this same property through multiple MIOT service instances, and the integration isn't properly deduplicating them during entity creation.

Recommended Action

1. Apply the workaround above to clean up your entities immediately
2. Report this as a bug to the hass-xiaomi-miot GitHub repository with your device model and entity details, so the developer can fix the built-in device profile

The working sensor (eaten_food_measure_3) is the one actually receiving updates, while the others are stale duplicates that can be safely excluded.

[github-actions]

This is a known issue where the device reports the same eaten_food_measure property from multiple services, causing the integration to create duplicate sensor entities. Only one of them (typically with the _3 suffix) actually receives updates.

Solution

You need to add custom configuration to exclude the duplicate MIoT properties. Since you're using Automatic mode, you can configure this through the UI:

Method 1: Exclude Duplicate Properties (Recommended)

1. Go to Settings → Devices & Services → Xiaomi Miot Auto
2. Click Configure
3. Select Customizing devices and entities
4. Add a new customization for your device model xiaomi.feeder.pi2001
5. Add the following custom option:
   • Key: exclude_miot_properties
   • Value: 2.5,3.5,5.5 (replace with actual SIID.PIID values from duplicate entities)

To find the correct values:

• Open the duplicate sensor entities (the ones that don't work)
• Check their attributes for siid and piid values
• The format is siid.piid (e.g., 2.5)
• Exclude all except the working one (usually 4.5 based on the _3 suffix pattern)

Method 2: Override Sensor Properties

If Method 1 is too complex, you can override which properties become sensors:

1. Follow steps 1-4 above
2. Add this custom option instead:
   • Key: sensor_properties
   • Value: pet_food_left_level,fault,desiccant_left_level,desiccant_left_time

This will prevent eaten_food_measure from being auto-created. Then manually create a template sensor using the working entity:

template:
  - sensor:
      - name: "Pet Food Eaten"
        unique_id: xiaomi_feeder_pi2001_eaten_food_measure
        state: "{{ states('sensor.xiaomi_feeder_pi2001_eaten_food_measure_3') }}"
        unit_of_measurement: "g"
        state_class: measurement

Quick Workaround

If you want an immediate fix without configuration changes:

1. Disable the three non-working sensors (eaten_food_measure, eaten_food_measure_2, eaten_food_measure_4)
2. Rename the working sensor (eaten_food_measure_3) to remove the _3 suffix
3. Use this sensor in your automations and dashboards

Root Cause

The built-in configuration for xiaomi.feeder.pi2001 includes eaten_food_measure in sensor_properties, but your device reports this property from multiple service instances (different SIIDs). The integration creates a sensor for each instance, resulting in duplicates.

Note: If you can provide the full attributes (including SIID/PIID) of the duplicate sensors, I can give you the exact exclude_miot_properties values to use.