Skip to content
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

[Feature Request]: Prevent unavailable values #922

Closed
2 tasks done
gimmel opened this issue Feb 2, 2025 · 2 comments
Closed
2 tasks done

[Feature Request]: Prevent unavailable values #922

gimmel opened this issue Feb 2, 2025 · 2 comments
Labels
enhancement New feature or request

Comments

@gimmel
Copy link

gimmel commented Feb 2, 2025

Describe your feature request

Although my inverter is located directly next to a WLAN access point, all values are often undefined for a short time. I would like to have the option of bridging such data pauses: Instead of undefined, the last value should then be output.

Or am I the only one with this "undefined" phases?

Proper usage

  • I confirm that this is not a bug report or support request
  • I confirm that this feature request is within the stated scope of the integration
@gimmel gimmel added the enhancement New feature or request label Feb 2, 2025
@wlcrs
Copy link
Owner

wlcrs commented Feb 2, 2025

If the value cannot be retrieved due to a bad connection, then the only correct value is 'unavailable'. Returning the last value is factually incorrect and would prevent users from detecting that the value is outdated.

@wlcrs wlcrs closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2025
@gimmel
Copy link
Author

gimmel commented Feb 3, 2025

From a device perspective, you are of course absolutely right. But from the user interface point of view, it's not nice when the solar values jump to “unavailable” in between and destroy the clean UI.
I assumed that this was a bug in the Huawei inverters.

But of course this also happens with other devices and sometimes I create a template sensor (sensor.value_last) for this. With the Huawei integration, however, there are a lot of values that are then saved twice.

However, it would probably make more sense to incorporate this at HomeAssistant level so that sensors can be used for user interfaces in such a way that they always output the last valid value, perhaps with a checkbox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants