Remote 2 integration for Logitech Harmony Hub
10K+
This integration will make devices and activities from one (or more) Logitech Harmony Hub(s) available on one (or more) UC Remote 2. The integration will try to detect the Hubs on the local network. If not detected you can add them manually (during setup). For all devices and activities the Harmony Hub settings (icons, favorites, button mappings) will copied. For each hub all activities are copied to one group (so only one harmony activity of a hub can be active).
Note
The integration will try to copy a complete harmony setup. But the order of activities is not and some custom icons can not be download (will replaced with text).
The integration will try to keep in sync with the hubs. So you can combine the original Logitech remote together with Remote 2!
After setup you can customize everything to your needs. You can use activities and devices in other activities to your liking.
See https://youtu.be/Fne3kIkJm7w for setup and result after setup
Docker image will run rootless. (assign group 'users' (USER_UID 1000) to mapped folder)
Network binding should be to the host (not bridged)
Note
The Harmony hubs should have a fixed IP address. Changing IP addresses of Remote 2 should be handled
correctly, but fixed IP address is advised. Also different VLANs between UC remote and Harmony Hub should work (integration should be connected to both VLANs).
The following enviroment variables can be used.
| Variables | Description |
|---|---|
| SERVICE_IP | IP for service binding |
| SERVICE_PORT | port for service binding |
| DRIVER_ID | optional custom driver id, for multiple instances |
| REMOTE_IP | optional: manual integration installation |
| REMOTE_PIN | optional: manual integration installation |
Important
SERVICE_IP and SERVICE_PORT must be used.
Map a volume to /app/config for the settingsfile config.json (in volume mapped folder). If no volume is mapped a local map in the docker will be used for the settingsfile (which will be lost when docker image is updated).
Important
The group 'users' (USER_UID 1000) must have write access to this volume.
Integration will register a mDNS record, which remote 2 will use to find the integration. It is possible to do a manual registration on remote 2. Add two environment variables: REMOTE_IP with IP address of the remote and REMOTE_PIN with PIN of the remote. When not using the manual registration methode the integration will ask for PIN (once) to genereate an API key. This API key is used for interaction with remote 2. The setup contains the following steps:
After selecting entities, integration will create the interface. This will will take 1 minute for each Hub after device selection. Remote 2 will restart after setup is complete. Restart is necessary to fix a UI issue (not showing icons) after setup.
The integration can handle multiple Hubs and can be used with multiple remote 2. For short: one integration for multiple remotes and multiple devices!
Note
before updating the integration, put the UC remote(s) in the dock (so UI updates on the remote can be done).
The first time after starting v0.2.8 the integration will try to update configuration and UI. If this fails, the advice is to follow the next procedure: delete integration, on the UC remote manually delete all Harmony group/activities, stop docker container, delete the file config.json (in mapped folder), start the docker container and add/setup the integration to the UC remote.
new
fixes
Content type
Image
Digest
sha256:a454ed1a3…
Size
115.7 MB
Last updated
about 2 years ago
docker pull clarijs/remote2integrationharmony