Wyze lock initial push.

[Mmiless]

What does this Ability do?

Allows for voice and optional WhatsApp control over the Wyze Lock Bolt v2. Relies on undocumented Wyze APIs.

Suggested Trigger Words

• Desired lock password
• The phrase "lock up", or something similar.
• (Need both)

Type

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

External APIs

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

Uses undocumented Wyze API endpoint that was reverse engineered. Must get Wyze API key from their developer console. https://developer-api-console.wyze.com/#/apikey/view

Also utilizes Twilio API and requires some specific setup using the WhatsApp sandbox. README for details.

Testing

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

Note: Wyze API is subject to change at any time. Check community SDK repos for latest. https://github.com/SecKatie/ha-wyzeapi is a good one. Code in WyzeLockClient based on their work in this PR: SecKatie/ha-wyzeapi#809. Currently unmerged.

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?

See README

[github-actions]

✅ Community PR Path Check — Passed

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

[github-actions]

🔀 Branch Merge Check

PR direction: wyze → dev

✅ Passed — wyze → dev is a valid merge direction

[github-actions]

❌ Ability Validation Failed

📋 Validating: community/wyze-lock-v2
  ❌ MD5 is a weak hash and not allowed — use a stronger algorithm like SHA-256
  ⚠️  Found 2 classes — only one class per main.py is recommended
  ❌ 1 error(s) found

📚 How to fix

• Read the Contributing Guide
• Check the CapabilityWorker Reference
• See Blocked Imports & Keywords

[github-actions]

🔍 Lint Results

✅ __init__.py — Empty as expected

Files linted: community/wyze-lock-v2/background.py community/wyze-lock-v2/main.py

✅ Flake8 — Passed

✅ All checks passed!

[Mmiless]

❌ Ability Validation Failed

📋 Validating: community/wyze-lock-v2
  ❌ MD5 is a weak hash and not allowed — use a stronger algorithm like SHA-256
  ⚠️  Found 2 classes — only one class per main.py is recommended
  ❌ 1 error(s) found

📚 How to fix

* Read the [Contributing Guide](CONTRIBUTING.md)

* Check the [CapabilityWorker Reference](docs/capability-worker.md)

* See [Blocked Imports & Keywords](https://docs.openhome.com/how_to_build_an_ability#blocked-imports-and-keywords)

MD5 is needed to sign secret in the Wyze API call.