Verification Request: homebridge-tuya-ceiling-fan
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- developer-experience
Research direction
Start with the verification checklist in this issue and review the linked homebridge-tuya-ceiling-fan repository. Check whether the plugin meets each stated requirement and supports the described ceiling fan and light functions; record any verification gaps with evidence. Done means the plugin's verification status can be decided from the checklist and repository.
Written by the indexing model from the issue text.
Description
Plugin Name
homebridge-tuya-ceiling-fan
Link To GitHub Repo
https://github.com/orenasher/homebridge-tuya-ceiling-fan
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
Local (LAN) control of Tuya-based ceiling fans with light: speed, direction, light and light modes, with a setup wizard in the UI. Focused on fan+light combos that generic Tuya plugins handle poorly.
- 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 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 ·
-
awaiting-final-review request-verification
Difficulty 4/5 3-5 days Newbie friendliness 12/100
homebridge/plugins#1371 · 2 comments ·
All issues in homebridge/plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mindfold-ai/Trellis#672 ·
-
p1 state:active track
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
StellarCanary/ProtocolCanary-Action#698 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pear-devs/pear-desktop#4839 ·
Maintainers usually reply within 1 day
-
product:platform
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Infisical/infisical#9746 · 1 comment ·
Maintainers usually reply within 1 day