Installation

1. Search for "No-IP" on the plugin screen of Homebridge Config UI X.
2. Click Install.

Configuration

1. Login / create an account at https://noip.com/
   • If you haven't already you can also create your No-IP hostname here as well.

2. Type in your NoIP Username, Password, and Hostname into the Plugin Setting UI
3. Click Save
4. Restart Homebridge

Supported No-IP Features

• IPv4 Update.
• IPv6 Update.

Homebridge Matter Support & HAP Fallback

This plugin supports Homebridge v2.0+ with Matter API integration. When running on a Homebridge version that provides the Matter API and Matter is enabled in your config, the plugin will register devices using Matter. If Matter is unavailable or disabled, the plugin will automatically fall back to standard HAP (HomeKit Accessory Protocol) registration.

Key Points:

• Automatic Selection: The plugin chooses Matter or HAP at runtime based on your Homebridge environment and config options.
• Config Options: You can control Matter preference and enable/disable via the plugin config (preferMatter, enableMatter).
• No Manual Changes Needed: If you upgrade/downgrade Homebridge or change your config, the plugin will always select the best available platform.
• Tested Fallback: The fallback logic is fully tested to ensure reliability.

See the Changelog for details on Matter support and fallback improvements.

Contributing

This project uses GitHub Copilot to help manage contributions. Before submitting issues or requesting features, please follow these guidelines:

Issue Guidelines

1. Label Requirements: All issues must have one semantic versioning label before assignment to Copilot:

   • patch: Bug fixes (backward compatible)
   • minor: New features (backward compatible)
   • major: Breaking changes

2. Branch Strategy: All pull requests must target beta branches first:

   • beta-X.Y.Z for specific version releases
   • beta as a fallback if no version-specific branch exists
   • Only after beta testing should changes be merged to latest

Workflow

1. Create an issue using the provided templates
2. The issue will automatically be labeled based on the version impact you select
3. Assign the issue to @copilot
4. Copilot will create the appropriate beta branch if needed
5. Copilot will create a pull request targeting the beta branch
6. After review and testing, changes will be merged to the beta branch
7. Once ready, beta changes will be promoted to the latest branch for release