Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add native cast support
See original GitHub issueA cast button to leverage the recently introduced Home Assistant Play Media action to show a camera stream in a Chromecast enabled media player.
When clicked, it would open a dropdown menu allowing to select which media player to cast the current camera stream to.
When selected, the card can then trigger the Play Media action passing in the current camera entity as input, in the selected media player.
It would be disabled for birdseye, by the way.
I haven’t tried to build my own custom buttons yet (and I wonder how far it would be possible), but the following are the reasons why I’m opening this suggestion:
- I believe it’s a quite common and generic use case. It would be nice to support it out-of-the-box, as HA now also does.
- I don’t think the current
tap_actionsyntax provides the means to call a Play Media action (which is not a service, by the way). But I suppose the card can do it, though. - If provided by the card, it can automatically decide to hide the button in case no suitable media players are found.
- If provided by the card, I suppose it can also color the icon based on the media_player state (whether it has started to stream the given camera or not), although this can come as an enhancement later (if possible at all).
What do you think?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @felipecrs , sounds like a good suggestion.
I think it hinges on this: whether or not / how a custom card can actually do this . It has to be via HA in order to get the HA media devices, which means it depends on HA having externalized that support somehow. The HA frontend is an enormous Javascript blob, and it is tricky – and in some cases not possible – for custom cards to get access to parts of it (here’s an example of where the card needs to fake load a picture glance card to get access to the editor widgets).
i.e. more research required on whether this is feasible right now.
Will be in v4.0.0 .