Your Devices and Entities

Your Devices and Entities

After signing in, each feeder shows up as one device in Home Assistant. To find it, go to Settings, then Devices & Services, open Philips Pet Series and click through to the device. Everything below hangs off that page.

Entity names are prefixed with whatever you called the feeder in the Philips app, so if yours is called "Kitchen" you will see "Kitchen Feed", "Kitchen Camera" and so on. The examples here use <feeder> in place of that name.

Feeding

Entity	What it is
button.<feeder>_feed	Dispense food now, using the portion set below
number.<feeder>_feed_num	How many portions the feed button dispenses
number.<feeder>_automatic_feed_portions	Portion size used by the feeder's own schedule
sensor.<feeder>_next_meal	Time of the next scheduled meal
calendar.<feeder>_meals	The whole meal schedule as a calendar

A portion is the feeder's own unit, roughly one turn of the dispenser. What that weighs depends on your kibble, so weigh one portion once and you will know what the numbers mean for your cat.

More on this on Feeding and Meal Schedules.

Camera

Entity	What it is
camera.<feeder>_camera	Live video and audio
image.<feeder>_last_motion_snapshot	The most recent motion snapshot
sensor.<feeder>_last_motion_snapshot_metadata	When that snapshot was taken and why
sensor.<feeder>_camera_orientation	How the picture is currently rotated

The snapshot image is cheap and always available, so it is the better thing to put on a dashboard you leave open all day. Use the live camera when you actually want to look. See The Camera.

Camera and device settings

Entity	What it does
switch.<feeder>_privacy_mode	Turns the camera off entirely
switch.<feeder>_motion_alarm	Motion detection on or off
switch.<feeder>_recorded_image_flip	Flips the picture, for a feeder mounted upside down
switch.<feeder>_video_osd	The timestamp overlay on the video
switch.<feeder>_pre_feed_snapshot	Take a picture just before each meal
select.<feeder>_motion_sensitivity	How twitchy motion detection is
select.<feeder>_nightvision	Night vision mode
select.<feeder>_anti_flicker	Fixes banding under some lights, 50Hz or 60Hz
number.<feeder>_device_volume	Speaker volume

If motion alerts are firing all day, drop the sensitivity a step before doing anything more drastic. It usually does the job.

Status

Entity	What it tells you
binary_sensor.<feeder>_device_connectivity	Whether the feeder is reachable
binary_sensor.<feeder>_tuya_cloud_connected	Whether the cloud link is up
binary_sensor.<feeder>_on_local_network	Whether the feeder is on your own network
binary_sensor.<feeder>_food_level_low	The hopper is getting empty
binary_sensor.<feeder>_food_outlet_stuck	Food is jammed in the outlet
binary_sensor.<feeder>_filter_replacement_due	Time to change the filter
binary_sensor.<feeder>_scheduled_feeding	Whether the feeder's schedule is enabled
sensor.<feeder>_food_weight	Reported food weight
sensor.<feeder>_feed_abnormal_status	The feeder's own fault code
sensor.<feeder>_lan_address	The feeder's IP address on your network
sensor.<feeder>_wifi_firmware_version	Firmware version

The two worth an automation are food level low and food outlet stuck. A jam means the cat is not being fed and nothing will tell you unless you ask it to. There is a ready-made example on Automation Ideas.

Events

Events are separate from sensors. A sensor tells you the current state; an event fires the moment something happens and is the right trigger for automations that should react once, immediately.

Entity	Fires when
event.<feeder>_motion_detected	The camera sees movement
event.<feeder>_meal_dispensed	Food has just been dispensed
event.<feeder>_meal_upcoming	A scheduled meal is about to happen
event.<feeder>_food_level_low	The feeder reports low food
event.<feeder>_food_outlet_stuck	A jam is reported
event.<feeder>_filter_replacement_due	The filter reminder trips
event.<feeder>_device_online	The feeder comes back
event.<feeder>_device_offline	The feeder drops off

Trigger on the event entity when you want a notification the moment something happens. Use the binary sensor when you want to check a condition, for instance "only if food is currently low".

A note on entities marked unavailable

If you have been running the integration since an early version, you may see a handful of leftover entities stuck at Unavailable, often duplicates of ones that work. Those are from an older naming scheme and are safe to delete: open the entity, click the cog, and choose delete. New installs will not have them.

Next

Feeding and Meal Schedules.