Comment on Self-hosted TV interface solutions
Onomatopoeia@lemmy.cafe 4 days ago
Two approaches:
Network isolation/DNS blocking - put the TV on a VLAN and only permit specific ports through to a media server (whatever the TV will support). If you lack VLAN capability, run PiHole as your DNS server (it works best as DNS and DHCP, but that’s just my opinion for things I like, such as proper name resolution for all devices).
Second option: disconnect TV from network entirely, then run something like Kodi (or whatever media center you prefer) on an old laptop, mini-PC, whatever, and have that device connect via HDMI. HDMI can passthrough the navigation controls from the TV remote (not giantess, but it’s part of the standard).
Even my POS Samsung passes through enough of the controls to navigate Kodi on a 2017 laptop, while retaining power, volume, settings, etc for the TV itself.
My current setup is a Jellyfin server and Jellyfin client on the TV. I run PiHole with a blocklist for all the Samsung BS which has had the side effect of making the TV menus faster as it doesn’t retrieve any “what’s new” info from Samsung. Its actually kind of fun to monitor the FNS log and see the domains the TV hits, click Deny and see what breaks in the TV. On average about 30% of all DNS requests on my network get denied, and nothing of value has been lost. That’s how much crap is being sent all the time.
Hope that gives you some ideas.
Reannlegge@lemmy.ca 4 days ago
Before I fully understood what pihole was doing, it does not block out going things, it was amazing to see how much ad poop was trying to get to my TV. As I got more and more into this very inexpensive hobby of home labing /s I decided just to remove the TV from my wifi and my pihole went from blocking in the high 60% range to something more like the mid 30% range.