Incorrect x10 Scaling for Delta Pro DC Car Out Power (mppt.carOutWatts) #455
Comments
|
Hey, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Environment
Affected API Value: mppt.carOutWatts
Description
While monitoring my EcoFlow Delta Pro via the hassio-ecoflow-cloud integration, I've noticed a consistent discrepancy with the DC Car Output Power reading. The value reported by the integration sensor is always exactly 10 times the value displayed in the official EcoFlow mobile app for the same output.
For example:
When the EcoFlow app shows the car port drawing 6W, the integration sensor reports 60W.
When the app shows 7W, the integration sensor reports 70W.
Analysis:
According to the official EcoFlow API documentation for the Delta Pro, the mppt.carOutWatts field should report power in Watts (W):
https://developer-eu.ecoflow.com/us/document/deltapro
However, the observed 10x scaling strongly suggests that the API might actually be providing this specific value in deciwatts (dW), contrary to the documentation.
Code Reference:
The current code (v1.3.0-beta4) defines the sensor using OutWattsSensorEntity, which assumes the input value is already in Watts and applies no scaling:
https://github.com/tolwi/hassio-ecoflow-cloud/blob/v1.3.0-beta4/custom_components/ecoflow_cloud/devices/public/delta_pro.py#L93-L95
Request
Could other Delta Pro users confirm if they are seeing this same x10 discrepancy for the DC Car Output Power sensor? This would help verify if it's a general issue with the API response for this field or specific to certain setups.
In any case i would be open to do a PR, and to get in touch with Ecoflow support to see if that docs needs an update. The solution might be as simple as changing the sensor definition in delta_pro.py to use the existing DeciwattsSensorEntity class instead. This class correctly handles values provided in deciwatts by dividing them by 10.
The text was updated successfully, but these errors were encountered: