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

Notification opening HA app with specific landing point #250

Closed
tinglis1 opened this issue Mar 29, 2019 · 4 comments · Fixed by #687
Closed

Notification opening HA app with specific landing point #250

tinglis1 opened this issue Mar 29, 2019 · 4 comments · Fixed by #687

Comments

@tinglis1
Copy link

One thing I would like to see is when you open a notification that you can specify where in the app you want it to land.

For instance. When I get a image sent to my phone when there is motion at my door. I can view the image in the notification but if I open the app from the notification it takes me to the main page of the HA app.
It would be nice if I could specify something like a navigation path in Lovelace, so when it opens the HA app it takes me to my security page or the stream for my camera.

@robbiet480 robbiet480 changed the title Feature Request: Notification opening HA app with specific landing point Notification opening HA app with specific landing point Mar 29, 2019
@jimz011
Copy link

jimz011 commented Mar 29, 2019

I too was wondering if this would be possible.

@gregschwartz
Copy link

+1 on this request!

@tinglis1
Copy link
Author

Any update on this?
The 2.0 app is awesome and this would really make it perfect for me.
In particular the other non-technical users of the app in my household would be the real target users.

I figure there is two main types of landing page. A Lovelace navigation path or an entity panel.

Some example use cases I could use right now are:

  • motion notification could open a camera entity or security page
  • temperature notification could open the entity to show history
  • temperature notification could take you too climate control page.

@TomBrien
Copy link
Member

This is similar to what is being discussed in #643

zacwest added a commit that referenced this issue Jun 21, 2020
This handles the various ways that we could launch:
- state restoration doesn't fire on notifications since the system knows it shouldn't
- launching from cold uses a Promise to wait (since it's launched well before WebViewController exists)
- launching  from warm goes through the same Promise but happens instantly
- handles one fun edge case of: start the app, get logged out due to deactivated token, open a notification with a url, finish onboarding -- this will correctly open the URL.

Fixes #250 -- use a URL like `/lovelace-name-here/0` to open a page as if you navigated to it normally.
zacwest added a commit that referenced this issue Jun 21, 2020
This handles the various ways that we could launch:
- state restoration doesn't fire on notifications since the system knows it shouldn't
- launching from cold uses a Promise to wait (since it's launched well before WebViewController exists)
- launching  from warm goes through the same Promise but happens instantly
- handles one fun edge case of: start the app, get logged out due to deactivated token, open a notification with a url, finish onboarding -- this will correctly open the URL.

Fixes #250 -- use a URL like `/lovelace-name-here/0` to open a page as if you navigated to it normally.
zacwest added a commit that referenced this issue Jun 21, 2020
This handles the various ways that we could launch:
- state restoration doesn't fire on notifications since the system knows it shouldn't
- launching from cold uses a Promise to wait (since it's launched well before WebViewController exists)
- launching  from warm goes through the same Promise but happens instantly
- handles one fun edge case of: start the app, get logged out due to deactivated token, open a notification with a url, finish onboarding -- this will correctly open the URL.

Fixes #250 -- use a URL like `/lovelace-name-here/0` to open a page as if you navigated to it normally.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants