Separate person to person.yaml- confused

I have many automations which based on home/not home status
mostly using life360 or device tracker coming from nmap,

I want to improve the reliability by using person,
So in configuration.yaml i include person.yaml
person.yaml:

#person:
  - name: karin
    id: karin777
    device_trackers:
      - device_tracker.life360_karin
      - device_tracker.karin
      - device_tracker.mi_9t_pro
  - name: avi
    id: avi777
    device_trackers:
      - device_tracker.life360_avi
      - device_tracker.avi
      - device_tracker.vtr_l29_2

questions please:
Why in the UI->developer->entities state I see it as:


1.why does it show as avi ,avi_2 avi_3?
I would expect to see 2 entities ,avi and karin …
in UI --> entities i see them though.

2.I want to change the automation to use those person entities (once solved issue#1).
but first to group them as “family” so the logic condition would based on both ,
i.e: if both are home -> so family =home
so the automation will looks better
Current automation is working but i need to refer each one of the entities ,
second it refer only the device_tracking where in person i can get more accurate state:

 - alias: 'cam_snapshot'
   initial_state: 'on'
   trigger:
     platform: state
     entity_id: binary_sensor.camera_desc
     to: 'on'
   condition:
      condition: and
      conditions:
        - condition: state
          entity_id: device_tracker.avi
          state: 'not_home'
          for:
            minutes: 4
        - condition: state
          entity_id: device_tracker.karin 
          state: 'not_home'
          for:
            minutes: 4
   action:
     - service: camera.snapshot
       data: