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?

  • IllecorsA
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    5 months ago

    Being locked into googles DNS gives me problems

    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.

    • Scrath@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      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

      • IllecorsA
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 months ago

        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 also 8.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.