sonos

问题 The documentation currently available in Sonos Labs (Customising the Root Browse Container) states that it can either use the EDITORIAL, GRID or LIST DisplayMode. Is there any documentation available on how to achieve the display that Apple and Spotify use? 回答1: Thanks for your interest in highlighting your brand inside the Sonos app experience. Our partners are critical to our efforts to deliver joy to our listeners. We are excited to help partners find opportunities to shine on Sonos. The

问题 There is a option to customizing root node with EDITORIAL, GRID, or LIST using presentation map like below <?xml version="1.0" encoding="UTF-8"?> <Presentation> . . . <PresentationMap type="DisplayType"> <RootNodeDisplayType> <DisplayMode>GRID</DisplayMode> </RootNodeDisplayType> . . . </PresentationMap> . . . </Presentation> But how show screen like below 回答1: We are currently developing the documentation for this experience and will post to our documentation as soon as it becomes available.

问题 We use the Sonos Control API to control the Sonos Speakers in a Smart Home System. Now we seem to have hit the rate limit for the requests sent to the API. We get the error 429 Too Many Requests. As described here https://developer.sonos.com/build/direct-control/control/ this means that we have hit the rate limit of the Sonos API. But there is no detailed information about the limits. So I have the following questions: How much requests are allowed until the rate limit is hit? When is the

问题 We use the Sonos Control API to control the Sonos Speakers in a Smart Home System. Now we seem to have hit the rate limit for the requests sent to the API. We get the error 429 Too Many Requests. As described here https://developer.sonos.com/build/direct-control/control/ this means that we have hit the rate limit of the Sonos API. But there is no detailed information about the limits. So I have the following questions: How much requests are allowed until the rate limit is hit? When is the

问题 We use the Sonos Control API to control the Sonos Speakers in a Smart Home System. Now we seem to have hit the rate limit for the requests sent to the API. We get the error 429 Too Many Requests. As described here https://developer.sonos.com/build/direct-control/control/ this means that we have hit the rate limit of the Sonos API. But there is no detailed information about the limits. So I have the following questions: How much requests are allowed until the rate limit is hit? When is the

问题 We are controlling the sonos via a small IOT device. This device will be placed at the homes of our customers. In our home automation system we need to know the playbackstate + volume of the players/groups. At which polling rate can we ask these parameters ? We cannot use a cloud server to handle the subscription events. I tried to put a https webservice in the IOT device with a self signed certificate but this doesn't work. After I have posted the subscription I get a request in my

问题 I'm in the process of building a Sonos iPhone app with Swift using the Sonos API but have hit a stumbling block. I would like to detect when a state/volume / metadata change on my app when someone uses a different app or the hardware buttons. I believe that subscribing to events is the way forward. I have copied in the reference link below. Subscribe—Subscribe to group namespaces to receive events when states change, such as changes to volume or playback status. https://developer.sonos.com

问题 We are running the Sonos Self-Test Suite to validate our service implementation. All tests are green except the "ssl_validation test_support_secure_renegotiation". The related output from the test is [FAIL] SONOS.sonos.workflow.fixture.ssl_validation - There was an exception while scanning the domain (<our domain>) for secure session renegotiation: sslyze.utils.ctSSL.errors.SSLErrorSSL - error:140E0197:SSL routines:SSL_shutdown:shutdown while in init Our domains supports secure renegotiation

问题 I have the starting shell of a SMAPI service programmed in Node.js. The service is running off of a local IP address. When I goto the customSD page for my Sonos Play:1 and add the service details to it and it returns 'Success!' upon clicking submit. When I open the Sonos Controllers on both my desktop and mobile, the service does not show up in the list of music services you can add. I have logging on the server turned on to max and there are no connection attempts ( either SSL or HTTP ) at

问题 We've built a SMAPI implementation that is serving up audiobooks. We're able to browse books and play them, but we're running into problems getting reporting to work correctly. We saw that the reporting endpoints for SMAPI have been deprecated, so we're attempting to follow the directions from the "Add reporting" page. We added a reporting path at https://<our_service>/v1/reporting and added endpoints for requests to /context and /timePlayed off of that base path. We're able to hit them