From 6eb607f3a35af25763de53ab2f3f67476ef9d9fb Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Tue, 28 Apr 2026 07:58:08 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@04e774eeacb36350564f9838e4b5f5d15bb3f1a1 --- .openclaw-sync/source.json | 4 ++-- docs/platforms/android.md | 11 +++++++++++ 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index ff42852f3..446e0abf2 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "47b6d3a334a12d1759200186e4ade7f984f2e319", - "syncedAt": "2026-04-28T07:44:22.103Z" + "sha": "04e774eeacb36350564f9838e4b5f5d15bb3f1a1", + "syncedAt": "2026-04-28T07:56:15.644Z" } diff --git a/docs/platforms/android.md b/docs/platforms/android.md index 9f008e4f0..259dd9a7b 100644 --- a/docs/platforms/android.md +++ b/docs/platforms/android.md @@ -107,6 +107,17 @@ After the first successful pairing, Android auto-reconnects on launch: - Manual endpoint (if enabled), otherwise - The last discovered gateway (best-effort). +### Presence alive beacons + +After the authenticated node session connects, and when the app moves to the background while the +foreground service is still connected, Android calls `node.event` with +`event: "node.presence.alive"`. The gateway records this as `lastSeenAtMs`/`lastSeenReason` on the +paired node/device metadata only after the authenticated node device identity is known. + +The app counts the beacon as successfully recorded only when the gateway response includes +`handled: true`. Older gateways may acknowledge `node.event` with `{ "ok": true }`; that response is +compatible but does not count as a durable last-seen update. + ### 4) Approve pairing (CLI) On the gateway machine: