Skip to main content

Debug Mode

Enable plugin debug logging by turning on Homebridge debug mode so verbose output stays isolated per bridge.

How Debug Mode Works

The plugin no longer has its own debug setting. Debug logging is now tied directly to Homebridge, and it turns on only when Homebridge debug mode is enabled.

  • Homebridge controls it — There is no separate field in config.json to switch the plugin into debug mode.
  • Per-bridge isolation — Because logging follows Homebridge, output can be separated for each bridge you run.

Why It Changed

Earlier versions exposed a plugin setting to switch on debug mode. Over time that setting made resolving issues harder rather than easier.

The common failure was partial setup. Consumers would enable the plugin's debug mode but forget to also enable Homebridge debug mode, which left contributors without the detailed logs needed to reproduce and fix bug reports.

Tying debug logging to Homebridge removes that gap. A single switch now controls verbose output, so the logs attached to a bug report are complete.

Enabling Debug Mode

Turn on debug mode in Homebridge itself, then restart so the plugin picks up the new log level.

  • Homebridge UI — Enable debug mode from the Homebridge settings, then restart Homebridge.
  • Command line — Start Homebridge with its debug flag so verbose logging is active for the session.
bash
# Start Homebridge with debug logging enabled.
homebridge -D

Once Homebridge debug mode is active, the plugin emits its detailed logs alongside the rest of the Homebridge output.

tip

Enable debug mode before reproducing an issue so the captured logs include the full detail contributors need to resolve a bug report.

View on GitHub