Skip to main content

Hey guys,

Unlike a bunch of people here in this community I'm happy to not have experienced any issues with my Sonos system that got introduced with the bigger update in May. In fact I'm pretty satisfied with my system and I've been a Sonos user for over 11 years now. When Sonos removed the "analytics" feature about 4-5 years ago, I saw some people complain that it was gone, so I decided to bring this feature back when I have time. So here it is. Feel free to register and check it out: https://audio.report

Current scope:

  • Measure and visualize your sonos usage

  • Compare your usage to the community (not the sonos community, but people registered with the service)

  • Display recently played tracks (my wife was constantly asking questions about songs that I played days ago, so this one is for the ladies)

  • Send weekly summaries

In case you have any feedback, feel free to reach out to me. In case you wonder about my motivation, you can read my FAQs on the website mentioned above.

Cheers,

Joschi

Pretty site: but I see no data.

Also there’s a typo in the FAQ (“adress”).

Ah now I read it more closely, I see I have to sign up before it will collect anything. Which makes sense based on how the API works, now I think of it.

Pretty site: but I see no data.

Also there’s a typo in the FAQ (“adress”).

Thanks for mentioning the typo! I wonder how you got to the page before registering!? Maybe I need to fix a bug...

Trust a programmer to also be a hacker ;)

Trust a programmer to also be a hacker ;)

Well my biggest mistake is, that I’m obviously not Sonos :-D

And of course it’s a pitty that Sonos’ idea of opening up it’s platform to third party applications is not yet ideal. I see two vectors for improving trust:

  1. Allow users to revoke third party application grants
  2. Offer more fine grained control over granted scopes. Currently it’s only full system control, which I don’t need...

I was teasing ​@controlav . Not being a programmer myself, I don’t really have an informed opinion on the ‘openness’ of the Sonos API, which doesn’t color my appreciation of those who write their own clients…especially given I’ve never seen any Sonos commitment to that process. I’d assume Sonos might change the underlying structure at any moment, and frustrate the third party coders who don’t stay on top of their code base. But I just am not aware. 

Reply


Terms & ConditionsCookie settings