Unifi package_detected sensors disappeared with 2026.7.0

junktrunk202 · July 2, 2026, 12:28am

I know the Unifi Protect package detection has been broken for a while in the Unifi firmware, but today following the 2026.7.0 installation, now the package_detected binary sensors also disappeared. I only know this because spook alerted me to invalid automations. All the other binary sensors for this camera are still present from what I can tell. I did double check that the sensor is not one of the disabled entities, and that "person detection" (the toggle) is still turned on. I can't see anything in the release notes that would point to this being a platform change. Any ideas? I don't really want to delete this automation, as I am foolishly holding out hopes that Unifi will one day decide to fix their broken AI for package detection, given that it is a core selling point of their doorbells...

NathanCu · July 2, 2026, 1:07am

Yes I noted the same did you open a bug?

junktrunk202 · July 2, 2026, 7:37pm

I had not previously but did so just now, good call. Maybe give it a subscribe:

github.com/home-assistant/core

Unifi Protect package_detected sensors disappeared with 2026.7.0

opened 07:36PM - 02 Jul 26 UTC

pjdubya

integration: unifiprotect

### The problem Unifi Protect exposes birary_sensor entities for Unifi cameras …supporting package detection like the G4 Doorbell camera. When the corresponding package_detection attribute is enabled, this will set the package_detection binary_sensor to true when package is detected and false otherwise. Until 2026.7.0, this entity was available for such cameras via the Protect integration. After the update, that entity disappeared. I only noticed it because spook notified me after the update that some of my automations were referring to an unknown entity. All other binary_sensor entities for this camera, and all other camera functions, appear to be working as they did prior to the updasshte; it's only the package_detection that I'm noticing has gone missing. I did check that it's not in the disabled set, and it's just not there anymore. If I remember right, it was originally disabled by default (since not everyone probably cares about this feature) and upon first setting up the integration you have to go enable it, so I would have done that long ago. ### What version of Home Assistant Core has the issue? 2026.7.0 ### What was the last working version of Home Assistant Core? 2026.6.6 ### What type of installation are you running? Home Assistant Container ### Integration causing the issue Unifi Protect ### Link to integration documentation on our website https://www.home-assistant.io/integrations/unifiprotect/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_

NathanCu · July 2, 2026, 7:42pm

Piled on with my version data

junktrunk202 · July 2, 2026, 7:53pm

Is it possible we're the only 2 people trying to use this functionality? Hahah.

NathanCu · July 2, 2026, 8:06pm

Doubtful. But very few go look.

esand · July 3, 2026, 10:42am

Do you have disabled sensors? I don't have Protect, but did a quick search and noticed changes related to package detection: Fix UniFi Protect package detection via public events websocket by RaHehl · Pull Request #173733 · home-assistant/core. It mentions a disabled by default sensor.

It might also be that the sensor was replaced and this is already in 2026.7. The proposed changes for that PR mentions that the detection stopped working due to upstream changes from Ubiquiti.