Verification Request: homebridge-winpc-tv

Abierto
#1,328 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
58/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start by reading the Homebridge plugin verification requirements and inspect the linked homebridge-winpc-tv repository to check the submitted claims, especially installation, configuration, error handling, and storage behavior. The issue gives no specific files or tests to run; done means the verification request has been reviewed and the plugin’s status or any needed follow-up is recorded.

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

Descripción

awaiting-final-review request-verification
Plugin Name

homebridge-winpc-tv

Link To GitHub Repo

https://github.com/orenasher/homebridge-winpc-tv

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

Exposes a Windows PC as a HomeKit TV: Wake-on-LAN to turn on, Airytec Switch Off to turn off, with real power state polling.

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.