Applies to: Supported OpenPLi receiver/image combinations with the documented local-extension interface
The useful distinctions
- OpenPLi documents a local-extension installer.
- The graphical route can use removable storage.
- A visible IPK is not itself a compatibility or safety assessment.
Check why a local package is needed
A local IPK is a package file, not proof that it belongs to the receiver’s installed image. Identify the maintainer and the reason for using that file instead of an available image feed. The OpenPLi graphical procedure describes how to select a package; it does not validate every file that happens to have the same extension.
Make the selection unambiguous
Use a removable medium and file arrangement that lets you identify the intended package clearly. Keep unrelated installers out of the selection task where possible. Before confirmation, compare the package information with the receiver/image context and retain a way to recover the current setup. An uncertain filename should be a reason to pause, not a reason to try several packages until one installs.
Verify installation before service setup
Once the documented installer completes, inspect whether the intended extension is available and opens. That is a different check from its later configuration or account access. If installation reports a dependency or compatibility error, preserve the message and ask the maintainer. Do not infer that a successful installer has tested the extension’s features, audited its code or confirmed a streaming provider relationship.
A focused way to proceed
- Confirm the receiver image and trusted package source.
- Preserve the current recoverable state.
- Place the intended IPK on the supported removable medium.
- Open Plugins, Software management and Install local extension as documented.
- Inspect the selected package before confirming installation.
Worked example · synthetic
Hypothetical comparison: a receiver can browse a USB drive and show an IPK, but the package was built for another image family. Storage access has succeeded while package preflight remains unresolved. Confirming installation would not be a meaningful test of the intended viewing setup.
When to stop or ask for help
Stop on an unidentified source, model/image mismatch or missing recovery method. Use the package maintainer’s instructions for errors rather than escalating immediately to unrelated command-line installation recipes.