I have setup and run what are basically HTPC’s for decades now. Kodi running on a Debian based Linux distribution or just Debian is a solid recommendation and has lots of support for infrared remotes, but kodi can be very fiddly to setup properly. It will work, but don’t expect it to work “out of the box”. You’ll probably still need a mouse and keyboard for anything outside Kodi. You’ll have to read a bunch of documentation and do some customizing to get the most out of Kodi. It’s still easier than most other setups, but it will feel very frustrating if it’s your introduction to Linux too.
I’ve moved to using my HTPC primarily as a server. Once you get comfortable with linux and docker, setting up new server services like Jellyfish, Plex, and and *ARR stack is relatively trivial. The advantage here being that you can serve your media to any device that can connect to your server. For me that means one library of media to share with any TV in my house, any mobile device I own, and any friends and family computer savvy enough to download the right apps and setup an account. If your network (and your Internet connection) isn’t reliable this kind of setup may not work very well for you at all. For example, Plex account authentication will fail is you don’t have Internet. Jellyfin and Kodi fair better when Internet is only available occasionally or is unreliable.
My least favorite part of using Kodi was setting up the remote. Even worse was trying to configure controllers for retro gaming. The situation is MUCH better than it was, but is still far from easy. I was kind of able to side step the remote problem because now I can just use the remote for the TV (if it supports the Plex or Jellyfin apps) or another streaming stick like fire stick, Nvidia shield, or Roku. My Nvidia shield can pair with any Bluetooth controller and runs RetroArch so that problem was side stepped too. ROMs can be copied via samba shares or loaded directly by a USB drive.
TLDR: Kodi has built-in support for IR, but streaming sticks are cheap, and in the long run I found setting up a server was more versatile, more reliable, and less stressful. I know, I also hate it when people ask for a specific solution and others recommend asking a different question. But in this case, my experience is that IR remotes suck, are flaky, and not worth it if there is any other option.
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 have setup and run what are basically HTPC’s for decades now. Kodi running on a Debian based Linux distribution or just Debian is a solid recommendation and has lots of support for infrared remotes, but kodi can be very fiddly to setup properly. It will work, but don’t expect it to work “out of the box”. You’ll probably still need a mouse and keyboard for anything outside Kodi. You’ll have to read a bunch of documentation and do some customizing to get the most out of Kodi. It’s still easier than most other setups, but it will feel very frustrating if it’s your introduction to Linux too.
I’ve moved to using my HTPC primarily as a server. Once you get comfortable with linux and docker, setting up new server services like Jellyfish, Plex, and and *ARR stack is relatively trivial. The advantage here being that you can serve your media to any device that can connect to your server. For me that means one library of media to share with any TV in my house, any mobile device I own, and any friends and family computer savvy enough to download the right apps and setup an account. If your network (and your Internet connection) isn’t reliable this kind of setup may not work very well for you at all. For example, Plex account authentication will fail is you don’t have Internet. Jellyfin and Kodi fair better when Internet is only available occasionally or is unreliable.
My least favorite part of using Kodi was setting up the remote. Even worse was trying to configure controllers for retro gaming. The situation is MUCH better than it was, but is still far from easy. I was kind of able to side step the remote problem because now I can just use the remote for the TV (if it supports the Plex or Jellyfin apps) or another streaming stick like fire stick, Nvidia shield, or Roku. My Nvidia shield can pair with any Bluetooth controller and runs RetroArch so that problem was side stepped too. ROMs can be copied via samba shares or loaded directly by a USB drive.
TLDR: Kodi has built-in support for IR, but streaming sticks are cheap, and in the long run I found setting up a server was more versatile, more reliable, and less stressful. I know, I also hate it when people ask for a specific solution and others recommend asking a different question. But in this case, my experience is that IR remotes suck, are flaky, and not worth it if there is any other option.
Huh I’ll have to give Kodi a shot. I’ve already got a bunch of Debian experiance and have jellyfin so leaning kodi shouldn’t be too bad.