EcoFlow Delta 3

… RIVER family looks simply unmapped rather than broken. Two things that might help: 1. Map the `R655` prefix. The RIVER 3 is the same generation as the DELTA 3, so the `delta3` parsers may already fit; a `DEVICE_TYPE_RIVER3` reusing them would be a reasonable first attempt. 2. Independently of RIVER support: the options flow lists every device the cloud account returns, including ones the integration cannot handle. Greying out or flagging unsupported devices there would avoid the "ticked but silent" state I ran into. ### Alternatives Considered _No response_ ### Additio

Excerpt saved from GitHub on 2026-10-23.