Skip to content
odio odio docs

Community

odio is 100% free software (MIT and BSD-2 licenses) built from independent, API-compatible components that plug into each other. Each piece — the API, the disc player, the notification system — can be used standalone or as part of the full stack. The architecture is designed to be tweaked, extended, and adapted to your own needs. Every Pi running odio is a proprietary streamer that doesn’t need to exist, less e-waste, less CO2, more life out of hardware you already own.

odio was built around one household’s needs and setup, but it’s not meant to stay that way. Free software lives through its community. Building and maintaining all of this is a lot of work: community help, even small contributions, makes a real difference.

Share your setup

Section titled “Share your setup”

One of the most useful things you can do is simply tell us how you use odio:

  • What hardware are you running it on? (Pi model, DAC, amplifier, speakers…)
  • How did you install it? (Imager or curl installer)
  • What features did you want? What do you actually use?
  • How do you control it? (embedded UI, odio app, Home Assistant, MPD client, API…)
  • What’s your setup around odio? (Music Assistant, Navidrome, Plex, Kodi, a NAS, a DLNA server… anything that talks to odio via standard protocols)

There is no tracking, no telemetry in odio, and no analytics on the odio websites. GitHub and Medium have their own analytics, which we do look at. Your feedback is the only way to know what works, what doesn’t, and what actually matters. Head over to Show and Tell to share.

Contribute

Section titled “Contribute”

There are many ways to help:

  • Talk about odio — a conversation, a blog post, a video, a mention in a forum. Every person who discovers odio is one more Pi saved from a drawer and one less proprietary box shipped.
  • Star the repositories — a small gesture that gives odio visibility and tells whoever lands on GitHub that the project is real and used.
  • Test on your hardware — odio supports a wide range of boards and setups. Confirming it works (or reporting when it doesn’t) on your specific configuration is invaluable.
  • Improve the docs — found something unclear or missing? The documentation repo is open for contributions.
  • Try extensions — got Plexamp, Jellyfin, or something else running alongside odio? Share your setup on the Extensions page.
  • Report bugs — open an issue with as much detail as you can.
  • Request features — or better yet, propose how they could work. Feature discussions are already happening, like this community request for web radio streaming support.
  • Contribute code — there are already open issues, PRs, and discussions to pick up. PRs are welcome, but please open a discussion first to validate the architecture, the approach, and the intended UX before diving into implementation. AI-assisted code is fine, AI-generated code thrown over the wall is not.
  • odiotv — the HTPC use case already shows Kodi and browser kiosk running in a graphical user session alongside odio. There’s a solid base here for a full media center experience — if the community wants to take it further.

Guidelines

Section titled “Guidelines”

odio can translate as “hate”, but this community runs on the opposite. Be kind, be helpful, be patient. Everyone’s setup is different, everyone’s experience level is different, and not every expectation can be met. If that’s not your vibe, this isn’t the place.

Beyond the ground rules, the empowerment page lays out the posture this community runs on: come curious, learn by doing, help odio and the people around it get a little better in the process.

Where to find us

Section titled “Where to find us”