From b650957b405b5160b7d4b55758d240e344203d3b Mon Sep 17 00:00:00 2001 From: Teknium <127238744+teknium1@users.noreply.github.com> Date: Thu, 9 Apr 2026 03:57:11 -0700 Subject: [PATCH] docs(bluebubbles): fix pairing instructions to use existing approve flow (#6548) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The docs incorrectly referenced 'hermes pairing generate bluebubbles' which doesn't exist. The existing reactive pairing flow already handles this — when an unknown user messages the bot, it sends them a code automatically, and the owner approves with 'hermes pairing approve'. --- website/docs/user-guide/messaging/bluebubbles.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/website/docs/user-guide/messaging/bluebubbles.md b/website/docs/user-guide/messaging/bluebubbles.md index 3f023d317..cde969031 100644 --- a/website/docs/user-guide/messaging/bluebubbles.md +++ b/website/docs/user-guide/messaging/bluebubbles.md @@ -43,17 +43,18 @@ BLUEBUBBLES_PASSWORD=your-server-password Choose one approach: **DM Pairing (recommended):** +When someone messages your iMessage, Hermes automatically sends them a pairing code. Approve it with: ```bash -hermes pairing generate bluebubbles +hermes pairing approve bluebubbles ``` -Share the pairing code — the user sends it via iMessage to get approved. +Use `hermes pairing list` to see pending codes and approved users. -**Pre-authorize specific users:** +**Pre-authorize specific users** (in `~/.hermes/.env`): ```bash BLUEBUBBLES_ALLOWED_USERS=user@icloud.com,+15551234567 ``` -**Open access:** +**Open access** (in `~/.hermes/.env`): ```bash BLUEBUBBLES_ALLOW_ALL_USERS=true ```