
With Version 1.1 B 2370 there was a remote control server introduced in neutrinoTV.


v1.1 Build 2370
---------------
This Version of neutrinoTV includes the very first version of a rudimentary remote control server. Nothing is yet final, so even the protocol may change in the next version. So, this is basically for testing and for learning (also for me, in order to find a good remote control protocol).

So, what can it do? Well you may connect with a TCP connection to port 31330 (configurable over the neutrinoTV config-file). The protocol is text based, so you may want to use putty in telnet mode to experiment; also windows telnet is ok, but there you don't see what you type..

In this version only the following 4 commands are recognized: START, STOP, NEXT and PREV. It's selfexplanatory what they do, but for completeness:
START: Start the live stream - does all the things what neutrinoTV does when you click on ""Go Live"
STOP: Well, it stops the live stream, also everything what happens when you click stop.
NEXT/PREV: Zaps to the next/previous channel, just as if you would have pushed the PageUp or PageDown key on your keyboard.

Also "bye" is recognized, which closes the connection from serverside.

Note: There is no feedback at this moment if the action was successfull or not. Also there is only very little error checking, so you might be able to crash neutrinoTV with these commands when not used in the way like it should be



v 1.1 B2371
-----------

Remote Control server update:

The following commands are supported (case insensitive):

start/stop: start/stops the stream
zaptonext/zaptoprev: zapps to the next or the previous channel (changed from prev/next)
zaptoid <channel-id in hex>: planned, but not implemented yet
getservices: triggers a listing of all channels - format is explained below:
BOUQUETLISTBEGIN <totalbouquets>
BOUQUET ..
...
BOUQUETLISTEND
CHANNELLISTBEGIN <totalchannels>
CHANNEL ...
...
CHANNELLISTEND

getcurrentchannel: triggers the event for sending the current channel
CURRENTCHANNEL ...


Completely new are the events:

BOUQUETLISTBEGIN <nr> - indicates that a bouquetlisting is about to start, <nr> gives the total number of the bouquets
BOUQUETLISTEND - indicates the end of a bouquetlisting
CHANNELLISTBEGIN/CHANNELLISTEND: the same for channels

BOUQUET <nr> <name>
CHANNEL <type> <bouquet-nr> <channel-id in hex> <channel number> <channel-name>

CURRENTCHANNEL <type> <bouquet-nr> <channel-id in hex> <channel number> <channel-name>
(same as CHANNEL)


STARTEDSTREAMING: event which tells you that neutrinoTV started streaming
STOPPEDSTREAMING: event which tells that neutrinoTV aborted streaming


Events come asynchronously, i.e. they can come at any time, even in the middle of a channel listing. So, when communicating with neutrinoTV just asume only single lines as atomic units.

Independent of above events are OK and ERROR - you always get an OK, if the command was recognized (not executed!), and an ERROR if something is syntactically wrong with the command.




v 1.1 B2378
-----------

Updated the remote control API and now neutrinoTV also supports "ZAPTOID <cid-in-hex>"

Also it is now possible to enable/disable the remote control server through the gui (Settings->Network). Also the port can be set through the gui. 