Verification Request: homebridge-landroid-v2 (successor to discontinued, still-verified homebridge-landroid)

[mrcksz]

Plugin Name

homebridge-landroid-v2

Link To GitHub Repo

https://github.com/mrcksz/homebridge-landroid-v2

Plugin Icon (Optional)

No response

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

homebridge-landroid-v2 is a maintained fork of homebridge-landroid (Worx Landroid / Kress / Ferrex / Landxcape mowers).

I want to flag the duplicate-functionality situation up front: the original homebridge-landroid is still on the verified list but was discontinued by its author in December 2023 and no longer works — Worx removed the GET /api/v2/users/me route, which crashes its MQTT connection, and it also crashes on Homebridge 2.x (removed Service.BatteryService alias). This fork fixes both and is confirmed working on Homebridge 2.2.1.

Since the existing verified plugin is abandoned and non-functional, how would you prefer to proceed — (1) delist the discontinued homebridge-landroid and verify homebridge-landroid-v2 as its working successor, or (2) a maintainer-handover path you prefer?

Checklist: dynamic platform ✓ · npm + GitHub w/ issues ✓ · GitHub releases ✓ · settings GUI ✓ · doesn't start unless configured ✓ · Node 18/20/22 ✓ · no analytics/tracking ✓ · writes only to Homebridge storage dir ✓ · catches/logs its own errors ✓ · note: uses aws-iot-device-sdk-v2 (aws-crt, native build) for the Worx AWS IoT MQTT connection, same as upstream ioBroker.worx.

MIT-licensed; connector code derived from ioBroker.worx (MIT) and the original homebridge-landroid (MIT), both credited in LICENSE.

[github-actions]

🔴 Failed Checks

• Package JSON: engines.node property is not compatible with Node 24
• Config Schema JSON: schema missing type property
• Config Schema JSON: does not contain a name schema property

🟢 Passed Checks

• Installation: successfully installed
• Package JSON: homepage exists
• Package JSON: bugs.url exists and seems a valid URL
• Package JSON: keywords exist and contain 'homebridge-plugin'
• Package JSON: keywords declare the supported transports ('supports-hap' and/or 'supports-matter')
• Package JSON: 'preinstall' in scripts is not present
• Package JSON: 'install' in scripts is not present
• Package JSON: 'postinstall' in scripts is not present
• Package JSON: engines.node property is compatible with Node 22
• Package JSON: engines.homebridge property is compatible with Homebridge 2.2.1
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v2.0.2) matches NPM version (v2.0.2)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains valid JSON Schema
• Config Schema JSON: contains a valid pluginAlias
• Config Schema JSON: pluginAlias matches the platform/accessory registered in code
• Config Schema JSON: the pluginType is set to 'platform'
• Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
• Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
• Security: no critical vulnerabilities (9 high, 1 moderate, 0 low)
• Security: code patterns flagged for manual review
• Security: no privilege escalation attempts detected
• GitHub Repo: repository is public
• GitHub Repo: repository is not archived
• GitHub Repo: issues are enabled
• GitHub Repo: contains releases

🔍 For Manual Review

The following items were detected and require manual review. We understand that these items may be false positives.

• Security: found 9 high-severity vulnerabilities in dependencies (manual review recommended)
• Security: uses dynamic require() which could load arbitrary code found in 2 files

ℹ️ Check Details

• These checks were run against v2.0.2 of the plugin.
• Link to the run workflow: visit →.

📋 Next Steps

• Once you have fixed these failures, comment /check on this issue to run the checks again — your request will not move forward until the checks are re-run.
• If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.
• Remember this is an automatic script: if you think something has been marked as a failure in error, let us know with a reply.
• Feel free to ask any questions you have by replying to this issue.

[github-actions]

It looks like you wanted to re-run the checks, but the checks have not been started.

To run them, please add a new comment with /check on a line by itself (it can be the only thing in the comment). It will not be picked up when it is part of a longer line.

[mrcksz]

/check

[github-actions]

🔴 Failed Checks

• Config Schema JSON: schema is invalid - required should not be a boolean property on individual fields. In JSON Schema, required must be an array at the object level listing required property names. Remove "required": true/false from individual properties and use "required": ["property1", "property2"] at the object level instead.

🟢 Passed Checks

• Installation: successfully installed
• Package JSON: homepage exists
• Package JSON: bugs.url exists and seems a valid URL
• Package JSON: keywords exist and contain 'homebridge-plugin'
• Package JSON: keywords declare the supported transports ('supports-hap' and/or 'supports-matter')
• Package JSON: 'preinstall' in scripts is not present
• Package JSON: 'install' in scripts is not present
• Package JSON: 'postinstall' in scripts is not present
• Package JSON: engines.node property is compatible with Node 22
• Package JSON: engines.node property is compatible with Node 24
• Package JSON: engines.homebridge property is compatible with Homebridge 2.2.1
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v2.0.3) matches NPM version (v2.0.3)
• Config Schema JSON: exists and is valid JSON
• Config Schema JSON: contains a valid pluginAlias
• Config Schema JSON: pluginAlias matches the platform/accessory registered in code
• Config Schema JSON: the pluginType is set to 'platform'
• Config Schema JSON: contains a name schema property
• Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
• Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
• Security: no critical vulnerabilities (7 high, 1 moderate, 0 low)
• Security: no unsafe code patterns detected
• Security: no privilege escalation attempts detected
• GitHub Repo: repository is public
• GitHub Repo: repository is not archived
• GitHub Repo: issues are enabled
• GitHub Repo: contains releases

🔍 For Manual Review

The following items were detected and require manual review. We understand that these items may be false positives.

• Security: found 7 high-severity vulnerabilities in dependencies (manual review recommended)

ℹ️ Check Details

• These checks were run against v2.0.3 of the plugin.
• Link to the run workflow: visit →.

📋 Next Steps

• Once you have fixed these failures, comment /check on this issue to run the checks again — your request will not move forward until the checks are re-run.
• If updating your package.json and config.schema.json files, don't forget to publish a new version to NPM.
• Remember this is an automatic script: if you think something has been marked as a failure in error, let us know with a reply.
• Feel free to ask any questions you have by replying to this issue.

[mrcksz]

/check