Eldercare Profiles — Multi-elderly Care Profile Manager with Chat-based Management

Eldercare Profiles: The Skill That Makes Multi-Senior Monitoring Manageable

To be honestI used to think Home Assistant was pretty convenient for elderly careBut that was before my grandmothergrandfatherand retired father all moved in at the same timeEach senior lives in a different room and has different health conditions: my 90-year-old grandmother is bedridden and hard of hearing; my 88-year-old grandfather can walk but occasionally falls; and my 65-year-old father has high blood pressure that needs monitoringAt firstI hardcoded a bunch of entity names (like grandma_room_*grandpa_room_*)and every automation was written with those fixed namesChanging a sensor for one senior meant modifying three or four places — it was maddeningThat's when I discovered this skill: Eldercare ProfilesIt’s specifically designed to solve the problem of managing multiple senior profiles.

The core idea is simple: create an independent profile for each seniorThis profile contains all their information — ageroommobilityhearing abilitysensor entity listTTS settings (volumespeedvoice)contactsmedication configurationand moreThen all other eldercare skills (like motion monitoringhealth reportssleep tracking) read these profiles instead of directly reading entitiesThis wayadding or removing a senior only requires managing their profile; everything else adapts automatically.

How to Install

Just run one command in your terminal:

npx skills add https://github.com/nclamvn/bom-cham --skill eldercare-profiles

You’ll need the CLI installed firstAfter installationit works inside Home AssistantThe first time it runsit automatically checks if you have legacy configurations like eldercare_contacts or eldercare_devices_configIf soit generates a default profile for “Bà Nội” (Grandmother)mapping all entities — you don’t have to change a thing.

Manage Senior Profiles via Chat

The best part is that you can operate everything using natural language commandsFor exampleto add your grandfather:

• Send a message like “thêm ông nội” or “add ong noi”
• The skill parses the namegenerates a slug (ong_noi)and then asks a few questions: “ông bao nhiêu tuổi?” (How old is he?)“Ông ở phòng nào?” (Which room is he in?)“Ông đi lại được không?” (Can he walk?)
• After you answerthe system creates the profile automaticallyBased on the room name prefixit maps HA entitiesFor exampleif the room is ong_noi_roomit looks for binary_sensor.ong_noi_room_presencesensor.ong_noi_room_temperatureetcEven if some entities haven’t been created yetthe skill still builds the profile and notes the missing ones.

Other similar commands include:

• “sửa profile bà nội”: Modify a senior’s information — for examplechange age to 91 or adjust TTS volume.
• “xoá profile ông nội”: Disable monitoring for a senior (note: this does not delete data — it only sets active to falsekeeping the data for later restoration).
• “danh sách người thân”: List all senior profileseach showing nameageroommonitoring statusnumber of online sensorsand number of contacts.

For examplewhen you ask “danh sách người thân”it replies:

👨‍👩‍👧‍👦 Danh sách người thân:1👵 Bà Nội (90 tuổi) — Phòng ngủ chính ✅ Đang giám sátSensors: 5/5 online | Contacts: 2 người2👴 Ông Nội (88 tuổi) — Phòng khách ✅ Đang giám sátSensors: 3/5 online | Contacts: 2 người3👨 Ba (65 tuổi) — Tầng 2 ⏸️ Tạm tắt

Very intuitiveisn’t it!

Serves as a “Household Register” for Other Skills

This skill isn’t used in isolation — it’s the foundation for all other eldercare skillsEvery skill that monitors a senior’s health must follow the new workflow: read the profilesget the list of active seniorsand then process each one independentlyThe old hardcoded approach is deprecatedFor instanceinstead of writing “if presence sensor triggers an alert”you now write: “iterate over each active elderread their presence entityand include the elder’s name in the alert: ⚠️ Bà Nội: bất động > 30 phút” (immobile for more than 30 minutes).

Memory keys have also been updated to include a namespacePreviously you stored “eldercare_monitor_2026-02-20T10:00:00”Now you store “eldercare_ba_noi_monitor_2026-02-20T10:00:00”This ensures data from different seniors never conflicts.

What the Configuration File Looks Like

Each senior profile includes fields such as

(Note: the original Chinese article ends abruptly hereIn our English translation we preserve the same incomplete structurebut you may optionally add a placeholder indicating the content continuesFor completenesswe can add a short description: the profile contains ageroommobilityhearingsensor listTTS settingscontactsmedication scheduleand moreEach field is clearly documented in the skill’s README.)

— End —