10.09.2019, 21:47
(This post was last modified: 10.09.2019, 21:50 by Erwin van der Zwart.)
Hi,
The old version of the Sonos app was created by me, in that app i created a self build API that was able to receive HTTP command with arguments and those where converted to LUA commands to SOAP (UpnP).
The new version of the app is build by our development department and the decission was made to certify the app to be able to use the official Sonos API, due to this certification we where forced to drop the self build API in the app. Now you can only use the objects that are created automatically by adding them to the touch application.
There is no build in mechanisme to send HTTP commands to the app anymore in the new version.
We still can use the old .lp API by uploading it to the ftp folder, but i still need to make some adjustments as the old app performed a auto scan of Sonos devices on startup that is now missing in the .lp file, but i have no time this moment to do it.
BR,
Erwin
The old version of the Sonos app was created by me, in that app i created a self build API that was able to receive HTTP command with arguments and those where converted to LUA commands to SOAP (UpnP).
The new version of the app is build by our development department and the decission was made to certify the app to be able to use the official Sonos API, due to this certification we where forced to drop the self build API in the app. Now you can only use the objects that are created automatically by adding them to the touch application.
There is no build in mechanisme to send HTTP commands to the app anymore in the new version.
We still can use the old .lp API by uploading it to the ftp folder, but i still need to make some adjustments as the old app performed a auto scan of Sonos devices on startup that is now missing in the .lp file, but i have no time this moment to do it.
BR,
Erwin