Verification Request: homebridge-xiaomi-mi
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- node.js, typescript
- Ambito
- developer-experience, documentation
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- TypeScript
- Stelle
- 371
- Fork
- 26
- Merge medio
- 1h
- PR unite (30g)
- 5
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di homebridge/plugins
-
awaiting-final-review request-icon
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 70/100
homebridge/plugins#1376 · 1 commento ·
-
awaiting-final-review request-verification
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
homebridge/plugins#1331 · 2 commenti ·
-
awaiting-final-review request-verification
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
homebridge/plugins#1288 · 1 commento ·
-
awaiting-changes request-icon
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
homebridge/plugins#1222 · 8 commenti ·
-
awaiting-final-review request-verification
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
homebridge/plugins#1374 · 2 commenti ·
Tutte le issue di homebridge/plugins
Issue simili
-
P2
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
bug ready-for-human
Difficoltà 2/5 1-3 ore Idoneità per principianti 60/100
LucasSantana-Dev/Lucky#3150 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement good first issue priority: low size: XS
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
area: testing bug priority: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 87/100
snapotter-hq/SnapOtter#5099 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
EveryInc/compound-engineering-plugin#2091 ·
I maintainer di solito rispondono entro 1 giorno