Kodi integration for Remote Two and 3

Using (modified) pykodi and uc-integration-api

The driver lets discover and configure your Kodi instances. A media player and a remote entity are exposed to the core.

Note : this release requires remote firmware >= 1.7.10

Supported attributes

• State (on, off, playing, paused, unknown)
• Title
• Album
• Artist
• Artwork
• Media position / duration
• Volume (level and up/down) and mute
• Remote entity : predefined buttons mapping and interface buttons (to be completed)

Supported commands for Media Player entity

• Turn off (turn on is not supported)
• Direction pad and enter
• Numeric pad
• Back
• Next
• Previous
• Volume up
• Volume down
• Pause / Play
• Channels Up/Down
• Menus (home, context)
• Colored buttons
• Subtitle/audio language switching
• Fast forward / rewind
• Simple commands (more can be added) : video menu, toggle fullscreen, zoom in/out, increase/decrease aspect ratio, toggle subtitles, subtitles delay minus/plus, audio delay minus/plus

Supported commands for Remote entity

• Send command : commands are sent as KB keymap commands in JSON RPC (see Kodi keyboard map for the list of available commands)
• Send command sequence (same commands as above)
• Support for the repeat, hold, delay parameters
• Simple commands : the same as media player simple commands, with the addition of the other media player commands

Usage

• Kodi must be running for setup, and control enabled from Settings > Services > Control section. Set the username, password and enable HTTP control.

• Port numbers shouldn't be modified normally (8080 for HTTP and 9090 for websocket) : websocket port is not configurable from the GUI (in advanced settings file)
• There is no turn on command : Kodi has to be started some other way

Tips

• The (simple) commands, interface or buttons mapping can be updated while a previous version of the integration has already been configured. In that case the new functionalities may not be visible. In that case, just remove the configured entity from the integration page and add it again. It won't affect your existing setup, but only trigger a refresh of the integration.

To do

• Add automatic discovery of Kodi instances on the network done
• Add more simple commands if necessary

Setup

• Requires Python 3.11
• Under a virtual environment : the driver has to be run in host mode and not bridge mode, otherwise the turn on function won't work (a magic packet has to be sent through network and it won't reach it under bridge mode)
• Your Kodi instance has to be started in order to run the setup flow and process commands. When configured, the integration will detect automatically when it will be started and process commands.
• Install required libraries:
  (using a virtual environment is highly recommended)

pip3 install -r requirements.txt

For running a separate integration driver on your network for Remote Two, the configuration in file driver.json needs to be changed:

• Set driver_id to a unique value, uc_kodi_driver is already used for the embedded driver in the firmware.
• Change name to easily identify the driver for discovery & setup with Remote Two or the web-configurator.
• Optionally add a "port": 8090 field for the WebSocket server listening port.
  • Default port: 9090
  • Also overrideable with environment variable UC_INTEGRATION_HTTP_PORT

Run

python3 intg-kodi/driver.py

See available environment variables in the Python integration library to control certain runtime features like listening interface and configuration directory.

Build self-contained binary for Remote Two

After some tests, turns out python stuff on embedded is a nightmare. So we're better off creating a single binary file that has everything in it.

To do that, we need to compile it on the target architecture as pyinstaller does not support cross compilation.

x86-64 Linux

On x86-64 Linux we need Qemu to emulate the aarch64 target platform:

sudo apt install qemu binfmt-support qemu-user-static
docker run --rm --privileged multiarch/qemu-user-static --reset -p yes

Run pyinstaller:

docker run --rm --name builder \
    --platform=aarch64 \
    --user=$(id -u):$(id -g) \
    -v "$PWD":/workspace \
    docker.io/unfoldedcircle/r2-pyinstaller:3.11.6  \
    bash -c \
      "python -m pip install -r requirements.txt && \
      pyinstaller --clean --onefile --name intg-kodi intg-kodi/driver.py"

aarch64 Linux / Mac

On an aarch64 host platform, the build image can be run directly (and much faster):

docker run --rm --name builder \
    --user=$(id -u):$(id -g) \
    -v "$PWD":/workspace \
    docker.io/unfoldedcircle/r2-pyinstaller:3.11.6  \
    bash -c \
      "python -m pip install -r requirements.txt && \
      pyinstaller --clean --onefile --name intg-kodi intg-kodi/driver.py"

Versioning

We use SemVer for versioning. For the versions available, see the tags and releases in this repository.

Changelog

The major changes found in each new release are listed in the changelog and under the GitHub releases.

Contributions

Please read our contribution guidelines before opening a pull request.

License

This project is licensed under the Mozilla Public License 2.0. See the LICENSE file for details.