You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Brand-focused plugin for Meaco portable air conditioners. Differences from the verified generic plugins for the Tuya platform:
Meaco specificity/discoverability: accessories show as Meaco, with the model Tuya reports.
Sleep mode: Meaco's sleep datapoint is exposed as a HomeKit switch. The generic plugin doesn't support it, and its deviceOverrides can't add it.
Targeted discovery: only Meaco units are picked up from a mixed Tuya account, with settings detected per unit. A "Discover devices" button in the plugin settings fills in the device list and shows every detected setting for review before saving.
Dedicated overrides and configuration specific to this appliance type in the user config.
Dependencies: homebridge must only be in devDependencies (not dependencies, optionalDependencies, bundledDependencies, or peerDependencies — npm auto-installs peer deps)
🟢 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.4.0
Package JSON: initializer function found
NPM Package: has not been deprecated
GitHub Repo: version in package.json (v1.3.0) matches NPM version (v1.3.0)
Config Schema JSON: exists and is valid JSON
Config Schema JSON: contains valid JSON Schema
Config Schema JSON: schema has valid type property
Config Schema JSON: schema has valid properties for object type
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: hap-nodejs is not declared as a runtime/peer/bundled dependency
Security: no known vulnerabilities in dependencies
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: accesses environment files in dist/tuya/pulsarClient.js
ℹ️ Check Details
These checks were run against v1.3.0 of the plugin.
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.
Interested in getting a @homebridge-plugins/ scope for your plugin? See our Homebridge Scoped Plugins program.
If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our Homebridge Plugins organization.
Don't forget to join the official Homebridge Discord server, where plugin developers can get tips and advice from other developers and the Homebridge project team in the #plugin-development channel!
As a verified plugin, you can request a channel in the Discord server to discuss your plugin with users and other developers. Just ask in the #plugin-development channel.
Thank you for your contribution to the Homebridge community.
One optional thought: engines.homebridge is set to ^2.0.0, so anyone still on Homebridge v1 can't install it. If the plugin works on v1 too, widening it to ^1.8.0 || ^2.0.0 would open it up to them.
Activity
github-actions commentedon Oct 22, 2026
🔴 Failed Checks
homebridgemust only be indevDependencies(notdependencies,optionalDependencies,bundledDependencies, orpeerDependencies— npm auto-installs peer deps)🟢 Passed Checks
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin'keywordsdeclare the supported transports ('supports-hap'and/or'supports-matter')'preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 22engines.nodeproperty is compatible with Node 24engines.homebridgeproperty is compatible with Homebridge 2.4.0typepropertypropertiesfor object typepluginAliaspluginAliasmatches the platform/accessory registered in codepluginTypeis set to'platform'nameschema propertyhap-nodejsis not declared as a runtime/peer/bundled dependency🔍 For Manual Review
The following items were detected and require manual review. We understand that these items may be false positives.
ℹ️ Check Details
v1.3.0of the plugin.📋 Next Steps
/checkon this issue to run the checks again — your request will not move forward until the checks are re-run.package.jsonandconfig.schema.jsonfiles, don't forget to publish a new version to NPM.chore: rename Pulsar client env option to channel
maubergine commentedon Oct 22, 2026
/check
github-actions commentedon Oct 22, 2026
🟢 Passed Checks
homepageexistsbugs.urlexists and seems a valid URLkeywordsexist and contain'homebridge-plugin'keywordsdeclare the supported transports ('supports-hap'and/or'supports-matter')'preinstall'inscriptsis not present'install'inscriptsis not present'postinstall'inscriptsis not presentengines.nodeproperty is compatible with Node 22engines.nodeproperty is compatible with Node 24engines.homebridgeproperty is compatible with Homebridge 2.4.0typepropertypropertiesfor object typepluginAliaspluginAliasmatches the platform/accessory registered in codepluginTypeis set to'platform'nameschema propertyhomebridgeis not declared as a runtime/peer/bundled dependencyhap-nodejsis not declared as a runtime/peer/bundled dependencyℹ️ Check Details
v1.3.1of the plugin.https://openapi.tuyaeu.com/v1.0/tokenMethods:
GET| Count:2| Scenarios: full config, network resilience📋 Next Steps
All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.
verify: homebridge-meaco
github-actions commentedon Oct 24, 2026
Congratulations! Your plugin has been verified!
You can now add one of the Verified by Homebridge badges to your plugin's README:
Your plugin is now also eligible to display a ❤️ Donate button on its tile in the Homebridge UI. See https://github.com/homebridge/homebridge/wiki/Donation-Links for instructions.
Interested in getting a
@homebridge-plugins/scope for your plugin? See our Homebridge Scoped Plugins program.If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our Homebridge Plugins organization.
Don't forget to join the official Homebridge Discord server, where plugin developers can get tips and advice from other developers and the Homebridge project team in the #plugin-development channel!
As a verified plugin, you can request a channel in the Discord server to discuss your plugin with users and other developers. Just ask in the #plugin-development channel.
Thank you for your contribution to the Homebridge community.
bwp91 commentedon Oct 24, 2026
Hi @maubergine, your plugin is now verified!
One optional thought:
engines.homebridgeis set to^2.0.0, so anyone still on Homebridge v1 can't install it. If the plugin works on v1 too, widening it to^1.8.0 || ^2.0.0would open it up to them.Thanks for contributing to Homebridge!