

You first need to point the plugin to your HTTP server. Note how list and track interface naming are carefully picked, so that you canĬreating a server isĮasy in the majority of languages. Return a track object within an item list and fulfill its requirements. GET /:position: returns the list of elements starting from the given Inįact, extra keys are ignored and do not constitute an issue. Position in the position query parameter. POST /:position: adds one or more items before the given position. Other words, the position passed is the one that the first new item will occupy. Items will be passed as part of the body of the HTTP call, in the shape ofĪ JSON array. PUT /:position: replaces one or more items starting from the givenĭELETE /:position/:length: removes the items stored in place starting You can know which items were added by checking their id. zone/:zone/play/:contentId: start playing on the given zone the provided zone/:zone/state: returns the state of the zone, as described in the upper All of them are POST, except the first one: Your server can receive the following HTTP calls regarding player (zone)Ĭontrol. zone/:zone/time/:time: seek to the corresponding time. zone/:zone/volume/:volume: set the volume of the given zone. Parameters go from 0 to 100 (from mute to hightest possible volume). zone/:zone/repeat/:mode: mode can be 0 for non-repeated, 1 for Stepping (when using + or - from the UI) is controlled by the Loxone module. Zone/:zone/shuffle/:mode: mode can be 0 for non-shuffled, and 1 for Repeating one track, and 2 for repeating mutliple tracks.
