V7.1.8 Binary Sensors triggered, then stuck on C500, C310 and C325CW

[galvheim]

Description

This is not a duplicate. After upgrading to V7.1.8 yesterday all detection of pets, motion, vehicles etc. get stuck on detected. This cannot be a camera-issue since they have not been upgraded lately, nor have I done any modifications to them for 1.5 week at least. And when downgrading to V7.1.0 it works fine again. This is for C325CW, C500, and all my C310. Overnight - after upgrade, restart and nothing more.

Searched and found some old post. Solutions in thes are unresolved and asking user to contact TP-link. I not see how this is a duplicate, since this is a new thing on many cameras on this exact version. If this is a HA-problem, why does V7.1 work fine on latest HAOS?

Reproduction Steps

1. Just as mentioned.

Expected behavior

Expect them to realease when they are released in App as they did before.

If applicable, add error logs.

No response

Device Firmware

1.3.8 Build 250811 Rel.67225n

Integration Version

7.1.8

Last known working integration version

7.1

Using stream component

Yes

Does camera work via official integrations?

N/A

HASS Environment

HAOS

Search for similar issues

Yes

Additional information

No response

Debug Logs (Required)

--

[JurajNyiri]

I am closing this issue due to:

1. No debug logs provided, these are required. Debug logs also were not provided in a duplicate ticket that was opened couple hours ago Binary sensor entities for AI detection missing in v7.1.8 - Breaking change for automations #1199
2. No test via core integration "Does camera work via official integrations?", same as in the previous issue you opened
3. As I described previously in the issue: Any motion behavior 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.

Specifically these are the changes between 7.1.0 and 7.1.8:

• 7.1.0...7.1.8 no changes to binary sensor
• JurajNyiri/pytapo@3.4.5...3.4.11 - pytapo not being used for binary sensor (motions) at all

4. Incorrectly filled out Last known working integration version, there was no version 7.1.
5. Both tickets lack steps that you took in order to attempt to resolve the issue as described in FAQ Binary sensor for motion doesn't show up or work
6. If it was an integration issue, you would need to provide a specific version that broke the update, not a range of 8 versions.
7. This ticket is another duplicate. If the motion sensor gets stuck, this is clearly documented in Feature Request: Add multiple events detections #304 and other duplicate issues that were opened and is a camera, or network issue. If the required debug logs were provided, we would see that camera did not send an event.

Opening another duplicate issue and/or continuing to break GitHub and this repository etiquette will result in permanent block of your account with no further explanations.