Sony Devices Binding

Yep - the scalar binding supports PSKs and really your file is doing nothing different than what the scalar binding is doing under the scenes (but in much more detail). In fact, if you pull up the sony webpage you can pretty much play around with all that - simply load your device file from userdata/sony/definitions/capabilities) and you’ll see everything your TV supports and can play with it interactively (a much more powerful version of the page you put together because you can also interactively specify parameters).

The problem isn’t the port on the individual calls. The problem is the port is required during discovery to retrieve the descriptive information to setup everything the binding needs (to discover all that information you have in the file). Once I discover all that - the port isn’t needed anymore. Having said that - I don’t think I ever thought all that through and maybe I can come up with some solution that is easier.

As for your edits:

  1. getApplicationStatusList() that is not applications in what you think. That is internal sony application status and will tell you various states the sony internal applications are in. What you want to use is getWebAppStatus but you’ll notice that it returns stopped on everything. Sony broke that when they broke DIALs implementation as well.
  2. getPlayingContentInfo() yep - thats correct. And the binding should properly update the associated channels on the poll when it retrieve that information
1 Like