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

Lovelace Cover Card icon logic is reversed #5627

Closed
3 tasks done
reisub opened this issue Apr 25, 2020 · 5 comments
Closed
3 tasks done

Lovelace Cover Card icon logic is reversed #5627

reisub opened this issue Apr 25, 2020 · 5 comments
Labels
Bug Current Bug in UI - Extra Attention

Comments

@reisub
Copy link

reisub commented Apr 25, 2020

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.

The problem

When using the cover card for my blinds, the button logic is reversed.
For example, when I press the down button:

  • the up button is disabled
  • the icon on the left side indicates that the cover is going up

For the up button it's again reverse:

  • the down button i disabled
  • the icon on the left side indicated that the cover is going down

Here is a gif of the issue on my Android device:
home-assistant-cover-card

Expected behavior

I expect that then I press the up or down button that the pressed button is disabled while the blinds are running and that the icon indicator displays the correct direction.

Steps to reproduce

  1. Press up or down on the cover card
  2. Observe changes to UI

Environment

I see the same behavior both in Firefox and inside the Home Assistant Android app.

  • Home Assistant release with the issue: Home Assistant 0.108.9, Frontend version: 20200407.2 - latest
  • Last working Home Assistant release (if known): unknown
  • Browser and browser version: Firefox 75 / Home Assistant Android app 1.8.0-144 on Android 10
  • Operating system: macOS / Android

Problem-relevant configuration

Javascript errors shown in your browser console/inspector

Additional information

The cover card is controlling a Shelly 2.5 device which is hooked up to motorized window blinds.

@reisub reisub added the Bug Current Bug in UI - Extra Attention label Apr 25, 2020
@stale
Copy link

stale bot commented Jul 25, 2020

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check 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.

@stale stale bot added the stale label Jul 25, 2020
@reisub
Copy link
Author

reisub commented Jul 26, 2020

I've been updating regularly and this is still an issue in the latest release.

@stale stale bot removed the stale label Jul 26, 2020
@bramkragten
Copy link
Member

What integration is providing the cover entities and what is the state in the different conditions?

@reisub
Copy link
Author

reisub commented Jul 27, 2020

@bramkragten the cover entities are provided by ShellyForHASS.

I've just now realized that these don't all behave the same, though. I have three of these cover cards, and two of those have the reversed icon logic I described - but one has the correct icon logic.

I have a hunch that this is connected to the shelly web interface for managing each relay. In the web interface, you can select a checkbox to reverse button logic to be able to match how the wires are connected to the physical switches. So this may indeed be a bug within ShellyForHASS.

I'll have to investigate a bit more once I'm back home.

Sorry for confusion, if I had noticed this sooner I would have opened a task in the correct repo - feel free to close if you agree with the conclusion.

@bramkragten
Copy link
Member

That seems like a possible explanation, you can open a new issue if you think the problem is in the frontend anyway.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Current Bug in UI - Extra Attention
Projects
None yet
Development

No branches or pull requests

2 participants