homebridge / homebridge/plugins
Verification Request: homebridge-alexa-sync
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 369
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Plugin Name
homebridge-alexa-sync
Link To GitHub Repo
https://github.com/johnccarroll/homebridge-alexa-sync
Plugin Icon (Optional)
No response
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
🟢 Yes
The plugin successfully installs and does not start unless it is configured.
🟢 Yes
The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.
🟢 Yes
The plugin does not contain any analytics or calls that enable you to track the user.
🟢 Yes
If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.
🟢 Yes
The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.
🟢 Yes
More Information
Built on Homebridge 2.x (currently testing on homebridge@2.0.0-beta.101). Dynamic platform plugin with alias AlexaSync. TypeScript/ESM/Node 20+.
Provider architecture: Tuya (direct cloud API + Pulsar push), Alexa (alexa-remote2 cookie fallback), Resideo (OAuth, code complete, awaiting Resideo dev approval).
Optional Alexa Smart Home Skill voice control via the Switchboard managed cloud (paid sponsorship at github.com/sponsors/johnccarroll). The plugin works fully free locally for HomeKit-only use forever — sponsorship only unlocks the optional cloud features. Token verification happens entirely offline against an embedded Ed25519 public key; no phone-home, no telemetry. Alternative self-hosted AWS Lambda path is fully documented in README.
107 unit tests covering directives, providers, accessory mapping. CI on Node 20/22/24 via .github/workflows/validate.yml. npm publishes through Trusted Publishing OIDC (no stored tokens).
Closest existing verified plugin is homebridge-alexa (NorthernMan54), which is one-way (Alexa → Homebridge). homebridge-alexa-sync differs in two material ways: (a) two-way bidirectional sync with a provider-based architecture preferring direct APIs over cookie scraping; (b) optional managed Alexa Smart Home Skill with no AWS account required by the user. Neither feature exists in the current verified set.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked homebridge-alexa-sync repository and its README, then check the verification claims against the homebridge/plugins requirements. The plugin's .github/workflows/validate.yml and 107 unit tests provide evidence for its stated support and behavior. Done means the verification request has been reviewed and a decision or required follow-up is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100