This guide explains how to add, remove, and configure your EcoFlow devices within Home Assistant using the EcoFlow Cloud integration.
To add a new device to an existing integration entry, you must use the Reconfigure option.
Steps:
- In Home Assistant, go to Settings > Devices & Services.
- Find the EcoFlow Cloud integration card.
- Click the three dots (vertical ellipsis) menu on the integration card.
- Select Reconfigure.
- The integration will authenticate (using your existing API keys or App credentials).
- You will be presented with a menu:
- Add device
- Remove device
- Finish
- Select Add device and click Next.
- Follow the prompts to select and confirm the new device.
Removing a device is also done via the Reconfigure menu.
Steps:
- In Home Assistant, go to Settings > Devices & Services.
- Find the EcoFlow Cloud integration card.
- Click the three dots (vertical ellipsis) menu.
- Select Reconfigure.
- In the menu, select Remove device and click Next.
- Choose the device you want to remove from the dropdown list.
- Click Submit.
The device and all its associated entities will be removed from Home Assistant.
Use the Configure button to adjust specific settings for your devices, such as refresh intervals and charging limits.
Steps:
- Go to Settings > Devices & Services.
- Find the EcoFlow Cloud integration card.
- Click the Configure button.
- You will be prompted to Select device. Choose the device you wish to adjust and click Submit.
- You will see a form with the following options:
Configuration Options:
- Charging power slider step:
- Defines the increment size for the charging power slider (e.g., changing power by 10W or 50W steps).
- Data refresh period (sec):
- Controls how often Home Assistant updates the device entities with the latest data received from the cloud.
- Note: This integration does not poll the device. Data is pushed by the cloud via MQTT, and this setting only determines how frequently Home Assistant reflects the latest received values.
- Diagnostic mode:
- Enables the collection of raw MQTT messages (commands, replies, status) in memory.
- This data is included when you download the integration diagnostics, which is useful for debugging issues.
- Note: This does not force the creation of additional entities, it only affects the "Download Diagnostics" feature.
- Assume offline timeout (sec):
- Time in seconds after which the device status changes to
assume_offlineif no new data is received. - After 3x this duration without data, the status changes to
offline. - Note: For some devices, this state triggers sending a quota message to attempt to recover data reception or obtain the real device status.
- Time in seconds after which the device status changes to
- Verbose status mode:
- Enables the display of the intermediate
assume_offlinestatus in the Main Status Entity. - If disabled (default), the status will remain
onlineduring the assume offline timeout, and then switch directly tooffline. - If enabled, the status will change to
assume_offlineas soon as the initial data timeout is reached.
- Enables the display of the intermediate
Click Submit to save your changes. The integration will reload with the new settings.