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

Added ll_notify in the Lovelace section #270

Closed
wants to merge 1 commit into from
Closed

Conversation

rr326
Copy link

@rr326 rr326 commented Feb 12, 2021

Note - ll_notify is a component but it adds front-end functionality just like a card, so I think it should be listed in the Lovelace section, even though technically not a card.

Describe the proposed change

ll_notify is a component but it adds front-end functionality just like a card, so I think it should be listed in the Lovelace section, even though technically not a card. I'm afraid that if listed as a component, front-end users won't see it.

Why awesome? Once you install in the backend as a component, you can have any button, script, automation, whatever trigger a good looking notification / toast on the front end. And it's fully configurable - different colors, auto-clear timing, etc. It's pretty awesome.

The link

https://github.com/rr326/ha_ll_notify

The annoying "I agree" thing

PRO TIP! Don't check the boxes right now! Open the PR first, and it will allow you actually to check the boxes using simple mouse clicks.


Anyone who agrees with this pull request could vote for it by adding a 👍 to it, and usually, the maintainer will merge it when votes reach significant numbers.

Note - ll_notify is a *component* but it adds front-end functionality just like a card, so I think it should be listed in the Lovelace section, even though technically not a card.
@frenck
Copy link
Owner

frenck commented Feb 12, 2021

Please read the contribution guidelines.

@frenck frenck closed this Feb 12, 2021
@rr326
Copy link
Author

rr326 commented Feb 12, 2021

I did and I'm not sure which is wrong.

Oh - is it because this is new and "not widely recommended"?

Totally fair. I'll repost in the future if appropriate.

@frenck
Copy link
Owner

frenck commented Feb 12, 2021

And self-promotion 😉

The combination of both is a bit too much

@rr326
Copy link
Author

rr326 commented Feb 12, 2021

@frenck ok, maybe that’s a but much. I guess you, perhaps rightly, see your list as a definitive curated guide to find the cream of the crop. Fair enough.

I thought it was “check here for custom components and cards”.

I get no $ or fame if I help people out by publishing my work. I was just trying to help.

@frenck
Copy link
Owner

frenck commented Feb 12, 2021

I get no $ or fame if I help people out by publishing my work. I was just trying to help.

Same.

@rr326
Copy link
Author

rr326 commented Feb 12, 2021 via email

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

Successfully merging this pull request may close these issues.

None yet

2 participants