-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delta Pro: AC input sensors' data wrong in pass-through mode #25
Comments
I started noticing something similar after updating to the latest version. Since I am using my River's as I've been using a check of AC input powered and this worked fine but since updating to the latest version - this now keeps changing and thus notifying me that AC input power has dropped when it has not so seems something is up with this. Thanks |
On the Delta Pro it stays constantly off once the device goes into pass-through mode (I did not update the firmeware yet though) When I compared the three debug files I took today the culprit seems to be the ac_in_type: Once charging has finished, the "ac_in_type" reads "0" which is the same as when the unit is unplugged from AC, even though AC input (ac_in_power) has a positive value. |
I have previously addressed this in the RIVER series so that you can have input entities in AC and DC respectively. However, that did not work well and even caused problems with DELTA. We are going to revert this and remove the AC/DC input entities from the RIVER series, leaving only the total input entities (the DELTA series will continue to have AC/DC input entities). |
That should work - while there would be valid use cases for input on AC and DC - seems that this is problematic so total is still fine as that will still detect no input. |
@vwt12eh8 Thanks, the "AC input" (WattsEntity) readout is now fine, but the binary sensor "AC input" still displays "Off". I guess this is because the device API returns "ac_in_type": 0 also in pass-through mode. |
@golden-guy It seems to be a firmware spec that reports no input when charged to max. This was also the case with DC input. I would not recommend using this entity to determine if there is a real input or not. As an alternative, it would be more reliable to determine that there is an input if the AC input voltage is of a certain value (e.g. 10V or higher). |
Alright, that's fine. I will just use another entity then, as you have suggested. Thanks for your always great support! |
I noticed another issue with the AC input sensors' readout in bypass (pass-through) mode on my Delta Pro running hassio-ecoflow 2.2.2):
Once the battery is fully charged, and the unit switches to pass-through mode, the sensor values for AC are "Off" resp. "0 W", although the unit is still plugged on AC and passing on power to the active AC output. The AC output power is correctly displayed, as well as the "Total input" and "Total output".
As a side note: According to the activity log, the AC input was reset at the same time the Charging indicator changed to "Not charging" when the battery was full. The ac_in_power in the debug log looks correct in this case (and is aligned with the ac_out_power)
config_entry-ecoflow-b59e0ccb379fad5eff3c3280bd845a54_2.json.txt
The text was updated successfully, but these errors were encountered: