Binary sensor entities for AI detection missing in v7.1.8 - Breaking change for automations

[galvheim]

Description

Problem Description
After upgrading to version 7.1.8, all binary_sensor entities for AI detection have disappeared from Home Assistant. Only select entities remain for configuring detection sensitivity, but there are no sensors to actually trigger automations when detection occurs.

Previous behavior (v6.1.4 and earlier):
The integration exposed binary sensors like:

binary_sensor.c325_entre_person_detection
binary_sensor.c325_entre_pet_detection
binary_sensor.c325_entre_vehicle_detection

These sensors would change state when the camera detected persons, pets, or vehicles, allowing automations to trigger.

Current behavior (v7.1.8):
Only select entities exist:

select.c325_entre_person_detection (state: "normal")
select.c325_entre_pet_detection (state: "normal")
select.c325_entre_vehicle_detection (state: "normal")

No binary sensors are exposed, making it impossible to use AI detection in automations.

Reproduction Steps

Steps to Reproduce
Upgrade Tapo Control integration to v7.1.8

Remove and re-add camera

Check Developer Tools → States

Search for binary_sensor.c325detection

No AI detection binary sensors found

Expected behavior

Expect to see sensors triggered when pet, human or vehicle is detected, but now we not even have the sensors anymore. I have done a full reinstall and adding cameras again, but it does not work.

If applicable, add error logs.

No response

Device Firmware

1.3.8

Integration Version

7.1.8

Last known working integration version

7.x

Using stream component

Yes

Does camera work via official integrations?

N/A

HASS Environment

HAOS

Search for similar issues

Yes

Additional information

Impact
This is a critical breaking change that completely breaks existing automations relying on AI detection. Users cannot:

Trigger lights only for person detection (not pets)

Create smart automations based on vehicle detection

Differentiate between motion types

Additional Information
All AI detection features work normally in the Tapo mobile app

Motion detection is enabled on camera

switch.c325_entre_trigger_alarm_on_people_detection exists and is ON

Camera streams work perfectly (camera.c325_entre_hd_stream)

All other entities load correctly except detection binary sensors

Debug Logs (Required)

There is no logs for this issue...

[markus-m2]

I only just installed the integration, and found that I needed to create Motion before those binary sensors came into existence.
Could be that the firmware update removed them, and you just need to activate a Motion event for the integration to re-add the sensors?
Try it, walk in front of the camera and hopefully those sensors will return...

[galvheim]

Tested: Yes, entities show up when triggered. But they are now stuck. So if my cat walk past or motion is triggered, they will remain as Detetcted for indefinite time. They do not clear. Now Downgraded to V7.1.0

I am in the Northsea at the moment, and I need to wait for people at home to wake up, to make them trigger them. But do I understand you correct, that they will only start exsist after first trigger? This may very well be the cause.

[JurajNyiri]

Read faq. Behaviour is well documented and this is yet another duplicate.

Instead of asking an llm to write you an issue ask it next time to search the repo for solution first.

https://chatgpt.com/share/69904a4d-84c4-8011-93d2-d5563c5d45ba

Any motion behaviour changes between versions 7.x is nonexistent because there were no changes. If entity is stuck there is an issue for it with workarounds as well and it is a camera issue.

[galvheim]

Ok. I really couldnt find this around. Also what about the stuck detections in latest version? I have downgraded to last weeks version (7.1) and detections get released. In v.7.1.8, they always gets stuck after detection. lør. 14. feb. 2026 kl. 10:43 skrev Juraj Nyíri ***@***.***>:

…

*JurajNyiri* left a comment (JurajNyiri/HomeAssistant-Tapo-Control#1199) <#1199 (comment)> Read faq. Behaviour is well documented and this is yet another duplicate. — Reply to this email directly, view it on GitHub <#1199 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7U7YJN64FTOBTITON6WRPT4L3U4RAVCNFSM6AAAAACVDVM26KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMBRGU4TAMBYGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Med vennlig hilsen, Gunnar Alvheim