Your camera's wrong password error can be three defaults deep

Описание и применение

Два камеры Tapo C210 отказались от правильного пароля из‑за трёх скрытых дефолтов: отключённого переключателя совместимости, неверного имени пользователя в интеграции Home Assistant и некорректных правил AdGuard. Исправление включения переключателя, корректных учётных данных и очистка правил AdGuard восстановили работу камер и предотвратили 70‑минутный сбой.

Задача

Two Tapo C210 cameras on a home network rejected the correct password, causing a temporary suspension and a 70‑minute service outage.

Результат

Enabling the Third‑Party Compatibility toggle, correcting Home Assistant credentials, cleaning AdGuard rules, and reducing container memory usage restored camera authentication, automated workflows, and prevented a 70‑minute outage.

Рабочий процесс

• 1. Identify the "Third‑Party Compatibility" toggle in the Tapo app and enable it.
• 2. In Home Assistant, use the camera’s TP‑Link account email as username, set "skip_rtsp" to true, and leave the cloud password empty.
• 3. Clean AdGuard user_rules by removing invalid lines, keeping 65 valid rules, and restart the container.
• 4. Verify DNS blocks for TP‑Link domains and confirm cameras are DNS‑quiet.
• 5. Adjust Frigate and other containers to reduce memory usage (720p stream, 5 fps detection, 3 GB memory cap).
• 6. Test PTZ, automations, and recordings to ensure functionality.

Доказательства

With it off, the camera's control API rejects every credential, the correct password included.

Источник

Home Assistant's Tapo integration ships cloud setup steps that hardcode the username as "admin".

Источник

My AdGuard user_rules section had python-source garbage sitting in it, leftover lines from an earlier quoting crash.

Источник

The box runs 7 GB total RAM, with ~1.7 GB of that already in swap even at idle.

Источник