Bug: Integration throws error on update when entity is disabled

Describe the bug I get thousands of these log entries in a few hours.

To Reproduce I just added the camera through integrations page.

Expected behavior No error in log 😉

Log If applicable, add error logs.

Logger: custom_components.tapo_control
Source: helpers/entity.py:438
Integration: Tapo: Cameras Control (documentation, issues)
First occurred: 19:26:54 (1094 occurrences)
Last logged: 22:48:07
Unexpected error fetching Tapo resource status data:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 143, in async_refresh
    self.data = await self._async_update_data()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 131, in _async_update_data
    return await self.update_method()
  File "/config/custom_components/tapo_control/__init__.py", line 68, in async_update_data
    entity.async_schedule_update_ha_state(True)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 438, in async_schedule_update_ha_state
    assert self.hass is not None
AssertionError

Camera (please complete the following information):

• Device Model: C200
• FW: 1.0.14 Build 200720 Rel.38552n(4555)

Using stream component yes i think so

Camera works through onvif component OR different cameras work in general yes i think so

Camera has all attributes filled out properly in developer tools yes i think so

HASS Environment Home Assistant Container in Debian VM Version 0.116.2

Additional context Currently added the camera in a picture-glance card.

[JurajNyiri]

Will be fixed in 2.2.

[JurajNyiri]

Yeah that makes perfect sense, it explains why Entity wouldn’t have hass. Even though we actually try to create it. It would throw that error message on the entity you disabled. I will take a look and try to fix this when I have some time later 👍