Humidifier water_lacks or out_of_water not working properly

[luixal]

The problem

DISCLAIMER: this doesn't seem to be a buf in this integration, but a bug on VeSync side. Looking for a workaround.

I have an LUH-D301S-WEU humidifier. Everything works fine but the out of water warning. It get's triggered and the value changes, but only for less than a minute:

The entity attribute water_lacks seems to have the same value, as it reports false althouthg I haven't refilled it yet (I guess the bainery sensor takes it's value from this attribute). I've tried using this python library to check the value in VeSync's cloud and yes, it shows a false value.

I can fire a notification when this value changes, but I would like to show a message in a dashboard card when a refill is needed. Any simple workaround to get this?

I know I could create an input_boolean and trigger and automation that sets it to true and reset it manually (or when the water_tank_lifted changes to true). But not sure if something like this could be made directly in the integration as it offers that binary sensor.

Thanks!

What version of this integration has the issue?

1.3.0

What version of Home Assistant Core has the issue?

2023.11.0

Diagnostics

Diagnostics

{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.11.0",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.11.6",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Madrid",
    "os_name": "Linux",
    "os_version": "6.1.59",
    "supervisor": "2023.11.0",
    "host_os": "Home Assistant OS 11.1",
    "docker_version": "24.0.6",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "hacs": {
      "version": "1.33.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "tapo": {
      "version": "2.11.0",
      "requirements": [
        "plugp100==3.13.1"
      ]
    },
    "xiaomi_cloud_map_extractor": {
      "version": "v2.2.0",
      "requirements": [
        "pillow",
        "pybase64",
        "python-miio",
        "requests",
        "pycryptodome"
      ]
    },
    "browser_mod": {
      "version": "2.3.0",
      "requirements": []
    },
    "irrigation_unlimited": {
      "version": "2023.11.0",
      "requirements": [
        "crontab"
      ]
    },
    "tapo_control": {
      "version": "5.4.0",
      "requirements": [
        "pytapo==3.3.2"
      ]
    },
    "xiaomi_miot": {
      "version": "0.7.13",
      "requirements": [
        "construct>=2.10.56",
        "python-miio>=0.5.6",
        "micloud>=0.3"
      ]
    },
    "owlet": {
      "version": "0.1.1",
      "requirements": [
        "PyJWT",
        "gcloud",
        "sseclient",
        "requests_toolbelt"
      ]
    },
    "home_connect_alt": {
      "version": "0.7.0",
      "requirements": [
        "home-connect-async==0.7.14"
      ]
    },
    "vesync": {
      "version": "1.3.0",
      "requirements": [
        "pyvesync==2.1.10"
      ]
    },
    "webrtc": {
      "version": "v3.5.0",
      "requirements": []
    },
    "meross_cloud": {
      "version": "1.2.10",
      "requirements": [
        "meross_iot==0.4.6.0rc2"
      ]
    },
    "alarmo": {
      "version": "v1.9.13",
      "requirements": []
    }
  },
  "integration_manifest": {
    "domain": "vesync",
    "name": "VeSync",
    "codeowners": [
      "@markperdue",
      "@webdjoe",
      "@thegardenmonkey",
      "@vlebourl",
      "@tv4you2016"
    ],
    "config_flow": true,
    "dhcp": [
      {
        "hostname": "levoit-*",
        "macaddress": "*"
      }
    ],
    "documentation": "https://www.home-assistant.io/integrations/vesync",
    "iot_class": "cloud_polling",
    "issue_tracker": "https://github.com/vlebourl/custom_vesync",
    "requirements": [
      "pyvesync==2.1.10"
    ],
    "version": "1.3.0",
    "is_built_in": false
  },
  "data": {}
}

Home Assistant log

N/A

Additional information

No response

[github-actions]

'There hasn't been any activity on this issue recently. Is this issue still present?
Please make sure to update to the latest Home Assistant version and version of this integration to see if that solves the issue. Let us know if that works for you by adding a comment 👍.
This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.'