Skip to content

feat: Support direct access token auth, auto device discovery, and du…#6

Open
veerkak wants to merge 1 commit into
AmazonAppDev:mainfrom
veerkak:feat/access-token-auth-and-auto-discovery
Open

feat: Support direct access token auth, auto device discovery, and du…#6
veerkak wants to merge 1 commit into
AmazonAppDev:mainfrom
veerkak:feat/access-token-auth-and-auto-discovery

Conversation

@veerkak
Copy link
Copy Markdown

@veerkak veerkak commented May 11, 2026

  • Add RING_ACCESS_TOKEN support (direct token, no client credentials needed)
  • Preserve existing RING_REFRESH_TOKEN flow (requires client_id + client_secret)
  • Error if both are set simultaneously
  • Auto-discover devices via GET /v1/devices when NEXT_PUBLIC_RING_DEVICE_ID not set
  • Stream route accepts deviceId from frontend (after discovery)
  • Add RING_API_BASE_URL env var for configurable API endpoint
  • Simplified live-view-only UI in access token mode
  • Full dashboard (events, processors, webhooks) in refresh token mode
  • Add /api/ring/config endpoint for frontend auth mode detection
  • Update README with dual auth documentation and env vars table

Comment thread README.md Outdated

The app supports two authentication modes. Choose one — do not set both.

### Option 1: If you have an Access Token
Copy link
Copy Markdown

@anishamalde anishamalde May 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets include the docs link to show where to get these tokens & why you would use one or the other?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added relevant links now

Comment thread README.md Outdated

Open [http://localhost:3000](http://localhost:3000) in your browser.

## Authentication
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devs would still need all the back end urls right to get the token right?
Can we make this clearer / provide an easy way for them to simulate this?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need of this set-up with Playground feature READ.ME latest should cover this.

Comment thread .env.example
RING_CLIENT_SECRET=your_client_secret_here

# Ring Device
NEXT_PUBLIC_RING_DEVICE_ID=your_device_id_here
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we include doc links on where these would be received from?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done included Playground Link for clarity.

@veerkak veerkak force-pushed the feat/access-token-auth-and-auto-discovery branch from aa70193 to d0c20a9 Compare May 13, 2026 14:22
… API scripts, and dual UI modes

- Add RING_ACCESS_TOKEN support (direct token, no client credentials needed)
- Preserve existing RING_REFRESH_TOKEN flow (requires client_id + client_secret)
- Error if both are set simultaneously
- Auto-discover devices via GET /v1/devices when NEXT_PUBLIC_RING_DEVICE_ID not set
- Access token mode ignores NEXT_PUBLIC_RING_DEVICE_ID (always auto-discovers)
- Stream route accepts deviceId from frontend (after discovery)
- Simplified live-view-only UI in access token mode
- Full dashboard (events, processors, webhooks) in refresh token mode
- Add /api/ring/config endpoint for frontend auth mode detection
- Add scripts/ folder with 8 Python scripts for calling Ring APIs
- Each script is standalone, prints curl equivalent, auto-discovers device
- Interactive explore_apis.py menu for trying all APIs
- Comprehensive README restructured for first-time users (Step 1/2/3)
- Doc links for tokens, credentials, and device IDs throughout
- .env.example updated with doc links for all values
@veerkak veerkak force-pushed the feat/access-token-auth-and-auto-discovery branch from d0c20a9 to 3aa4b70 Compare May 13, 2026 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants