Unless otherwise noted, URLs should not end with a
/ or other API path. Each widget will handle the path on its own.
Each service can have one widget attached to it (often matching the service type, but thats not forced).
In addition to the href of the service, you can also specify the target location in which to open that link. See Link Target for more details.
Using Emby as an example, this is how you would attach the Emby service widget.
- Emby: icon: emby.png href: http://emby.home/ description: Movies & TV Shows widget: type: emby url: http://emby.home/ key: apikeyapikeyapikeyapikeyapikey
Each widget can optionally provide a list of which fields should be visible via the
fields widget property. If no fields are specified, then all fields will be displayed. The
fields property must be a valid YAML array of strings. As an example, here is the entry for Sonarr showing only a couple of fields.
In all cases a widget will work and display all fields without specifying the
- Sonarr: icon: sonarr.png href: http://sonarr.host.or.ip widget: type: sonarr fields: ["wanted", "queued"] url: http://sonarr.host.or.ip key: apikeyapikeyapikeyapikeyapikey
Here are all the currently available widgets.
- Streaming Media Providers
- Media Management Tools
- Download Clients
- Network Utilities
- Network Infrastructure
- Information Providers