It would be great if there is a kodi binding,
the rest api has a lot of possible approches how to interact with the channels.
For example listing channel details: http://forum.kodi.tv/showthread.php?tid=244198
And this site also recommends using curl: http://forum.kodi.tv/showthread.php?tid=183965&pid=1607144#pid1607144 /usr/bin/curl -v -H "Accept: application/json" -H "Content-type: application/json" -X POST -d '{"id":1,"jsonrpc":"2.0","method":"Player.Open","params":{"item":{"channelid":14}}}' http://localhost:9191/jsonrpc
The Umlaut problem is a well-known problem also for other bindings. We are discussing this in the Smarthome issue tracker (https://github.com/eclipse/smarthome/issues/2639) and I think that we have a solution.
Now that the binding has been merged I can work on the PVR support. But it may take 2 or 3 weeks until a first implementation.
Things file always have to be created manually. But if you use the Paper UI you don’t need it. Normally your Kodi will be detected automatically. Then new binding uses the websocket API and as far as I remember this does not need auth.
Testing this new binding I came across a small problem…
The “control” channel does not support STOP.
Is this the intended behavior?
If you stop the player in Kodi, the channel state goes to PAUSE instead of STOP.
And, evidently, you cannot send STOP command to player…
Valid data types are: ( PlayPauseType RewindFastforwardType UnDefType )
The channel uses the standard player item type (https://www.eclipse.org/smarthome/documentation/concepts/items.html) but this item type apparently does not have a stop function.
You could add an issue in the Smarthome repo for support of a stop function in the player.