device_request.yaml
device_request.yaml
| Name | About | Labels | Assignees |
|---|---|---|---|
| New device support | Request support for an EcoFlow device that isn't listed as supported yet | new device |
Thanks for helping expand device coverage! Please skim the wiki first:
- Requesting Support for New Devices
- overall flow for getting a new device supported.
- Providing Diagnostics Data
- how to capture the diagnostics file we need. Diagnostics are safe to share
publicly - all potentially sensitive data is AES encrypted.
- how to capture the diagnostics file we need. Diagnostics are safe to share
Since v0.6.0 you can add an unsupported device through the integration in
diagnostic-collection mode, exercise its features, and attach the resulting file
here. That's almost always the fastest path to getting the device supported.
If you've already built a draft PR (vibe-coded or otherwise), link it below - but
please read the
AI-assisted contributions
section of the contributing guide first so you know what to expect.
Full marketing name (e.g. "Delta 3 Pro", "Wave 3", "River 2 Max").
Visible in the EcoFlow app under device settings / info. Leave blank if you
can't find it.
First 4 characters of the device's serial number - the integration uses
this to recognise the device family. Please don't paste the full SN.
Paste a note here (e.g. "attached as diagnostics.json") and drag-and-drop the
file into the main issue body after submitting.
For the most useful capture, exercise as many features as you can while collecting
- charge, discharge, toggle AC / DC ports, plug in solar, etc. - so the dump
contains as many populated fields as possible.
Which sensors and controls do you most want to see supported for this device?
This helps prioritise if the protobuf schema is large.
Link to a draft / WIP pull request if you've started one.
Related links (Discord threads, forum posts, vendor docs), similar devices that
are already supported and might share a protocol, screenshots of the EcoFlow app,
etc.