Verification Request: homebridge-tuya-without-developer-account

Open
#1,290 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
54/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
node.js, typescript

Research direction

Read the plugin verification requirements and inspect the linked repository’s package.json and published npm package metadata, focusing on the missing supports-hap transport keyword. Check whether the remaining verification criteria are met by the submitted evidence. Done means a new npm patch release includes the corrected keyword and the published package passes the verification checks.

Written by the indexing model from the issue text.

Description

awaiting-final-review request-verification
Plugin Name

homebridge-tuya-without-developer-account

Link To GitHub Repo

https://github.com/Kosztyk/homebridge-tuya-without-developer-account

Plugin Icon (Optional)

Official TUYA vendor logo

100 × 100 PNG using the official vendor artwork with its proportions preserved. Official source: https://www.tuya.com/
Asset provenance: https://github.com/Kosztyk/homebridge-tuya-without-developer-account/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.

🟢 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

Current npm version: 1.1.3
npm: https://www.npmjs.com/package/homebridge-tuya-without-developer-account/v/1.1.3
GitHub release with notes: https://github.com/Kosztyk/homebridge-tuya-without-developer-account/releases/tag/v1.1.3

Functionality and differentiation:
QR authentication with the Tuya/Smart Life consumer app, without an IoT developer project. Additional behavior includes opt-in per-device fan-speed presets, schema-aware discrete speed mapping, physical garage-door contact feedback and HomeKit name synchronization. Version 1.1.3 also includes IR air-conditioner controls, partial LAN hub updates via dp-refresh, and LAN power-state precedence over delayed cloud updates. These are the specific enhancements submitted for review alongside overlap with existing Tuya plugins.

Validation:
The published npm version 1.1.3 and the GitHub release/package metadata were checked. The npm tarball contains the plugin entry point, config.schema.json and the 100 × 100 official vendor icon.
The package engine range includes Node 22 and 24; no additional live-device test or local Node 22 test is claimed.

Published verification fixes:

  • The npm 1.1.3 package includes the supports-hap transport keyword.
  • Homebridge is declared only in devDependencies, not runtime, optional or peer dependencies.
  • The release retains the verification fixes and branding merged from 1.1.1 alongside the 1.1.3 IR AC changes.

Previous automated verification:
Version 1.1.1 passed all automated checks: https://github.com/homebridge/plugins/actions/runs/39845818706
A fresh automated check is requested for version 1.1.3. 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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from homebridge/plugins

All issues in homebridge/plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.