Verification Request: homebridge-meraki-mt-sensor-ng

Plugin Name

homebridge-meraki-mt-sensor-ng

Link To GitHub Repo

https://github.com/alexsannikov/homebridge-meraki-mt-sensor-ng

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

About the plugin

This plugin exposes Cisco Meraki MT sensor telemetry to HomeKit: temperature,
humidity, door (contact), CO2, and indoor air quality (score, PM2.5, TVOC)
sensors, polled via the official Meraki Dashboard API v1.

It is a maintained next-generation fork of the unmaintained
homebridge-meraki-mt-sensor (MIT), rewritten for current Homebridge:
dynamic platform with cached bridged accessories, Homebridge 1.8/2.0 support,
onGet handlers with HapStatusError, and a config schema for the settings UI.

Overlap with existing verified plugins

The only verified Meraki plugin is homebridge-meraki-control, which controls
Meraki Dashboard network/client settings (exposed as switches). It does not
expose MT environmental sensor readings, so the functionality does not overlap.

Requirements checklist

Dynamic platform: accessories are registered via registerPlatformAccessories,
restored from cache, and unregistered when removed from the config.
Runs on Node.js 22 and 24 (engines enforced), Homebridge 1.8+ and 2.x.
Installs cleanly and does not start unless configured; no post-install
scripts; no TTY or non-standard startup parameters required.
Implements the Homebridge Plugin Settings GUI (config.schema.json).
No analytics or tracking — the only outbound calls are to the Meraki API
configured by the user.
Writes nothing to disk.
All errors are caught and logged; read failures are reported to HomeKit as
SERVICE_COMMUNICATION_FAILURE.
Published to npm (latest: 2.1.0), GitHub releases with notes for every
version, issues enabled.

Note

The verification check script has recently been updated. If you believe any result below is incorrect (a false positive), please reply to this issue and let us know — it helps us tune the new checks.

🔴 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.
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: '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.1.0
Package JSON: initializer function found
NPM Package: has not been deprecated
GitHub Repo: version in package.json (v2.1.0) matches NPM version (v2.1.0)
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'
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 known vulnerabilities in dependencies
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

ℹ️ Check Details

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

📋 Next Steps

Please action these failures and then comment /check to run the checks again.
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.

/check

Both config schema issues are fixed in v2.1.1 (now published as latest): per-field boolean required flags replaced with object-level required arrays, and a top-level platform name property added.

Note

The verification check script has recently been updated. If you believe any result below is incorrect (a false positive), please reply to this issue and let us know — it helps us tune the new checks.

🟢 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: '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.1.0
Package JSON: initializer function found
NPM Package: has not been deprecated
GitHub Repo: version in package.json (v2.1.1) matches NPM version (v2.1.1)
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: homebridge is not declared as a runtime/peer/bundled dependency
Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
Security: no known vulnerabilities in dependencies
Security: no unsafe code patterns detected
Security: no privilege escalation attempts detected
Runtime: homebridge installed successfully
Runtime: no config - homebridge should start without plugin configuration and plugin should not load
Runtime: platform only - plugin should start with just platform property
Runtime: minimal required - plugin should start with minimal required configuration
Runtime: full config - plugin should start with comprehensive configuration
Runtime: network resilience - plugin should handle network failures without crashing
Runtime: plugin shuts down cleanly within 12s of SIGTERM
Runtime: plugin restarts cleanly without port conflicts
GitHub Repo: repository is public
GitHub Repo: repository is not archived
GitHub Repo: issues are enabled
GitHub Repo: contains releases

ℹ️ Check Details

These checks were run against v2.1.1 of the plugin.
Link to the run workflow: visit →.
External HTTP requests detected:
- 📡 https://api.meraki.com/api/v1/organizations/test-value/sensor/readings/latest
  Methods: 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-meraki-mt-sensor-ng

Congratulations! Your plugin has been verified!

You can now add one of the Verified by Homebridge badges to your plugin's README:

[![verified-by-homebridge](https://img.shields.io/badge/_-verified-blueviolet?color=%23491F59&style=flat&logoColor=%23FFFFFF&logo=homebridge)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

[![verified-by-homebridge](https://img.shields.io/badge/homebridge-verified-blueviolet?color=%23491F59&style=flat)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

[![verified-by-homebridge](https://img.shields.io/badge/homebridge-verified-blueviolet?color=%23491F59&style=for-the-badge&logoColor=%23FFFFFF&logo=homebridge)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)

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.

The Homebridge Team

Thanks for the plugin! All checks out — now verified. 🎉

Navigation Menu

Repository navigation

Verification Request: homebridge-meraki-mt-sensor-ng #1105

Plugin Name

Link To GitHub Repo

Plugin Icon (Optional)

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

The plugin successfully installs and does not start unless it is configured.

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

The plugin does not contain any analytics or calls that enable you to track the user.

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

More Information

About the plugin

Overlap with existing verified plugins

Requirements checklist

🔴 Failed Checks

🟢 Passed Checks

ℹ️ Check Details

📋 Next Steps

🟢 Passed Checks

ℹ️ Check Details

📋 Next Steps

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Verification Request: homebridge-meraki-mt-sensor-ng #1105

Description

Plugin Name

Link To GitHub Repo

Plugin Icon (Optional)

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

The plugin successfully installs and does not start unless it is configured.

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

The plugin does not contain any analytics or calls that enable you to track the user.

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

More Information

About the plugin

Overlap with existing verified plugins

Requirements checklist

Activity

github-actions commented on Jul 4, 2026

🔴 Failed Checks

🟢 Passed Checks

ℹ️ Check Details

📋 Next Steps

alexsannikov commented on Jul 4, 2026

alexsannikov commented on Jul 4, 2026

github-actions commented on Jul 4, 2026

🟢 Passed Checks

ℹ️ Check Details

📋 Next Steps

github-actions commented on Jul 12, 2026

bwp91 commented on Jul 12, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions