C520WS v1 and v2 mixed deployments with Alexa
Currently have three Tapo C520WS V1 cameras (firmware 1.3.4) and one C520WS V2 (firmware 1.2.4), all integrated with Alexa.
It appears that the V2 model reports event types differently to Alexa compared to the V1 units. Since adding the V2 camera, I’ve noticed inconsistent behavior:
If i switch on the person detection notification on alexa for the V2 camera
The V1 cameras trigger duplicate Alexa announcements for a single event
From what I can tell, this may be related to how event types are exposed to Alexa between hardware versions.
Are you aware of this behaviour or a known issue with mixed V1 and V2 deployments?
And is there a firmware update or fix planned to standardise event handling across versions?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
I did some testing again and found a solution. Previously, I had tried unlinking Tapo and Alexa multiple times without success.
The only change I noticed was that I had added the C520WS V2 after initially installing the C520WS V1 cameras last year.
Here’s what worked: I completely removed a C520WS V1 camera from Alexa and then unlinked Tapo and Alexa. When Alexa re-discovered the C520WS V1 camera, it started behaving like the C520WS V2—announcing events only once. I repeated this process for all the V1 cameras, and now everything is working 100%.
I believe there were some changes late last year in how Alexa and Tapo exchange camera events, hence the additional "Camera Events" tab. For some reason, the V1 cameras didn’t accept these changes automatically—they had to be completely deleted and re-discovered.
- Copy Link
- Report Inappropriate Content
Hello,
Thank you for your detailed feedback and for raising this with the community.
We’ve confirmed that this behavior is related to a update on the Alexa side affecting how camera events are handled. After this update, cameras may need to be re‑discovered in Alexa (for example, by using the “discover devices” voice command or by unlinking and re‑linking Tapo with Alexa) so that their event handling is refreshed correctly.
If this step is not completed, notification issues such as duplicate announcements may occur. We recommend re‑discovering the affected cameras in Alexa to resolve the issue.
Thank you again for your patience and for sharing your observations.
Best Regards
- Copy Link
- Report Inappropriate Content
Hello,
Thank you for your detailed post, and welcome to the community.
First, we’d like to clarify an important point: there is no functional difference in how the Tapo C520WS V1 and V2 report events to Alexa. Under normal conditions, both hardware versions should expose event information to Alexa in a consistent manner.
To help us better understand the root cause, we kindly ask you to confirm and assist with the following:
1. Alexa routines and settings
Please provide the details of your routines and review the Alexa routines and notification settings associated with each camera. We’d like to confirm whether any routines may be overlapping or reacting to multiple event types, which could result in duplicate announcements.
2. Tapo app notification behavior
Could you please check whether the Tapo app itself only receives a single person‑detection notification for the same event? This will help determine whether the duplication originates from the camera/app side or specifically within Alexa’s handling
3. If convenient, please help collect:
- The original person‑detection video clip as shown in the Tapo app
- A short video recording capturing the Alexa voice announcements occurring for that same event
These materials will help us correlate the event timing and behavior.
Once we have this information, we’ll be in a better position to evaluate whether this is related to a configuration interaction, an Alexa routine behavior,
Best Regards
- Copy Link
- Report Inappropriate Content
Hi,
Thank you for your prompt response. Please find the requested information below:
1. Alexa Routines and Settings
I do have other routines configured (e.g., for switching on outdoor lights). However, for person detection, I am currently using the default Alexa notification method.
Screenshots of all relevant settings have been included in the attached ZIP file.
2. Tapo App Notification Behaviour
Upon reviewing the event logs in the Tapo app, only a single person detection event is recorded.
Screenshots of the events have been included in the attached ZIP file
3. Additional Information Provided
I have uploaded both audio clips to the ZIP file:
- V1 camera: two notifications
- V2 camera: one notification
It can also be noted that the duplicate notification from the V1 camera differs slightly in audio, indicating they are being triggered separately.
Findings
If the cameras are removed from the “Camera Events” settings page and only the “Person Detection Announcements” toggle is enabled (on the main page), the V1 cameras announce only once on Alexa. However, in this configuration, the V2 camera does not generate any announcements.
Removed the ZIP File - due to solution below
- Copy Link
- Report Inappropriate Content
Hi,
I did some testing again and found a solution. Previously, I had tried unlinking Tapo and Alexa multiple times without success.
The only change I noticed was that I had added the C520WS V2 after initially installing the C520WS V1 cameras last year.
Here’s what worked: I completely removed a C520WS V1 camera from Alexa and then unlinked Tapo and Alexa. When Alexa re-discovered the C520WS V1 camera, it started behaving like the C520WS V2—announcing events only once. I repeated this process for all the V1 cameras, and now everything is working 100%.
I believe there were some changes late last year in how Alexa and Tapo exchange camera events, hence the additional "Camera Events" tab. For some reason, the V1 cameras didn’t accept these changes automatically—they had to be completely deleted and re-discovered.
- Copy Link
- Report Inappropriate Content
Antonhdutoit wrote
Hi,
I did some testing again and found a solution. Previously, I had tried unlinking Tapo and Alexa multiple times without success.
The only change I noticed was that I had added the C520WS V2 after initially installing the C520WS V1 cameras last year.
Here’s what worked: I completely removed a C520WS V1 camera from Alexa and then unlinked Tapo and Alexa. When Alexa re-discovered the C520WS V1 camera, it started behaving like the C520WS V2—announcing events only once. I repeated this process for all the V1 cameras, and now everything is working 100%.
I believe there were some changes late last year in how Alexa and Tapo exchange camera events, hence the additional "Camera Events" tab. For some reason, the V1 cameras didn’t accept these changes automatically—they had to be completely deleted and re-discovered.
Hello,
Thank you very much for sharing this detailed update and for taking the time to explain the steps that resolved the issue. We truly appreciate your thorough testing and clear description of the solution. Your findings are very helpful. We will review and verify this behavior internally.Thank you again for following up and for contributing such a well‑documented solution to the community. If you notice anything further or have additional observations, please feel free to share them with us.
Best Regards
- Copy Link
- Report Inappropriate Content
Hello,
Thank you for your detailed feedback and for raising this with the community.
We’ve confirmed that this behavior is related to a update on the Alexa side affecting how camera events are handled. After this update, cameras may need to be re‑discovered in Alexa (for example, by using the “discover devices” voice command or by unlinking and re‑linking Tapo with Alexa) so that their event handling is refreshed correctly.
If this step is not completed, notification issues such as duplicate announcements may occur. We recommend re‑discovering the affected cameras in Alexa to resolve the issue.
Thank you again for your patience and for sharing your observations.
Best Regards
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 146
Replies: 5
Voters 0
No one has voted for it yet.
