Sourced from homebridge's releases.

v2.0.1

Changes

• docs: add CLAUDE.md to repo
• feat: expose hap flag on child bridge metadata
• chore: dependency updates
• fix: disable hap publishing on child bridges
• fix: drop legacy request type aliases removed in matter v0.17.x
• fix: keep accessory listeners attached during teardown

Homebridge Dependencies

• @homebridge/hap-nodejs @ v2.1.5

v2.0.0

⚠️ Breaking Changes

• For Users:

  • Before upgrading, you will want to ensure that the plugin(s) you are using are compatible with this new version of Homebridge. If you are unsure, see the link below or open an issue with the developer of your plugin(s) in question.
  • Node.js v18 and v20 are no longer supported. Homebridge v2 requires Node.js v22 or v24.

• For Plugin Developers:

  • HAP-NodeJS rename + major upgrade. The dependency was renamed from hap-nodejs to @homebridge/hap-nodejs and bumped from 0.14.x to 2.x. Plugins importing directly from hap-nodejs must update both the package name and adjust to the v2 API. The recommended path is to import HAP types from homebridge (which re-exports them) rather than depending on @homebridge/hap-nodejs directly.
  • ESM-only. The published package is now ESM ("type": "module"). Plugins authored as CommonJS that load homebridge via require() will not work; use import syntax. Plugins must publish ESM (or dual ESM/CJS) builds.
  • Output directory renamed lib/ → dist/. Plugins doing dirty-imports like homebridge/lib/api must switch to the public exports (import { API } from 'homebridge').
  • bin/homebridge → bin/homebridge.js. The bin entry now includes the .js extension (ESM requires it). The npm-managed homebridge shim is unaffected; only hardcoded paths to the script need updating.
  • Legacy deprecation cleanup (#3648). The following were removed in v2:
    • Module-level withPrefix, setDebugEnabled, setTimestampEnabled, forceColor exports from homebridge. Use Logger.withPrefix(...), Logger.setDebugEnabled(...), etc. on the Logger class.
    • PlatformAccessory.reachable, PlatformAccessory.updateReachability, PlatformAccessory.getServiceByUUIDAndSubType, PlatformAccessory.configureCameraSource. Use getServiceById and standard HAP camera registration patterns.
    • API.publishCameraAccessories. Use API.publishExternalAccessories (this is what the deprecated method delegated to internally).
    • HomebridgeConfig.mdns field is no longer forwarded to child bridges and is ignored. Use bridge.advertiser instead.

• Please visit the following link to learn more about the changes and how to prepare:

  • Updating-To-Homebridge-v2.0

Added

• set debug -D setting per child bridge
• feat: matter implementation
  • fix: matter fix [1] - matter cache getter (@​talrhv)
  • fix: matter fix [2] - various fixes
  • fix: matter fix [3] - combined devices
  • fix: matter fix [4] - general fixes
  • fix: matter fix [5] - expose WaterValve device (#3909) (@​donavanbecker)
  • fix: matter fix [6] - crash when bridge bind is set (#3910) (@​gtalusan)
  • fix: matter fix [7] - fix level control for non-lighting devices
  • fix: add powerSource to clusterNames and ClusterStateMap (#3912) (@​gtalusan)
  • fix: enable Rechargeable feature for PowerSource cluster when batChargeState is provided (#3914) (@​gtalusan)
  • fix: remove API event listeners in Matter manager teardown (#3915) (@​gtalusan)
  • fix: remove stateChange/commissioning listeners from MatterServer on teardown (#3916) (@​gtalusan)

... (truncated)

Sourced from homebridge's changelog.

v2.0.1 (2026-05-05)

Changes

• docs: add CLAUDE.md to repo
• feat: expose hap flag on child bridge metadata
• chore: dependency updates
• fix: disable hap publishing on child bridges
• fix: drop legacy request type aliases removed in matter v0.17.x
• fix: keep accessory listeners attached during teardown

Homebridge Dependencies

• @homebridge/hap-nodejs @ v2.1.5

v2.0.0 (2026-05-04)

⚠️ Breaking Changes

• For Users:

  • Before upgrading, you will want to ensure that the plugin(s) you are using are compatible with this new version of Homebridge. If you are unsure, see the link below or open an issue with the developer of your plugin(s) in question.
  • Node.js v18 and v20 are no longer supported. Homebridge v2 requires Node.js v22 or v24.

• For Plugin Developers:

  • HAP-NodeJS rename + major upgrade. The dependency was renamed from hap-nodejs to @homebridge/hap-nodejs and bumped from 0.14.x to 2.x. Plugins importing directly from hap-nodejs must update both the package name and adjust to the v2 API. The recommended path is to import HAP types from homebridge (which re-exports them) rather than depending on @homebridge/hap-nodejs directly.
  • ESM-only. The published package is now ESM ("type": "module"). Plugins authored as CommonJS that load homebridge via require() will not work; use import syntax. Plugins must publish ESM (or dual ESM/CJS) builds.
  • Output directory renamed lib/ → dist/. Plugins doing dirty-imports like homebridge/lib/api must switch to the public exports (import { API } from 'homebridge').
  • bin/homebridge → bin/homebridge.js. The bin entry now includes the .js extension (ESM requires it). The npm-managed homebridge shim is unaffected; only hardcoded paths to the script need updating.
  • Legacy deprecation cleanup (#3648). The following were removed in v2:
    • Module-level withPrefix, setDebugEnabled, setTimestampEnabled, forceColor exports from homebridge. Use Logger.withPrefix(...), Logger.setDebugEnabled(...), etc. on the Logger class.
    • PlatformAccessory.reachable, PlatformAccessory.updateReachability, PlatformAccessory.getServiceByUUIDAndSubType, PlatformAccessory.configureCameraSource. Use getServiceById and standard HAP camera registration patterns.
    • API.publishCameraAccessories. Use API.publishExternalAccessories (this is what the deprecated method delegated to internally).
    • HomebridgeConfig.mdns field is no longer forwarded to child bridges and is ignored. Use bridge.advertiser instead.

• Please visit the following link to learn more about the changes and how to prepare:

  • Updating-To-Homebridge-v2.0

Added

• set debug -D setting per child bridge
• feat: matter implementation
  • fix: matter fix [1] - matter cache getter (@​talrhv)
  • fix: matter fix [2] - various fixes
  • fix: matter fix [3] - combined devices
  • fix: matter fix [4] - general fixes
  • fix: matter fix [5] - expose WaterValve device (#3909) (@​donavanbecker)
  • fix: matter fix [6] - crash when bridge bind is set (#3910) (@​gtalusan)
  • fix: matter fix [7] - fix level control for non-lighting devices
  • fix: add powerSource to clusterNames and ClusterStateMap (#3912) (@​gtalusan)
  • fix: enable Rechargeable feature for PowerSource cluster when batChargeState is provided (#3914) (@​gtalusan)

... (truncated)

• bd78497 v2.0.1
• ae1e74e fix: keep accessory listeners attached during teardown
• 6b51744 fix: drop legacy request type aliases removed in matter v0.17.x
• 5dbce20 fix: disable hap publishing on child bridges
• 35b1246 chore: dependency updates
• 12dd7e4 feat: expose hap flag on child bridge metadata
• 40964b1 docs: add CLAUDE.md to repo
• fc54b4d v2.0.0
• cc90551 fix: update changelog for 2.0 release
• b92fe91 docs: regenerate typedoc docs
• Additional commits viewable in compare view

This version was pushed to npm by GitHub Actions, a new releaser for homebridge since your current version.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions