Authorization notice. Vision State is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA family that wants Home Assistant to know who has arrived, and to notice an unknown person at the door.
The problemPresence sensors often rely on phones, and a camera view of the drive gives no named result.
The outcomeObject and person sensors for COCO objects such as cars, plus named people recognised by face. Unknown people appear as their own sensor.
What you need first
- Home Assistant OS or Home Assistant Supervised, version 2025.10 or newer
- The Mosquitto broker app and the MQTT integration in Home Assistant
- A camera that Home Assistant can see as a camera entity, or an RTSP or HTTP snapshot URL
Steps
- Install Vision State, open it from the sidebar, and choose New sensor for the driveway or front door camera.
- Draw a region around the driveway or door so only that area is watched.
- Choose the objects to watch, such as car, from the list of 80 objects. No training is needed for these.
- Turn on face recognition for that camera, then add a few photos of each person and give them a name. Faces are kept in the app's own storage.
- Check the object sensor and the person sensor in Home Assistant, then add an automation if you want a message when a named person arrives.
Prompt for your agent
Using the VisionState repo at https://github.com/oleost/VisionState, set up object and person sensors for the camera <camera_entity>, with named people <person_names>. Expected output: an on/off sensor for each named person and for the car object. Verify that face recognition is enabled only for the camera you chose.
Caveat. Face recognition is a dual-use capability, so only enable it for cameras where you have a clear reason and where people have been told they are being recognised.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page