mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-07-04 04:58:46 +02:00
4754794968
bashio now emits deprecation warnings for bashio::addon.* calls. This migrates all 227 call-sites across 86 files to use the new bashio::app.* API. Cross-compatibility is preserved in two ways: 1. bashio-standalone.sh: adds bashio::app.* functions that forward to bashio::addon.* (used when running without HA Supervisor). Also adds the missing ingress_url, restart and stop stubs. 2. ha_entrypoint.sh: injects a one-liner compat shim after the shebang of every cont-init and service script at container startup. On old bashio installations (bashio::app.* absent) the shim defines bashio::app.* as thin wrappers around bashio::addon.*; on new bashio the guard condition is true so the block is a no-op. The probe script in ha_entrypoint.sh is also updated to try bashio::app.version before falling back to bashio::addon.version. https://claude.ai/code/session_011FWFBhYQ6VS5FauSqv4UMo
Home Assistant add-on: Seerr
About
This add-on packages Seerr, an open-source media request and discovery manager for Jellyfin, Plex, and Emby.
This add-on is based on the existing Overseerr add-on structure, adapted for the Seerr upstream project and container image. It supports Home Assistant Ingress via an internal NGINX reverse proxy.
Upstream repositories reviewed:
- Overseerr: https://github.com/sct/overseerr
- Seerr: https://github.com/seerr-team/seerr
Installation
- Add my add-ons repository to your home assistant instance (in supervisor addons store at top right, or click button below if you have configured my HA)
- Install Seerr.
- Configure options, then start the add-on.
- Open the Web UI on port
5055or via Home Assistant Ingress.
Configuration
Use env_vars to pass extra environment variables when needed. Seerr configuration is stored in /config.
Options
| Option | Type | Default | Description |
|---|---|---|---|
NODE_MEMORY_LIMIT |
int | 512 |
Maximum Node.js heap memory in MB. Increase if Seerr crashes with large libraries; decrease on memory-constrained systems. |
PGID |
int | 0 |
Group ID for file permissions |
PUID |
int | 0 |
User ID for file permissions |
TZ |
str | Timezone (e.g. Europe/London) |
Example
NODE_MEMORY_LIMIT: 512
env_vars: []
PGID: 0
PUID: 0
TZ: Europe/London
Migration
From Overseerr
Seerr is compatible with Overseerr's data format. To migrate your existing configuration:
- Stop the Overseerr add-on.
- Install and start the Seerr add-on once to create its config directory (
/addon_configs/db21ed7f_seerr/), then stop it. - Open the Filebrowser add-on (or any file manager with access to
/addon_configs/). - Navigate to
/addon_configs/db21ed7f_overseerr/and copy all files into/addon_configs/db21ed7f_seerr/. - Start the Seerr add-on. Your existing settings, users, and requests will be preserved.
From Jellyseerr
Seerr is compatible with Jellyseerr's data format. To migrate your existing configuration:
- Stop the Jellyseerr add-on.
- Install and start the Seerr add-on once to create its config directory (
/addon_configs/db21ed7f_seerr/), then stop it. - Open the Filebrowser add-on (or any file manager with access to
/addon_configs/). - Navigate to
/addon_configs/db21ed7f_jellyseerr/and copy all files into/addon_configs/db21ed7f_seerr/. - Start the Seerr add-on. Your existing settings, users, and requests will be preserved.
From Ombi
Ombi uses a different data format and there is no automated migration path to Seerr. You will need to configure Seerr from scratch:
- Note down your Ombi configuration (media servers, users, notification settings, etc.).
- Stop the Ombi add-on.
- Install and start the Seerr add-on.
- Use the Seerr web UI to reconnect your media server(s) and reconfigure your preferences.
Support
If you find a bug, open an issue in this repository.