Evidence at a glance #
Based on the linked sources. The author's reported result and independent confirmation are separate checks.
- AI involvement
- Reported models: Claude Opus 5.5, Claude Sonnet 5.5. Tools: ioBroker, Node.js, TypeScript. The writeup below describes the work attributed to AI.
- Reported result
- Research. This is the directory's source-based outcome classification.
- Independent confirmation
- Not reported.
- Human work and limitations
- The adapter is explicitly noted as not tested against a physical vehicle. Users are advised to consult the provided documentation for test plans and known limitations.
Original sources
What was done #
An unofficial ioBroker adapter for BYD vehicles using reverse-engineered cloud interfaces. It supports telemetry and remote commands but has not been tested against a physical car.
The iobroker.byd-vehicle project is an unofficial ioBroker adapter designed to interface with BYD vehicles via the manufacturer's cloud. The adapter utilizes reverse-engineered cloud interfaces, including protocol knowledge and Bangcle tables sourced from jkaberg/pyBYD. The implementation features a vehicle manager, per-VIN schedulers, and an opt-in remote command system. The adapter was developed with assistance from Claude Opus 5.5 and Claude Sonnet 5.5, as credited in the commit history. While the adapter includes unit tests with fixtures and has been verified against golden vectors and an in-process fake BYD cloud, the README explicitly documents that it has not been tested against a physical car. Known limitations include the inability to perform certain actions like battery health (SoH) reporting or stopping a charge, as the cloud call for the latter is a known no-op. The adapter manages command lifecycles through states such as pending, sent, acknowledged, succeeded, failed, timed_out, unknown, or rejected, with specific logic to handle transport failures.