new-device-support

To add Eufy Security device support, gather the device name, model, raw properties, and firmware version, then map those properties to existing constants across the eufy-security-client and homebridge-eufy-security repositories. This workflow automates planning, implementing, building, and submitting cross-repo pull requests.

Mapping raw Eufy device properties involves extracting device details from sources like GitHub issues and translating them into existing client and plugin constants. This workflow structures the property mapping during the implementation phase, adjusting code across both repositories to ensure correct device integration.

Yes, you can automate cross-repo pull requests for Eufy Homebridge plugins by following a phase-driven workflow that branches, commits, and opens scoped PRs for both the client and plugin. It ensures changes are properly separated and synchronized across the eufy-security-client and homebridge-eufy-security repositories.

Yes, running build and lint checks is required when adding Eufy device support to ensure correctness across the eufy-security-client and homebridge-eufy-security codebases. The workflow explicitly includes a build and lint phase to verify code quality before finalizing Git operations and pull requests.

Planning code changes for a new Eufy device requires listing files to modify, dependencies, and required changes using an explicit planning framework. This workflow generates a detailed implementation plan that scopes adjustments across both the eufy-security-client and homebridge-eufy-security repositories before coding begins.

To start integrating a new Eufy device type, you need the device name, model, device type, raw properties, firmware version, and any available references. Gathering this information is the first phase of the workflow, providing the necessary data to map properties and plan code modifications.