Ombi is a friendly media request tool for Plex, Emby, and Jellyfin.
This repository packages Ombi as a Home Assistant App with ingress support. It opens from the Home Assistant sidebar and also exposes Ombi on port 3579 for direct local access.
| Service | App |
|---|---|
| Build | |
| Update | |
| Image | ghcr.io/wheemer/ombi-app |
For Ombi application features, use the Ombi feature board:
For Home Assistant App issues, use this repository:
https://github.com/Wheemer/ombi-app/issues
- Lets your users request movies, TV shows, and music from a clean web interface.
- Works with Plex, Emby, and Jellyfin.
- Connects to download and library tools such as Sonarr, Radarr, Lidarr, and other supported Ombi integrations.
- Supports request approval, user management, notifications, and availability tracking through Ombi.
- Opens inside Home Assistant through ingress.
- Exposes direct local access on port
3579. - Builds for
amd64andaarch64. - Uses the LinuxServer.io Ombi development image.
- Auto-updates from
Ombi-app/Ombiprereleases to match the development image stream. - Includes Ombi icon and logo assets for the Home Assistant App store and sidebar.
- Stores Ombi data in Home Assistant's backed-up app config storage.
Manual repository URL:
https://github.com/Wheemer/ombi-app
After adding the repository:
- Install
Ombi App. - Start the app.
- Open Ombi App from the Home Assistant sidebar or the app page's
Open Web UIbutton. - Direct local access is available on port
3579.
If you already used the older alexbelgium Ombi add-on, keep its data until Ombi App has imported it.
Recommended migration:
- Stop the old Ombi add-on.
- Add this repository to Home Assistant.
- Install and start
Ombi Appfrom this repository. - Ombi App automatically imports the old
addons_config/ombidata into its own backed-up app config folder when the new config is empty. - After Ombi App starts and your settings are present, uninstall the old Ombi add-on.
Alternative migration:
- Stop and uninstall the old Ombi add-on first.
- If Home Assistant asks whether to delete the add-on data, do not delete it.
- Install and start
Ombi Appfrom this repository.
If the old add-on data is deleted before Ombi App starts, there may be nothing left to import.
Use Ombi's setup wizard to connect Plex, Emby, or Jellyfin first. After that, add your request automation tools such as Sonarr, Radarr, or Lidarr from Ombi's settings.
When ingress is enabled, the app sets Ombi's Base URL to Home Assistant's ingress path. In Ombi settings this looks like /api/hassio_ingress/...; leave it that way for sidebar access. The generic Ombi reverse-proxy instructions do not apply to Home Assistant ingress.
Ombi data is stored in the app's own backed-up config folder. If an older install has data in addons_config/ombi, the app copies it into the new storage location when /config is empty.
Ombi's own application docs are here:
| Option | Default | Description |
|---|---|---|
PUID |
0 |
User ID used for Ombi files |
PGID |
0 |
Group ID used for Ombi files |
env_vars |
[] |
Extra environment variables passed to Ombi |
Example:
PUID: 1000
PGID: 1000
env_vars: []The scheduled update workflow checks Ombi-app/Ombi prereleases and bumps the app version when Ombi changes. This follows the same stream used by the LinuxServer.io development image.
Published image:
ghcr.io/wheemer/ombi-app
Use .github/social-preview.png for GitHub's repository social preview image so Home Assistant forum links show Ombi branding.
