Hey ibvhefe,
Thanks for the reply
it had just started working after installing bindings - http binding & tcp/upd binding from the addons. Just before I read your reply.
The Audio Control API is a subset of what you may know as the ScalarAPI (ScalarAPI is the internal name, set long before it was decided to make any part of it public).
If you have any questions about the API I will gladly try to answer them, but I can only answer the part of the API that is connected to the Audio (soundbar, receiver and wireless speakers) since this are the only parts that are officially supported by SONY.
Just to let everyone know - David put together a quick ESH sony audio plugin PR and Iām starting some discussions with him on the subject. The public API documentation is great - most of what I have done is confirmed by it and there were a couple of gems that I didnāt know about (the biggest being a different way to connect that doesnāt require authentication and will support a wider range of devices - including my HT-NT5 soundbar).
While Iām working on making the binding mergable and implementing some of the stuff the API shows - Iāll be having discussions with him and @Kai on the future direction of this binding (whether to make this an ESH binding or not).
i had this working on 2 of my 3 sony tvs. but i got a dead sd card and had to start over.
i now cant find the tvs in the inbox. i have removed the openhab remote from the tvs. now i cant work out why they are not being found
i can see the binding has loaded as its in the list of installed bindings
i cant find the logs as openhab log viewer isnt working after starting over.
any help working this out would be great
thanks
I got really excited when I first saw this thread, because I have one SA-NS300 and seven Sony SA-NS400 speakers through the house, and I was hoping that your binding might include them. I wrote some scripts to control them through OH, including putting them into Party mode for announcements, but it would be nice to have it all wrapped into a binding that makes use of audio sinks. I have started to deconstruct the Sonos binding with the intent of putting together a Sony HomeShare binding, but if these devices would become supported by your binding, then Iām probably wasting my time. They are slightly older tech, but is there any chance you would/could be adding support for these speakers?
@freke awesome to see that Sony made a public API! On the device page, only three speakers are listed. Why is it limited to there three? Will other speakers follow or are more speakers than the listed once supported? What about the SRS-ZR7 for example?
Hi @dominicdesu
I hope more speakers will be listed and supported by SONY in the future (I donāt know when or which, it is decided in Tokyo), the main reason it is only three, is manpower. It is a lot of work to go through to make this possible, so we selected one of each category (Soundbar, Receiver, Wireless Speaker) and in different price range to start with to make sure that something got released.
The SRS-ZR7 is almost the same as SRS-ZR5 so even if it is not officially supported it will (most likely) work with @tmrobert8 OpenHAB binding.
@freke nice, thanks for the explanation. So the devices already have the capability to be controlled via an API, just the (public) API is missing
I am currently looking for a replacement for my Panasonic AllPlay speakers, and the Sony Multiroom speakers look very promising! Iāll keep an eye on the API development
Thanks for your and @tmrobert8ās effort!
Hi @tmrobert8
I looked in to the docs I have about the HT-NT5 and it uses the same API version as STR-DN1070, this is the receiver I first used to test the API and you should not have any authentication problems with it.
That sad, I had some problems with WebSockets in the beginning, saying that I needed authentication. In the end it was the WebSocket library I used that caused the problem it added āOrigin: file://ā to the upgrade message and that causes the problem I got.
So it might be worth checking the http header to see if anything there is causing your auth problem. Even if non of the audio products are using the authentication the functionality, is there in the backend and can cause unexpected errors if trigged.
Finally made it work on my Sony Bravia KDL-48W600B! Iām still very new at this so if thereās anything else you need let me know and Iāll try to post it. I just mapped the power, volume slider and mute switches for now and theyāre all working.
Sounds like you need to delete your cache/temp directories and start over again since it sounds like you have bigger openhab issues than just this binding.
Absolutely kills me when you say āā¦looked into the docs I have about ā¦ā - would have loved to see those resources! The authentication issues I was having is because I didnāt know about the websockets until now (hadnāt really looked at what that port was doing - so never noticed the websocket protocol) and I was trying to figure out how to authenticate when I was missing the āactRegisterā method. However - with the websocket protocol - I believe I should be able to get those working.
Would you be able to state whether ALL devices that implement webscalar service will have a websocket available (and thus can change everything over to a websocket rather than http posts)?
@tmrobert8 the short answer is, I donāt know.
From the sources I can see my guess is there is some older products that donāt have websockets support, it looks like the first versions of webscalar didnāt support websockets, but I donāt know.
To complicate it even more it is not certain that all methods is present in both even if both are supported. The only one I know of, is switchNotification, that is only pressent for websockets.
If āactRegisterā method is missing no authentication is needed for that product
If it is present some functions will need authentication for both websockets and http.
