Verification Request: @bcourbage/homebridge-ambient-weather-sensors

[bcourbage]

Plugin Name

@bcourbage/homebridge-ambient-weather-sensors

Link To GitHub Repo

https://github.com/bcourbage/homebridge-ambient-weather-sensors

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

Homebridge plugin for Ambient Weather weather stations. Pulls sensor data via the official AWN REST API (or optionally the realtime WebSocket endpoint) and exposes temperature, humidity, solar radiation, CO2, and PM2.5/PM10 sensors to HomeKit. Supports multiple weather stations on a single account.

Relationship to the existing verified plugin. I'm aware that homebridge-ambient-weather-sensors (unscoped, by peledies) is currently in the verified-plugins list (line 96 of verified-plugins.json). This fork is submitted for verification because it adds Homebridge 2.x / HAP 2.x compatibility, without which the upstream verified plugin emits engine warnings and won't fully run on current Homebridge installations. That's the situation tracked in upstream issues #18 and #19, which have no current path to fix without this fork. The fork also adds several net-new features requested in Issues (see below). The base / overlapping functionality (temperature, humidity, solar radiation sensors) is the same as the verified upstream. That part is Deac Karns's work, preserved unchanged.

Disclosure: this is a soft fork of peledies/homebridge-ambient-weather-sensors. Original work, design, and most of the code are by Deac Karns. I forked it in May 2026 to add Homebridge 2.x / HAP 2.x compatibility after the upstream maintainer's activity went quiet in February 2025. Pull requests #21 (HB2 compat) and #22 (independent cache bug fix) against upstream remain open without response.

The fork adds beyond verified upstream v1.3.2: multi-station naming using AWN's info.name, opt-in WebSocket realtime data source via rt2.ambientweather.net, CO2 sensor (via AWN's AQIN-family co2_in_aqin and standalone co2 fields), PM2.5 and PM10 air quality sensors with EPA-bucket-derived AirQuality enum, password-masked API key fields in homebridge-config-ui-x, and a polling refactor (one platform-level timer instead of N per-accessory timers, which eliminates the parallel-fetch race against AWN's 1 req/s rate limit).

Attribution preserved. README and package.json funding field still direct support to Deac. NOTICE file at repo root records Apache 2.0 attribution. If upstream resumes and merges PRs #21/#22, this fork can be sunset.

Operations. Running in production on HB 2.0.2 / HAP 2.1.6 / Node 24.x. Automated release pipeline via GitHub Actions with npm provenance attestations.

[github-actions]

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

• Package JSON: homepage missing or does not start with https://
• Package JSON: more keywords apart from 'homebridge-plugin' should exist
• 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.
• GitHub Repo: should have issues enabled
• GitHub Repo: should contain releases

🟢 Passed Checks

• Installation: successfully installed
• Package JSON: bugs.url exists and seems a valid URL
• 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.0.2
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v1.4.2) matches NPM version (v1.4.2)
• 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 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

ℹ️ Check Details

• These checks were run against v1.4.2 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.

[bcourbage]

/check

[github-actions]

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.0.2
• Package JSON: initializer function found
• NPM Package: has not been deprecated
• GitHub Repo: version in package.json (v1.4.3) matches NPM version (v1.4.3)
• 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 v1.4.3 of the plugin.
• Link to the run workflow: visit →.
• External HTTP requests detected:
  • 📡 https://rt.ambientweather.net/v1/devices
    Methods: GET | Count: 4 | Scenarios: full config, minimal required, network resilience, platform only

📋 Next Steps

All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.