-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
PR #1393 provides unclear instructions #1493
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
Comments
@amahlaka Since you wrote the expanded documentation I'm hoping you could help here? |
It can be difficult to verify domain if you can't open ports 80 and 443 on your router, recommend way is to use DNS provider that allows you to create txt records, you can get domains like that from namecheap for under 1$ |
Hi @amahlaka and @Landrash,
|
I've temporarily solved the issue on domain verification by adding the meta tag in |
It seems like the instructions in general could use an update, as it was confusing which values to use for the keys. It even looks like the API key may be deprecated going forward. |
There was no action on this issue for over six months. I'm going to close it. |
PR #1393 "Simplified instructions" provides unclear (impossible?) instructions regarding HTML5 push notification component under subsection Getting ready for Chrome .
See details of the issue here: https://community.home-assistant.io/t/html5-step-getting-ready-for-chrome-pls-help/6586
The text was updated successfully, but these errors were encountered: