Lighting

Tapo: Cameras Control

JurajNyiri/HomeAssistant-Tapo-Control · v7.2.12

HACSConnection not stated

Control for Tapo cameras as a Home Assistant component

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

Entity	Shows up as	Note
`light`	Light
`switch`	Switch or outlet
`camera`	Camera	Needs its own HomeKit Bridge in accessory mode
`binary_sensor`	Sensor (motion, contact, leak, smoke…)
`sensor`	Sensor (temperature, humidity, air quality…)
`button`	Button (as a switch)
`select`	Mode picker (as switches)

What people report

Most Tapo cameras work locally with an admin plus cloud-password setup and third-party compatibility enabled. Firmware updates sometimes break credentials or controls, and doorbell press entities are patchy.

Works4
Partly works5
Won’t be supported1

Device	In Home Assistant	What they said	Source
Tapo C206	Works	Use admin with cloud password; resolved after setup Saved copy Description Unable to connect to Tapo: Cameras Control controller: PyTapo KLAP Error #3: ('Device connection error: XXX.XXX.XXX.XXX: Server disconnected', ServerDisconnectedError('Server disconnected')) ### Reproduction Steps 1. Install Tapo: Cameras Control integration (version 7.1.3) via HACS. 2. Go to Settings → Devices & Services → Add Integration. 3. Select "Tapo: Cameras Control". 4. Enter Tapo account email and password. 5. Enter camera IP address (192.168.0.121). 6. Complete setup. 7. Integration attempts to connect. 8. Error appears: PyTapo KLAP Error #3: ('Device connection error: … Excerpt saved from GitHub on 2026-10-23.	Issue #1189 · 2026-02
Tapo C520WS	Works	Manual alarm buttons vanished on firmware 1.2.6; fixed after report Saved copy I can confirm the same issue with my C520WS camera. My setup: - Camera: Tapo C520WS - Firmware: 1.2.6 Build 260628 rel (slightly different build than OP's 260528) - Integration: 7.1.17 - Home Assistant: HAOS 2026.6.3 The "Manual Alarm Start" and "Manual Alarm Stop" buttons are completely missing from the entity list. However, the manual alarm works perfectly fine in the official Tapo app, so the hardware supports this feature. I also noticed that the C510 model still has these buttons available with the same integration version. This seems to be a C520WS-specific issue, possibly related to … Excerpt saved from GitHub on 2026-10-23.	Issue #1347 · 2026-06
Tapo cameras	Works Local	No cloud subscription needed; integrates well, all local Saved copy I just got some Tapo cameras. No cloud subscription required. Don’t put an SD card in it and it won’t persistently record anything. Cheap, integrates well via the HACS Tapo: Cameras Control integration. All local. Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23.	Reddit comment · 2026-03
Tapo D230 doorbell	Works	Firmware update detection fixed for new format Saved copy My D230 just got a firmware update, the quick response list looks different. Therefore suggesting to implement this change, to check for the correct format. Looks like the C520WS also has the "new" format, even though the feature is not supported there: https://github.com/JurajNyiri/pytapo/pull/133#issuecomment-2586716629 Excerpt saved from GitHub on 2026-10-23.	PR #827 · 2025-01
Tapo C200	Partly works	Cloud password with special characters reported failing; owner could not reproduce Saved copy … to do with integration or symbols in password. It should not matter as long as firmware is 2023+, but noting down the camera tested for completeness: C200 Firmware: 1.3.15 Build 240715 Rel.43073n(4555) Hardware: 3.0 Excerpt saved from GitHub on 2026-10-23.	Issue #960 · 2025-05
Tapo C320WS	Partly works	Spotlight intensity cap and invalid siren controls; fix PR unmerged Saved copy Summary Two small, C320WS-focused fixes that avoid broken controls and invalid slider ranges. Both are backed by existing upstream reports (#979, #373, #678, discussion #978). - Spotlight intensity: Some C320WS firmwares report `smartwtl_digital_level` as 100 (or similar) while the camera rejects any value above 5 with `-40101`. The Tapo app only exposes 1–5 for this model. Cap `TapoSpotlightIntensity` max at 5 when `device_model` starts with `C320WS`. - Manual siren / alarm buttons: C320WS has no API to trigger the siren on demand (`startManualAlarm`, `setSirenStatus`, and `testUsrDefAudio` … Excerpt saved from GitHub on 2026-10-23.	PR #1364 · 2026-07
Tapo C560WS	Partly works	Direct MJPEG stream stops on 4K HEVC; fix PR closed Saved copy Fix: Direct MJPEG stream stops after few seconds on HEVC cameras #1125 Cameras like the C560WS (4K HEVC) send periodic IDR resets that cause PTS to go non-monotonic. The -vsync 0 flag passed timestamps through unchanged, causing the mjpeg encoder to reject frames with Invalid pts <= last. Removing it lets ffmpeg handle timestamps automatically. Also increased probesize (32→50000) and analyzeduration (0→1000000) as the original values were insufficient for HEVC stream detection, causing immediate stream failure. Tested on C560WS (3840x2160 HEVC 25fps HD + 1280x720 H.264 50fps SD). No tested on … Excerpt saved from GitHub on 2026-10-23.	PR #1279 · 2026-05
Tapo D230S1 doorbell	Partly works	No doorbell press entity on 7.0.10 Saved copy Also cannot see a doorbell press entity. All the 'old' doorbell entities are still there though. Running 7.0.10 on HA Container 2025.11.3 ### Mandatory information: I own doorbell device type: D230S1 - [x] I have a doorbell that works with HUB - [ ] I have a doorbell that works without HUB - [ ] I tested solution from @AriaGen and it worked - [ ] I see log DEBUG (MainThread) [custom_components.tapo_control] TapoUdpMonitor started on UDP port 20005 for device IP ... - [x] I tested solution in branch udp_monitor and it worked ### Home Assistant environment OS / Docker ... Excerpt saved from GitHub on 2026-10-23.	Discussion #1116 · 2025-11
Tapo D235 doorbell	Partly works	No doorbell press entity on 7.0.10, firmware 1.2.1 Saved copy Running 7.0.10 on a D235 but I cannot see a doorbell press entity anywhere? ### Mandatory information: I own doorbell device type: ...D235, 1.2.1 firmware - [ ] I have a doorbell that works with HUB - [x] I have a doorbell that works without HUB - [ ] I tested solution from @AriaGen and it worked - [x] I see log DEBUG (MainThread) [custom_components.tapo_control] TapoUdpMonitor started on UDP port 20005 for device IP ... - [ ] I tested solution in branch udp_monitor and it worked ### Home Assistant environment HAOS 2025.11.3 ### Any additional observations Excerpt saved from GitHub on 2026-10-23.	Discussion #1116 · 2025-11
Tapo C420S2	Won’t be supported	Marked as not supported camera Saved copy See https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues/243 Excerpt saved from GitHub on 2026-10-23.	PR #244 · 2022-10

Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.

How it connects

Connection not stated

The integration doesn’t declare how it connects.

Its README mentions local or LAN control.

Found automatically over

DHCP

Details

Installs (analytics)	17,352 (2.45%)
GitHub stars	2,029
Latest version	7.2.12 (2026-10-23)
Set up in the UI	Yes
Maintainers	@JurajNyiri
License	Apache-2.0

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.

Sources

Documentation: https://github.com/JurajNyiri/HomeAssistant-Tapo-Control
Source code: https://github.com/JurajNyiri/HomeAssistant-Tapo-Control
Issues: https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues
HACS: https://hacs.xyz