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

Add Stop Effect to Lights more-info dialog #3619

Closed
SeanPM5 opened this issue Sep 4, 2019 · 11 comments · Fixed by #3636
Closed

Add Stop Effect to Lights more-info dialog #3619

SeanPM5 opened this issue Sep 4, 2019 · 11 comments · Fixed by #3636
Assignees

Comments

@SeanPM5
Copy link
Contributor

SeanPM5 commented Sep 4, 2019

Description of problem:
You can turn on light effects from the more-info dialog for Lights, but there is no apparent way to turn these effects off. Seems that you have to turn the light off and then back on again, which is not obvious and can be a little confusing. Some examples of community posts referencing this: here, here, here.

It seems that sending effect: stop will stop the effect and restore your lights. I've tested this with Hue and it seems to work, but I am not 100% positive if this is a standard Home Assistant thing that all light platforms support?

I think that there should either be a "stop" option added inside of the dropdown when an effect is currently active like this (mockup 1):

stopeffectmock1

Or a stop button to the right of the "Effect" dropdown as pictured here (mockup 2):

stopeffectmock2

@balloob
Copy link
Member

balloob commented Sep 4, 2019

If we would go for a button, only show it if we know an effect is active. I think I prefer making it part of the dropdown.

@SeanPM5
Copy link
Contributor Author

SeanPM5 commented Sep 5, 2019

There is one minor discoverability issue with the dropdown idea however.

If the "stop effect" choice is hidden until an effect is active, the user doesn't see it when opening the dropdown menu and they wouldn't necessarily know it was added either because the dropdown closes immediately after they make their selection.

So if this is possible, maybe have the "show effect" option be visible in the dropdown at all times but just in an unselectable/disabled until there is an active effect? And it probably should be at the very bottom of the effect list too.

@dshokouhi
Copy link
Member

Maybe instead of "Stop Effect" we change it to "No Effect" and make that the default option?

@iantrich
Copy link
Member

iantrich commented Sep 5, 2019

I like "No Effect". Going to add that.

@iantrich iantrich self-assigned this Sep 5, 2019
@iantrich
Copy link
Member

iantrich commented Sep 6, 2019

Looked at the code and it is just a list of effects, so for now just going to have "stop" for now. It will not be hidden.

Edit: Changing my mind. Going to go with a button. That will be cleaner

@iantrich
Copy link
Member

iantrich commented Sep 6, 2019

I only have the demo light to play with for this but it has an effect of 'none'. Do yours not?

image

@dshokouhi
Copy link
Member

This is what I got:

Lightify:
image

Hue:
image

Limitlessled:
image

@iantrich
Copy link
Member

iantrich commented Sep 6, 2019

Can you check if there is an effect attribute after calling the turn_on with an effect of "stop"?

iantrich added a commit to iantrich/home-assistant-polymer that referenced this issue Sep 6, 2019
bramkragten pushed a commit that referenced this issue Sep 9, 2019
* Convert weather-forecast to LitElement

Part of #2095

Not sure how RTL works and how to apply it.

Also, thinking I should update if the forecast changes and not just the state. Input?

* Revert "Convert weather-forecast to LitElement"

This reverts commit e1893b0.

* Add stop effect button

Closes #3619

* address review comments

* cleanup
@BjoernPetersen
Copy link

BjoernPetersen commented Mar 3, 2020

As I understand the (partial) fix has been reverted in #3672, right? Could this issue be reopened then? I understand that there's no perfect solution for all devices right now, but having to power-cycle the light to turn off an effect is still annoying.

@zsarnett zsarnett reopened this Mar 3, 2020
@iantrich
Copy link
Member

iantrich commented Mar 3, 2020

I don't believe this is a frontend issue. The backend would have to change to have all integrations follow a similar method of stopping effects, if even possible before the frontend could support it.

@ghost
Copy link

ghost commented Mar 3, 2020

This issue was moved by iantrich to home-assistant/core#32446.

@ghost ghost closed this as completed Mar 3, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jul 6, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants