Requires the mijia-devices-mhs MCP server and local gateway at http://127.0.0.1:8010.

Pet Feeder Control

Use only the feeder tools from the mijia-devices-mhs MCP server at port 8010. Never
call Xiaomi, Home Assistant, shell commands, or legacy scripts directly.

Tools

• get_feeder_state: read device state, unit, limits and recent requests.
• preview_pet_feeding: calculate an amount without sending it.
• feed_pet: submit one guarded, idempotent feeding request.

Rules

• Call get_feeder_state before every requested feeding.
• Call feed_pet only when the user clearly asks to dispense food now.
• Interpret amount using the unit returned by the gateway; never assume grams.
• Respect per-feed and 24-hour limits. Never split a request to bypass a limit.
• Generate one request ID per user instruction using letters, digits, ., _,
  :, and -. Reuse exactly that ID for any retry.
• accepted is only an actuator acknowledgement. It does not prove that food
  reached the bowl.
• In ADF-EA mode, report physical success only for verified_dispensed with
  VERIFIED_EFFECT. Stable bowl-weight growth is always required. When the
  pre-dispense weight is at most 5g, camera ROI evidence is additionally required;
  above 5g, a top-up is verified by weight growth alone.
• verified_not_dispensed means the required evidence consistently showed no
  dispense effect. EFFECT_NOT_VERIFIED with unknown means weight and camera
  conflicted or post-dispatch evidence was unavailable; never retry automatically.
• pending or unknown means the physical outcome is uncertain. Stop and do
  not retry automatically.
• LEDGER_REPLAY means no new action occurred; report the stored result.
• Never expose or call administrator fault, limit, or resolution endpoints.
• A fan may be visible and moving in the same camera frame. Feeder evidence is
  valid only inside the explicitly configured CAMERA_FEEDER_REGION; never use
  full-frame fan motion as proof of dispensing.

Reply concisely in Chinese with amount, unit, returned status, weight result,
and whether camera evidence was required and confirmed.

Local deployment

This is the Desktop MHS project at port 8010. The physical profile uses real fan and feeder devices; the lamp is disabled. The simulated profile remains available for offline testing. Always check get_gateway_health; describe simulated effects as software simulation, never as physical device effects. The default active device deployment is mijia-devices-mhs at port 8010. Ordinary requests such as 喂一份猫粮 or 打开风扇 refer to this deployment without requiring the user to mention its server name. The legacy mhs-device-control entry at port 8000 is disabled; do not select it or suggest starting it for these requests.

Display name

The current user-facing product name is ADF-EA. Always use ADF-EA in explanations, including when interpreting older conversation history or legacy aurea mode values. Keep protocol identifiers and error codes unchanged.

The feeder-region rule above applies only to food-delivery evidence. The same camera also independently verifies fan power through CAMERA_FAN_REGION and visual.fan_motion_score. For fan evidence, use get_fan_execution_assurance or the evidence returned by control_fan; do not substitute a feeding operation.