Package tracker

[maxflips16]

What does this Ability do?

A voice‑driven package tracker for OpenHome. Users can add tracking numbers with friendly names, check real‑time status via the TrackingMore API, list all packages, and remove them – all through natural voice commands.

Suggested Trigger Words

• track my package
• where's my package
• package status
• tracking

Type

• New community Ability

External APIs

• Uses external API(s): TrackingMore API (v4) – requires a free API key, stored in config.json with placeholder.

Testing

• Tested in OpenHome Live Editor
• All exit paths tested
• Error scenarios tested

Checklist

• Files are in community/package-tracker/
• main.py follows SDK pattern
• README.md included
• resume_normal_flow() called on every exit path
• No print() – using editor_logging_handler
• No hardcoded API keys – using placeholders
• No blocked imports
• No asyncio.sleep() or asyncio.create_task()
• Error handling on all external calls

Anything else?

• https://www.loom.com/share/f4058e4151234170972c137b5b0db5cc

[github-actions]

🔀 Branch Merge Check

PR direction: package-tracker → dev

✅ Passed — package-tracker → dev is a valid merge direction

[github-actions]

✅ Ability Validation Passed

📋 Validating: community/package-tracker
  ✅ All checks passed!

[github-actions]

🔍 Lint Results

Files linted: community/package-tracker/main.py

✅ Flake8 — Passed

✅ All checks passed!

[maxflips16]

waiting on revision!

[codermohsin]

under review

[codermohsin]

Hey

I have reveiwd and ran your ability code but it's not triggered with me.
please check your code and make sure your requested the latest commit.

[maxflips16]

Hi,

Thanks for the feedback. I've reviewed the code and added a fallback so the ability will trigger even if config.json isn't loaded correctly. Now, if the config is missing, it still registers with the default hotwords:
track my package, where's my package, package status, tracking.

Please pull the latest changes from the package-tracker branch (the commit is now up‑to‑date) and redeploy the ability. After that, try the trigger words again.

If it still doesn't trigger, could you:

Check that the config.json file is present in the same directory as main.py and contains the matching_hotwords list.

Share any logs or error messages from the OpenHome Live Editor — that would help me see what the runtime actually loaded.

I've also added a startup log that prints the registered hotwords, so any logs you can provide will be very useful.

Thanks again for your help testing this — we're very close to a fully working ability.

Best regards,
Maxwell

[maxflips16]

ability should be good to go

[codermohsin]

Your ability is under review.

Our team will review it and provide feedback shortly.

Thank you for your submission

[github-actions]

✅ Community PR Path Check — Passed

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