Verification Request: homebridge-xiaomi-mi
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, typescript
- Domain
- developer-experience, documentation
Research direction
Read the verification requirements in the issue and compare them with the plugin repository at https://github.com/Kosztyk/homebridge-miot, especially package.json and config.schema.json. Start by checking the current published npm package against the listed requirements and reviewing the claimed differences from the verified upstream plugin. The issue is resolved when maintainers can decide whether the plugin meets the verification and differentiation requirements and its publication blockers are addressed.
Written by the indexing model from the issue text.
Description
Plugin Name
homebridge-xiaomi-mi
Link To GitHub Repo
https://github.com/Kosztyk/homebridge-xiaomi-mi
Plugin Icon (Optional)
![]()
100 × 100 PNG using the official vendor artwork with its proportions preserved. Official source: https://www.mi.com/global/
Asset provenance: https://github.com/Kosztyk/homebridge-xiaomi-mi/blob/main/BRANDING.md
This independent community plugin is not affiliated with or endorsed by the vendor. The logo identifies supported devices.
The plugin does not offer the same nor less functionality than that of any existing verified plugin.
🟠 No (please explain in the more information box at the end)
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
Current npm version: 1.0.22
npm: https://www.npmjs.com/package/homebridge-xiaomi-mi/v/1.0.22
GitHub release with notes: https://github.com/Kosztyk/homebridge-xiaomi-mi/releases/tag/1.0.22
Functionality and differentiation:
This is a fork of merdok/homebridge-miot and substantially overlaps that verified plugin. Original upstream credit is retained. The fork adds dedicated Xiaomi Robot Vacuum E5 (xiaomi.vacuum.c108) controls, additional careli.fryer.maf02 air-fryer actions and refinements to device/service behavior. Please assess whether these differences meet the differentiation requirement; a renamed package alone is not offered as justification.
Validation:
No automated test suite is provided by this fork. Entry-point syntax, package loading/installation, npm pack dry run and the corrected JSON schema were checked.
The package engine range includes Node 22 and 24; no additional live-device test or local Node 22 test is claimed.
Published fixes:
- The current npm package includes the
supports-haptransport keyword. - The published config.schema.json uses object-level
requiredarrays and includes the platformnameproperty. - Repository, homepage and issue URLs now match the renamed GitHub repository.
Previous automated verification:
Version 1.0.21 passed all automated checks: https://github.com/homebridge/plugins/actions/runs/39845882010
Version 1.0.22 updates repository metadata and publication documentation; the new version is submitted for a fresh automated check. Manual Homebridge review is still pending.
Error-handling confirmation is based on reviewed startup, network and command paths and the available regression tests; no claim of exhaustive failure coverage is made.
- Dominant language
- TypeScript
- Stars
- 371
- Forks
- 26
- Avg merge
- 1h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from homebridge/plugins
-
awaiting-final-review request-icon
Difficulty 1/5 Under an hour Newbie friendliness 70/100
homebridge/plugins#1376 · 1 comment ·
-
awaiting-final-review request-verification
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
homebridge/plugins#1331 · 2 comments ·
-
awaiting-final-review request-verification
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
homebridge/plugins#1288 · 1 comment ·
-
awaiting-changes request-icon
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
homebridge/plugins#1222 · 8 comments ·
-
awaiting-final-review request-verification
Difficulty 4/5 3-5 days Newbie friendliness 35/100
homebridge/plugins#1374 · 2 comments ·
All issues in homebridge/plugins
Similar issues
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area: testing bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
snapotter-hq/SnapOtter#5099 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EveryInc/compound-engineering-plugin#2091 ·
Maintainers usually reply within 1 day