Verification Request: homebridge-roborock-room-clean
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 12/100
Research direction
This is a verification request for a Homebridge plugin, not a code change. The work is a maintainer review of the linked repository at github.com/orenasher/homebridge-roborock-room-clean and its npm package, checking the six checklist items above. A newcomer can't finish it by editing this repo, and the thread already has three comments, so it is not a first-timer task.
Written by the indexing model from the issue text.
Description
Plugin Name
homebridge-roborock-room-clean
Link To GitHub Repo
https://github.com/orenasher/homebridge-roborock-room-clean
Plugin Icon (Optional)
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
Each room on the Roborock map becomes a fan in Apple Home (fan speed = suction power), with no limit of 10 routines. Roborock routines can be added as switches. Optional: charging, cleaning, returning and stopped sensors, a child lock switch, the robot as a Matter robot vacuum (Homebridge 2) that shows which room is being cleaned, and a live map camera.
Pure Node.js. It needs no other plugins or scripts. Everything is stored in the Homebridge storage folder, and the settings UI is in English and Hebrew.
npm: https://www.npmjs.com/package/homebridge-roborock-room-clean
The icon is original artwork with no third-party trademarks.
- 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 65/100
homebridge/plugins#1331 · 2 comments ·
-
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 ·
All issues in homebridge/plugins
Similar issues
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area: testing bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
snapotter-hq/SnapOtter#5099 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EveryInc/compound-engineering-plugin#2091 ·
Maintainers usually reply within 1 day