Feature/podcast player

[SpkArtZen]

What does this Ability do?

Suggested Trigger Words

Type

• New community Ability
• Improvement to existing Ability
• Bug fix
• Documentation update

External APIs

• No external APIs
• Uses external API(s):

Testing

• Tested in OpenHome Live Editor
• All exit paths tested (said "stop", "exit", etc.)
• Error scenarios tested (API down, bad input, etc.)

Checklist

• Files are in community/my-ability-name/
• main.py follows SDK pattern (extends MatchingCapability, has register_capability + call)
• README.md included with description, suggested triggers, and setup
• resume_normal_flow() called on every exit path
• No print() — using editor_logging_handler
• No hardcoded API keys — using placeholders
• No blocked imports (redis, user_config)
• No asyncio.sleep() or asyncio.create_task() — using session_tasks
• Error handling on all external calls
• Tested in OpenHome Live Editor

Anything else?

[github-actions]

🔀 Branch Merge Check

PR direction: feature/podcast_player → dev

✅ Passed — feature/podcast_player → dev is a valid merge direction

[github-actions]

✅ Community PR Path Check — Passed

All changed files are inside the community/ folder. Looks good!

[github-actions]

✅ Ability Validation Passed

📋 Validating: community/podcast-player
  ✅ All checks passed!

[github-actions]

🔍 Lint Results

✅ __init__.py — Empty as expected

Files linted: community/podcast-player/main.py

✅ Flake8 — Passed

✅ All checks passed!

[uzair401]

Hi @SpkArtZen, please update your code to follow the new SDK changes for API key management as outlined in the docs: https://docs.openhome.com/OpenHome_SDK_Reference#15-custom-api-keys

Also since this ability uses a paid service API key, please also provide a Loom demo showing the full working flow with the actual service. Once that’s submitted, we can proceed with the review and approval.