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

Remote Start Binary sensor and Remote Start Button mutually exclusive - button is unavailable and at the same time Sensor is ON #805

Open
anthonykeane opened this issue Oct 4, 2024 · 1 comment

Comments

@anthonykeane
Copy link

anthonykeane commented Oct 4, 2024

Describe the bug

Running the Washer and not pressing the remote start sets the

binary_sensor.front_load_washer_remote_start == on

at the same time

button.front_load_washer_remote_start == unavailable

Remote Start Binary sensor and Remote Start Button should be mutually exclusive - button cannot be unavailable and at the same time Sensor is ON - right?

Expected behavior
Turning on the washer does not change the Remote Start sensor or button

Screenshots
image

blank black is unavailable

Environment details:

  • Environment Ubuntu, hassio docker
  • Home Assistant version installed: 2024.10
  • Component version installed: ollo69 ha-smartthinq-sensors 0.39.2
  • Last know working version: NONE
  • LG device type and model with issue: F_V__Y___W.B__QEUK-FL (WASHER) by LG Firmware: clip_hna_v1.9.198
  • LG devices connected (list): Washer, Dryer, Fridge

Output of HA logs
Paste the relavant output of the HA log here.


Additional context
Steps to reproduce

  1. Turn on the Washer from its front panel
  2. select different wash mode, not sure if this is needed but it what I did, I chose Turbo39 from Cotton
  3. Press Start
  4. When the washer is running the pause button becomes available and the remote start binary_sensor.front_load_washer_remote_start changes from off to on

resulting in the above picture

@anthonykeane
Copy link
Author

Would be great if the entities had labels that could differentiate them, the ux shows them both as the same label

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

No branches or pull requests

1 participant