Toggling a person in zone, without devices

I have a couple of people who visit every now and then, but don’t have devices in our HA setup; and depending if they are around etc, I want automations to handle things accordingly.
Is there a way to have a person’s presence controlled by anything other than a device? Ideally, there’d be a button updating an entity state/helper that we press when the person is at home, then when they leave, we toggle is off.

Thanks

To clarify… Do you just want to add one to the value of zone.home? Or is it something more complicated?

Create an automation that responds to either an input boolean or a button helper (or a button) that uses the device tracker see action with home or not_home as appropriate

I have a ‘guest’ user and an input boolean when I want ‘guest more on’ flip the switch. It pops device tracker.see - home for that guest person and suddenly the house has a virtual guest.

All my automation sees a guest in the house

How about an NFC tag that your guests can scan when they enter to let Home Assistant know they are there?

If they have a phone, Bermuda will identify it without it having to be registered anywhere else in HA.

2 Likes

Nott unless it is set to act as a ibeacon, and for me that worked with varying success. Or do you know a way to identify a phone without HA acting as iBeacon?

There’s a guide to getting the IRK here:

1 Like

I won’t be asking my guests to pair their phone any time soon :grinning:
Would be nice if the code to get the IRK is added to esphome at some point.

2 Likes

I tried this and it didn’t work.

I am trying to use a boolean to indicate a specific person is ‘home’. The automation requires a mac address for them. They do not have a device to track.

Any suggestions?

The action Nathan recommended, device_tracker.see, does not require a MAC address… the only required configuration variable is an identifier string, dev_id, that you can just make up.

1 Like

When I tried, the automation failed with a ‘requies Mac address’ error.

However, I discovered that, as you say, it requires a Dev_ID entry and if you insert a Dev_ID string to the automation, it adds that to the known_devices.yaml file and creates a dummy device_tracker device.

The easier setup (in my opinion) is to create a group in yaml (not UI) called family, in this group you add the input_boolean (and the other family members).
Use this group in all automations where home/away presence is needed.

No need for extra automations with device_tracker.see

1 Like