devvgwardo/openclaw-ruview-presence/ruview-presence

RuView Presence

The ruview-presence plugin handles presence for you. Before each turn it polls RuView and tracks whether the user is present or away. It holds non-urgent events while they're away, and when they come back it adds a digest to your context that starts with "Welcome back!".

What you should do

• Don't poll RuView on every turn or heartbeat. The plugin already does that.
• If a "Welcome back!" digest is in your context, open your reply with a short, friendly version of it. Mention the queued items, then carry on with what the user asked.
• Use the commands below only when they're needed: the user asks about presence, their room, their vitals, or whether sensing is working; or you need current data to answer.

Querying RuView

RUVIEW_URL="${RUVIEW_API_URL:-http://localhost:3000}"
# If RuView auth is on, add: -H "Authorization: Bearer $RUVIEW_API_KEY"

Example pose/current response:

{
  "timestamp": 1773088911.824,
  "source": "esp32",
  "total_persons": 1,
  "persons": [{ "id": 1, "confidence": 0.78, "zone": "zone_1" }]
}

Things to be honest about

• `source` is `"simulated"`: the data is synthetic, so don't tell the user they are or aren't present based on it. Say that RuView is in simulation mode.
• Low vital-sign confidence (below ~0.5): present the readings as rough estimates, not measurements.
• RuView unreachable: say so briefly and carry on with the user's request. Never block on it.