homebridge / homebridge/plugins

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

Open
#1,063 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

awaiting-final-review request-verification
Dominant language
TypeScript
Stars
369
Forks
24
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing verified-plugins.json, especially the existing Ambient Weather entry near line 96, then inspect the submitted plugin repository and its verification evidence. Compare the fork with the existing verified plugin and the stated requirements, including installation, configuration, error handling, and feature overlap. Done means reaching a documented verification decision for this submission.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.