What is Matter Casting? The smart home standard Matter includes the ability to cast media and it'll allow users to cast content to Fire TV | Trusted Reviews
I’m curious what people’s thoughts are about Matter. This is the first I’m hearing of it.
I’ve been trying to find a way to replace my old Chromecast Ultra (because Google), but I really like having that little cast button show up in apps, even on the phones of guests. But from what I can tell, Google killed this functionality on open alternatives (ex. Raspicast) with a lockdown to the Chromecast spec.
I’m hopeful that Matter could be a way to have my devices cast streams to each other in a standardized way that wouldn’t require me to rely on Google/Apple/Amazon/etc. Maybe even Newpipe could get in on the action?
I don’t know how it will work, or if this “Connected Standards Alliance” (which is apparently used to be the ZigBee Alliance, also news to me) will still have to greenlight specific devices despite it being “open”, which would rule out Newpipe. I would assume the official YouTube apps will be particularly resistant to supporting Matter.
Anyone have any experience here? Has anyone else successfully replaced their media device with something open that also works with the casting button in apps?
The company says services like Plex, Pluto TV, Sling TV, Starz, and ZDF will introduce support later this year.
I always had the impression that plex was really slow when it comes to implementing new features. I’m definitely looking forward to a chromecast alternative though. Being locked into googles DNS gives me problems due to it prohibiting streaming from my local server via hostname.
I really hope it will be implemented in Jellyfin as well since I can’t get my installation to work with Chromecast at all (most likely again due to the DNS issue)
I solved that by adding an 8.8.8.8 ip to my pihole interface. Because of how TCP/IP works, this has the fewest hops and is, therefore, the one to be used. I’m blocking all outbound DNS traffic for good measure.
By adding do you mean blocking it in pi-hole or somehow redirecting it to your pi-hole dns server?
I currently have it blocked in my router and can confirm this by trying to ping 8.8.8.8 without any response. If you mean redirecting to your pi-hole I would really like to know how to do it
I didn’t add it to any lists, but to the network interface itself. You know the output of ip a? The one pihole listens on (wg0 in my case, because wireguard) has something like, say, 10.0.0.1, but also8.8.8.8. So when a DNS packet is spit out by chromecast to go to 8.8.8.8 UDP port 53 - my pihole happily answers that request. You could also do a separate unbound instance on a new virtual interface with a quad8 ip and just forward everything to pihole, if you fancy.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I always had the impression that plex was really slow when it comes to implementing new features. I’m definitely looking forward to a chromecast alternative though. Being locked into googles DNS gives me problems due to it prohibiting streaming from my local server via hostname.
I really hope it will be implemented in Jellyfin as well since I can’t get my installation to work with Chromecast at all (most likely again due to the DNS issue)
I solved that by adding an 8.8.8.8 ip to my pihole interface. Because of how TCP/IP works, this has the fewest hops and is, therefore, the one to be used. I’m blocking all outbound DNS traffic for good measure.
By adding do you mean blocking it in pi-hole or somehow redirecting it to your pi-hole dns server?
I currently have it blocked in my router and can confirm this by trying to ping 8.8.8.8 without any response. If you mean redirecting to your pi-hole I would really like to know how to do it
I didn’t add it to any lists, but to the network interface itself. You know the output of
ip a? The one pihole listens on (wg0in my case, because wireguard) has something like, say,10.0.0.1, but also8.8.8.8. So when a DNS packet is spit out by chromecast to go to 8.8.8.8 UDP port 53 - my pihole happily answers that request. You could also do a separate unbound instance on a new virtual interface with a quad8 ip and just forward everything to pihole, if you fancy.