search

jishi / node-sonos-http-api

An HTTP API bridge for Sonos easing automation. Hostable on any node.js capable device, like a raspberry pi or similar.
http://jishi.github.io/node-sonos-http-api/
MIT License
1.83k stars 462 forks source link

Feature request: endpoint to show current household_id #786

Open hankhank10 opened 3 years ago

hankhank10 commented 3 years ago

Given the move to S2 I have found that many more users are now running dual S1 and S2 systems on the same network. This has led to many more errors reported by users of my vinylemulator project (https://github.com/hankhank10/vinylemulator) that the system is failing to find their zones (because it is connecting incorrectly to the wrong system).

I would make two suggestions:

  1. In the readme around settings.json include the "household" as an example - it is currently described but an example is not given in the sample json (happy to do a pull request on the readme if you like - let me know)

  2. Add an endpoint to the node server (eg "/household") which returns the current household_id to which it is connected. This is much more user friendly for users to populate their settings.json than having to connect to the base sonos api which entails working out a Sonos player IP address and fighting through Sonos' horrible API

gjuecat commented 3 years ago

I'm also using a dual S1 and S2 system and added the household in the settings.json file but it is not working. We have 3 household in our network and I always get the wrong speaker.

That's my settings.json:

{
    "household": "HHID_Ts...........X_2"
},

{ 
    disableIpDiscovery: true
}
gjuecat commented 1 year ago

any updates on this? still having the same problem

jsiegenthaler commented 1 year ago

I for one would really appreciate a new release. Last release of this API was over 5 years ago