binary_sensor.door_cell_motion_detection not available in version 6.0.1

[Jesus-M]

Description

The entity binary_sensor.door_cell_motion_detection is no longer available in version 6.0.1. It was in 6.0.0

Reproduction Steps

1. In a previously configured camera, go to the entity lists
2. look for binary_sensor.door_cell_motion_detection one and open the details
3. the message This entity is no longer being provided by the tapo_control integration. If the entity is no longer in use, delete it in settings. is shown and the entity is disabled.

Expected behavior

The entity should be available (or replaced by a new one)

If applicable, add error logs.

No response

Device Firmware

1.3.9 Build 231019 Rel.37378n(4555)

Integration Version

6.0.1

Using stream component

Yes

Does camera work via official integrations?

Yes

Camera has all attributes filled out in developer tools

Yes

HASS Environment

HAOS on dedicated x86 device

Search for similar issues

Yes

Additional information

Similar case to #761 but it is not that the sensor is not working, the issue here is that the entity is shown 'unavailable' and the message saying it is no longer in use.

I, anyway, followed the steps in the Readme FAQ section, with no success.

The sensor is working properly with other integration (Amazon's Alexa) and the vendor App (Tapo).

[JurajNyiri]

Read

Binary sensor for motion doesn't show up or work

under Readme FAQ.

Search for similar issues
Yes

[Jesus-M]

thanks, but ... did you read the additional information section?

I saw the issue you mention and I don't think it's the same issue.

[JurajNyiri]

I see you mentioned the ticket in Additional information, I skipped through that initially when writing above comment.

6.0.1 vs 6.0.0 has changed nothing about this, this functionality hasnt been changed in months, possibly years, just keep trying, it will come up if it did before. Cameras are not great in reporting events, especially when being hit hard by multiple services.

[JurajNyiri]

FYI;

"unavailable" with message that it is no longer provided is the exact same case as if it isn't there at all. On the first, HA just remembers that it used to be there and no longer is now.

[Jesus-M]

Will keep trying, but it was the only change. Indeed, you can see it was working until around 9:00 today, when I updated the integration from 6.0.0 to 6.0.1

[JurajNyiri]

Every time you restart HA even without integration update it will dissapear, that is normal and expected.

See #748 (reply in thread) where I explained it a bit more.