Verification Request: homebridge-xiaomi-mi

Abierto
#1,291 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
node.js, typescript

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

awaiting-final-review request-verification
Plugin Name

homebridge-xiaomi-mi

Link To GitHub Repo

https://github.com/Kosztyk/homebridge-xiaomi-mi

Plugin Icon (Optional)

Official XIAOMI vendor logo

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-hap transport keyword.
  • The published config.schema.json uses object-level required arrays and includes the platform name property.
  • 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.

Lenguaje dominante
TypeScript
Estrellas
371
Forks
26
Merge medio
1 h
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de homebridge/plugins

Todos los issues de homebridge/plugins

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.