Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    John-Jood
    @John-Jood
    @jishi It works ! Thanks a lot for your help !
    j
    @jasonthefirst_twitter
    Hey @jishi i know you dont have a move, but... my move has sort of disappeared? When i call for its state i get a response, but it’s wrong. And when i try to do anything else via the api, it times out. Any thoughts?
    Jimmy Shimizu
    @jishi
    @jasonthefirst_twitter does it frequently change IP? I'm assuming you can still control it via the sonos app. The api might not handle IP changes fully seamlessly, and those should be rare (since otherwise sonos in itself will be sad), if you have any means of logging the IP used by the move over time, that would help. In the meantime, a restart of the api should probably suffice.
    j
    @jasonthefirst_twitter
    Yeah app still works. Ive tried restarting with no luck. Ill try giving the Move a static IP, maybe that will help.
    Yeah i think that did the trick. Weird! Sorry ro bother you, love love love your work!
    Jimmy Shimizu
    @jishi
    Super strange, but glad it got sorted out.
    bayratt
    @bayratt
    @John-Jood I am also trying to run Chris Campbell's Qrocodile project, and having issues playing from Spotify (many of the commands work fine, but not all). Did you modify anything else besides the line in the package file mentioned above?
    John-Jood
    @John-Jood
    @bayratt For the moment i only tested "play/pause" command (which works) and didn't have the time to test the other ones. I'll keep you posted if i face any issues
    j
    @jasonthefirst_twitter
    Hey @jishi perhaps I spoke too soon. Now the Move is fine, but a couple of my other speakers (One SLs) are behaving weirdly. Seems like it's just timing out when I make a request to two of my six rooms. The error looks like this: {"status":"error","error":"connect ETIMEDOUT 192.168.1.22:1400","stack":"Error: connect ETIMEDOUT 192.168.1.22:1400\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)"}
    Ive restarted the API and the machine on which it's running... nothing changes. Any advice would be appreciated!
    j
    @jasonthefirst_twitter
    ok wtf seems like re-booting the speakers themselves might fix it? I'm so confused. :/
    ok turns out the restart fixed one speaker. the other still times out. ¯_(ツ)_/¯
    j
    @jasonthefirst_twitter
    so sorry to spam the chat, but I finally sorted a weird permissions issue and installed the freshest version of node, and that seems to have solved it (for now). fingers crossed!
    Jimmy Shimizu
    @jishi
    @John-Jood I think you should really keep track of the ip-addresses that your sonos gear use, to see if they are constantly changing. Also compare the ips that are timing out with the assigned ips of the players.
    John-Jood
    @John-Jood
    @jishi Are u sure this message wath for me ?
    j
    @jasonthefirst_twitter
    it was for me. And I will keep an eye on it; I'd been running it as a launch agent but now I've got it running in terminal so I can see the errors more clearly
    and right now, as I'm doing nothing but having the api listen, it's basically cycling through my speakers with this error: WARN resubscribing to sid null failed
    Error: connect ETIMEDOUT 192.168.1.20:1400
    the IP address stays the same for a few timeouts, then it seems to pick a new one
    Jimmy Shimizu
    @jishi
    @jasonthefirst_twitter but does any of your players actually have 192.168.1.20?
    j
    @jasonthefirst_twitter
    Yeah it did, I had made the IP static. But then I took that off, it was assigned a new one, and the API kept calling the old IP. restarted the API, and now I'm getting a new error: Got status 500 when invoking /MediaRenderer/AVTransport/Control","stack":"Error: Got status 500 when invoking /MediaRenderer/AVTransport/Control\n at Object.invoke (/home/pi/node-sonos-http-api/node_modules/sonos-discovery/lib/helpers/soap.js:99:10)\n at Player.play (/home/pi/node-sonos-http-api/node_modules/sonos-discovery/lib/models/Player.js:446:15)\n at promise.then (/home/pi/node-sonos-http-api/node_modules/sonos-discovery/lib/prototypes/SonosSystem/applyPreset.js:153:46)\n at processTicksAndRejections (internal/process/task_queues.js:86:5)"}
    idk man, things were working smoothly for so long and then things got weird. maybe around the time I added a sub to the system? tho not sure how that would mess things up. do you generally suggest ppl put all the speakers on static IP, or does that not usually make a difference?
    Jimmy Shimizu
    @jishi
    @jasonthefirst_twitter it normally doesn't make a difference, and a healthy network shouldn't change ip-addresses at all if the devices are constantly powered on. I don't see how a sub would affect anything. I would be surprised if the system works flawlessly outside of this api...
    j
    @jasonthefirst_twitter
    it mostly does. Every once in a while a speaker will be missing from the Sonos app or AirPlay, but pretty infrequently. Have you noticed any difference if the system is wired?
    acab
    @wasfret_twitter
    Hello all! I am having an issue with setting up macOS say command- I have inserted {"macSay": {
    "Voice" : "Joana"
    }
    };
    sorry, early send- I have inserted that following the 'var settings' section, but I am not sure if that is the correct place to put it, as it isn't changing from the default google voice
    Luke Nukem
    @lukenukemmp3_twitter
    hello there, i am trying to use this wonderful thing on a raspberry with Homebridge. i am able to download, install and start the service, but as soon as i close the terminal, the service is shutdown. how can i avoid this? thank you in advance
    lnguyenh
    @lnguyenh
    @lukenukemmp3_twitter there are many different ways, one of them is to have it run as a service. Google "systemd service" for example.
    Jimmy Shimizu
    @jishi
    Easiest might be to use pm2, it has options to install the systemd service and keep track of which node.js apps that you have started.
    @wasfret_twitter did you put that in settings.json? Also, voice is lower case, and Joana might not be a valid voice name on macos
    Luke Nukem
    @lukenukemmp3_twitter
    @lnguyenh thank you very much! but there is another issue. I dont use homebridge in its native form, but a HOOBS-Installation instead. Everytime i reboot the system, the directory "/node-sonos-http-api-master" is automatically deleted, so there is no .js to start. Sorry for the massive noobness.
    acab
    @wasfret_twitter
    @jishi I did, I will try messing with the case. thanks!
    Owain Williams
    @OwainWilliams
    Hi, is it just me or has Spotify removed the URI lookup? I can't seem to get it to work anymore
    http://192.168.0.32:5005/Study/spotify/play/6agCM9GJcebduMddgFmgsO this returns a success message but nothing actually plays or shows in my queue
    1 reply
    John-Jood
    @John-Jood
    @jishi Hi Jishi, i've got an issue while trying to read Playlists on Spotify with http://192.168.0.41:5005/salon/spotify/now/spotify:playlist:3xN6J0LCyVj8k1gVCguWRH or even http://192.168.0.41:5005/salon/spotify/now/spotify:user:spotify:playlist:3xN6J0LCyVj8k1gVCguWRH
    Can you please help me with this issue ?
    John-Jood
    @John-Jood
    I face the following issue :
    {"status":"error","error":"Got status 500 when invoking /MediaRenderer/AVTransport/Control","stack":"Error: Got status 500 when invoking /MediaRenderer/AVTransport/Control\n at Object.invoke (/home/pi/Developer/node-sonos-http-api/node_modules/sonos-discovery/lib/helpers/soap.js:99:10)\n at Player.trackSeek (/home/pi/Developer/node-sonos-http-api/node_modules/sonos-discovery/lib/models/Player.js:552:15)\n at /home/pi/Developer/node-sonos-http-api/lib/actions/spotify.js:38:56\n at processTicksAndRejections (internal/process/task_queues.js:93:5)"}
    acab
    @wasfret_twitter
    hello! I'm having trouble getting the node to load my settings.json file
    should I delete the settings.js file? everything starts up fine but it isn't accepting my macSay addition or my spotify keys for search
    I'm running this on a mac, I should mention. my settings.json file reads like this-
    and it is in the root directory of the server
    acab
    @wasfret_twitter
    nevermind! had made a couple of syntax errors! got it up and running
    Owain Williams
    @OwainWilliams
    Is this room actually used anymore?
    John-Jood
    @John-Jood
    Yes i had the opportunity to get some help from @jishi a couple of days aga
    Owain Williams
    @OwainWilliams
    @John-Jood Did you manage to solve the 500 status error? I'm having something similar.
    John-Jood
    @John-Jood
    @OwainWilliams Yes i did. To be honest i'm totally sure that what i did change anything but now it works.
    I just had to set environment variables for Spotipy on my Rasperrby PI see : https://spotipy.readthedocs.io/en/latest/#authorization-code-flow
    murmeltier08
    @murmeltier08
    Thank you for the project. Work fine ! :)
    adeighton
    @adeighton

    I'm using this project (which is awesome) to do voice announcements from a home automation system. It issues commands like http://192.168.2.51:5005/saypreset/firstfloor/Woop%20there%20it%20is/Matthew/5 I set a preset firstfloor.json file as below:

    {
      "players": [
        {
          "roomName": "1. Family Room",
          "volume": 50
        },
        {
          "roomName": "1. Library",
          "volume": 50
        },
        {
          "roomName": "0. Ruff Playroom",
          "volume": 50
        }
      ],
      "pauseOthers": false,
    }

    What is strange is that regardless of setting on "pauseOthers", either true or false, it always pauses the other players in the house. So, as the voice announcement plays, the other zones, if they're playing something, pause and then resume after the announcement. It seems that /saypreset/ doesn't respect the pauseOthers flag. I looked through the code, and don't see how it works exactly. I was wondering if this is a known thing?

    1 reply
    mnipaiaf
    @mnipaiaf
    To start with: Thanks for a great job. This has really made communicating with my Sonos devices a whole lot easier. For example I'm now using this to play vinyl records on my sonos speakers by the click of a smart button attached to the vinyl player.
    However, I am having some problems with getting the info of what is being played on my speakers (I am talking about songs from Spotify here, obviously I understand I can't get track data when playing line-in vinyl...). When I call "state" I get an almost empty "currentTrack" where only the uri is set (to "x-rincon:...."). Other variables (such as elapsedTime, which always seem to return "24") are also giving incorrect values.
    1 reply
    paul-thomas1964
    @paul-thomas1964
    I've just setup a new rasp pi, and cant get the text to speech to work. I've updates settings.json with my voicerss api key. The browser returns success from the request, but nothing comes out of the sonos and the terminal log shows 2021-01-16T16:24:16.816Z ERROR
    { error: 'action \'tts\' not found' }
    My old PI does this ok with the same voicerss api key. Any ideas? Thanks
    29 replies
    j
    @jasonthefirst_twitter
    Hey y’all, having a weird response time issue. I’m using some clips I made to function as ‘bells’ for my kid’s virtual school. So ive set up an automation to run a shortcut on my phone a minute or two before she needs to log back on. Shortcut just calls the URL to play the clip. It used to be quite quick, but things have slowed down and now it’ll be 2-3 minutes before the clip will play. This morning i even had a request time out, according to shortcuts, and then a minute later the clip played.
    1 reply
    Anyone experience this before or have thoughts on what could be causing this?