Configuration
Example config
# commands can have defaults added via the defaults item
# if icon is not supplied then it is defaulted to <item name>.ico
# command title must be a zone name if it is played by jriver
commands:
defaults:
exe: 'x:\mc_scripts\ezmote.exe'
volume: 0.40
stopAll: true
close:
args: ['CloseAll']
# icons prefixed with mi are special cased to be a material-ui icon
icon: 'mi/close'
# idx is the order in which the commands will be listed in the ui
idx: 0
title: 'Close'
music:
args: ['jriver', 'Music']
icon: 'mi/library_music'
idx: 1
title: 'Music'
# sets the top appbar to the jriver selector which is based on MCWS browseChildren
control: 'jriver'
# nodeId is the start point to navigate through MCWS browseChildren
nodeId: 1
stopAll: false
video:
args: ['jriver', 'Film']
icon: 'mi/movie'
idx: 2
title: 'Films'
control: 'jriver'
nodeId: 3
stopAll: false
netflix:
args: ['netflix']
idx: 3
title: 'Netflix'
playingNowId: 5000
# if zoneId is provided, the specified zone will be activated when the command is sent
zoneId: 10009
virgin:
args: ['tivo']
idx: 4
title: 'Virgin'
control: 'tivo'
playingNowId: 6000
zoneId: 10009
iplayer:
args: ['iplayer']
idx: 5
title: 'BBC iPlayer'
playingNowId: 1000
zoneId: 10009
amazon:
args: ['amazon']
idx: 6
title: 'Amazon Video'
playingNowId: 4000
zoneId: 10009
all4:
args: ['all4']
idx: 7
title: 'All4'
playingNowId: 3000
zoneId: 10009
itv:
args: ['itv']
idx: 8
title: 'ITV'
playingNowId: 2000
zoneId: 10009
radio:
args: ['jriver', 'Radio']
icon: 'mi/radio'
idx: 9
title: 'Radio'
control: 'jriver'
nodeId: 1000
stopAll: false
playlists:
args: ['jriver', 'Playlist']
icon: 'mi/playlist play'
idx: 10
title: 'Playlists'
control: 'jriver'
nodeId: 4
stopAll: false
iconPath: 'x:\mc_scripts\icons'
playingNowExe: 'x:\mc_scripts\getPlayingNow.exe'
debug: false
debugLogging: true
host: megatron
port: 53199
# use for debug
webappPath: 'C:\Users\mattk\github\ezmote\build'
Metadata
Release files for ezmote-cmdserver 2.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ezmote_cmdserver-2.0.5.tar.gz | 21.1 kB | Without provenance | Details for ezmote_cmdserver-2.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ezmote_cmdserver-2.0.5-py3-none-any.whl | Python 3 | none | any | Details for ezmote_cmdserver-2.0.5-py3-none-any.whl |
Total release size: 46.6 kB
Release files / ezmote_cmdserver-2.0.5.tar.gz
| Download URL | ezmote_cmdserver-2.0.5.tar.gz |
|---|---|
| Size | 21.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b3c125ba3f08e60c30ff6d229adc09610e2f76a3d831e2b9d5d7df60ab6b1b1c
|
|
BLAKE2b-256 checksum How to use checksums |
dc3295a0f6a850d2583c7ae668921b0064e43870fdb4ea2be9e63a7a1f0bf736
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / ezmote_cmdserver-2.0.5-py3-none-any.whl
| Download URL | ezmote_cmdserver-2.0.5-py3-none-any.whl |
|---|---|
| Size | 25.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaef4d7ea9094c376fd2c2e9166fe52ce9e1caff5d97225cb483bd37401409bb
|
|
BLAKE2b-256 checksum How to use checksums |
f0938d05127e048885e04e82223db7c21a96a60a4294c4da5b66494ccc62a0f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for ezmote-cmdserver 2.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.