These properties are used to describe player state, which goes two ways - a POST to the stremiocast endpoint can set any of these properties, and a GET on the endpoint would return a full description of the player state using those properties
source
- read/write - url to media source; set this to begin playbackvolume
- read/write - player volume, from 0 to 1time
- read/write - current player time; use this to seekpaused
- read/write - whether the playback is pausedstate
- read - current player state; 0 - idle, 1 - opening, 2 - buffering, 3 - playing, 4 - paused, 5 - stopped, 6 - ended, 7 - errorlength
- read - time length of current mediaplay(source)
- start playbackstop()
- stop playbackupdate(cb)
- re-fetch status from casting deviceDISCLAIMER This does not pretend to be an alternative of existing protocols, such as DLNA and castv2. It's merely something similar designed with extreme simplicity in mind over HTTP and JSON.