Is there a way to generate / get a URL for a lovelace view with a single card so that it can be included in other systems?
The idea is to either use an iFrame to include in a web page or for embedding in digital signage.
Obviously because both those systems wouldn’t have the capacity to “log in” - the URL would need to be unsecured or long-live signed.
2 Likes
You might choose HADashboard (AppDaemon), but a single lovelace card without authentication is not reliable and hurting the whole concept IMHO.
There are many ways to create a frontend, because of that API and websocket exist…
I have several devices to show states and for every OS there a lots of ways to show something.
One easy way (and universal) way could be a PHP page with MQTT client library and some JS to refresh state.
But HADashbard brings everything you need, I think.
Or is the design/look and feel of lovelace important for you?
It just seems silly to “reinvent the wheel”.
The lovelace cards are serviceable, and easily managed / updated.
If not a card, then accessing a lovelace page without banners / footers etc (ie - just the page content) would be ideal.
Again though, it would need to be a signed URL that can be long lived.
1 Like
Perhaps this is where users can take us in the system as the model is developed.
I am assuming that different users in HASS can have different default views once the model is more fully implemented.
If that is the case, my tablet in the kitchen can login as kitchen_tablet user and get its own views.
Indeed.
Would be a nice feature to have. Never thought about it…
Usually, I have quite old devices, which cannot display such “modern” pages as lovelace 
I use lovelace on my cell and laptop only.
As feature request, a combination of a lovelace link and the auth part of webhooks could be a possible approach? 
I’d suggest this should be broken into two parts:
- We should be able to set IP addresses as whitelisted for a specific user - removing the need to “log in” even from a whitelisted IP. Eg
---
trusted_networks:
- 1.2.3.4/32: screen_user
- 5.6.7.8/32: another_user
and…
- Allow a url querystring override that doesn’t display headers/footers/sidebars etc - just the lovelace page itself. Eg
https://my.home.assistant/lovelace/digisign003?kiosk=true
2 Likes
This would be awesome! I would love to create cards specific for each of my kids and some close friends without exposing them to complete control! This is a major missing piece in HomeKit too! Hopefully the smarter then I people here can figure out a way to implement this!
any news on this guys?
Sort of halfway there… You can now define trusted_users. When you use it with a combination of allow_bypass_login you can simulate some of which we are discussing here.
Missing part is the kiosk rendering, which must be there somewhere given the new Chromecast support.
1 Like