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

Removed toast (entities turn on/off and OK service calls) #2822

Merged
merged 3 commits into from Feb 23, 2019

Conversation

yosilevy
Copy link
Contributor

Still will show on service error

@iantrich
Copy link
Member

yeah, this is needed; but perhaps it should be configurable?

@yosilevy
Copy link
Contributor Author

Discussed with @balloob before implementation and was decided that opt in/out is not required.

@iantrich
Copy link
Member

fine by me as long as you guys have considered it 👍

Copy link
Member

@iantrich iantrich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove L18 import computeStateName per the linter and this should be good to go, I think.

const name = names.join(", ");
if (service === "turn_on" && serviceData.entity_id) {
message = this.hass.localize(
"ui.notification_toast.entity_turned_on",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove the translation strings too

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@iantrich iantrich merged commit dede819 into home-assistant:dev Feb 23, 2019
@ghost ghost removed the in progress label Feb 23, 2019
@yosilevy yosilevy deleted the toast-notification-supression branch February 24, 2019 03:38
@balloob balloob mentioned this pull request Feb 28, 2019
@gavinwoolley
Copy link

I have been debugging for a while why this had vanished till I noticed this PR.
I found this feature really useful . So I knew I'd actually pressed the button. Some switches take a few seconds to respond and change state etc.
Will there be any chance you could add a toggle to turn on/off?

@yosilevy
Copy link
Contributor Author

Well it vanished because it is rarely useful and just makes the UI technical and not really simple user friendly. As for adding it back - @balloob ?

@balloob
Copy link
Member

balloob commented May 3, 2019

We should not add it back globally. We can consider adding something back on a per-button case.

@balloob
Copy link
Member

balloob commented May 3, 2019

Generally, switches you will see that they switch. We have also been adding haptic events, which we can start using on mobile phones. https://developer.mozilla.org/en-US/docs/Web/API/Navigator/vibrate

@gavinwoolley
Copy link

I have a lot of scripts which send IR command's to TVs etc . They don't highlight when active. It was just nice to get some positive feedback that I had pressed the button and the command was sent.
Haptic events sound perfect. Would like to try that.

@iantrich
Copy link
Member

iantrich commented May 3, 2019

@gavinwoolley they are currently only available in the iOS companion app beta release (to my knowledge)

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

Successfully merging this pull request may close these issues.

None yet

5 participants