Triggers per household instead of per device

Triggers per household instead of per device

Triggers per household instead of per device
Triggers per household instead of per device
Thursday
Model: Tapo C530WS  
Hardware Version:
Firmware Version: 1.3.3

Hi !

 

You have a strong and affordable camera ecosystem, but there is a major limitation that makes it difficult to use in real households as far as it hink.
we have multiple cameras integrated with a home base H500, plutgs & lights.

 

Currently, automations are triggered per device (phone), not per household.

This creates a serious issue:

 

Use case:

 

  • 2 people living in the same home

  • One person leaves → camera turns ON

  • The other person is still home → gets recorded unintentionally

  • another scenario when the shared user gets home and recorded all the time instead of being able to have 2 or more admins if preferred.

This is a privacy issue and makes the automation unreliable.

 

Expected behavior:

  • Camera should only turn ON when ALL registered users are away(if requested)

  • Camera should turn OFF when ANY user arrives home (if requested)

 

 

Why this matters:

  • Most households have multiple occupants

  • Current setup forces manual actions

  • Competitors already support household-based presence detection

 

 

is this Feature request already taken into account?

  • Multi-user presence detection

  • “ALL users away” logic

  • Household-based Home/Away mode

 

This would significantly improve usability and trust in the product.

 

if it's already availble in settings i would be happy to learn how to 

thanks for informing me,

 

BR
Mryn

  0      
  0      
#1
Options
1 Reply
Re:Triggers per household instead of per device
Friday

  @Mryn 

Hi,
Thank you very much for your feedback and feature request. It's recommended to vote and leave your use case/request in the thread "Geofencing for multiple people?". We will log it and forward it to the relevant team for evaluation.
Best Regards

  0  
  0  
#2
Options