# Sonos Say **URL:** \ **Category:** Apps\ **Created:** [January 13, 2019, 12:30pm UTC](https://community.homey.app/t/sonos-say/6697 "2019-01-13T12:30:29Z")\ **Posts on this page:** 20\ **Page:** 4
**Author:** ![Martin\_van\_der\_Aart](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin_van_der_aart/32/9658_2.png) [@Martin\_van\_der\_Aart](https://community.homey.app/u/Martin_van_der_Aart)\ **Post date:** [July 1, 2020, 9:32pm UTC](https://community.homey.app/t/sonos-say/6697/61 "2020-07-01T21:32:06Z")
Did you also type in the port 5005 It looks like it is already preset in the app Connection Settings under the IP adres, but you still have to type it in. After that it worked for me, all speakers were found ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [July 2, 2020, 2:04pm UTC](https://community.homey.app/t/sonos-say/6697/62 "2020-07-02T14:04:02Z")
Don’t think it matters what he has entered, if he gets a 404 page it means the docker image doesn’t work as expected. @Henk_Renting did you check the docker image? If need any help with it, maybe we can help? ---
**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\ **Post date:** [July 2, 2020, 3:37pm UTC](https://community.homey.app/t/sonos-say/6697/63 "2020-07-02T15:37:48Z")
That would be great @Martijn! I am sure the problem lies in the Docker image too. When the container is started, it runs for a few seconds and the gets automatically restarted. Over and over again. When I try to setup the folders as you mentioned in your post below: > [@Sonos Say](https://community.homey.app/t/sonos-say/6697/31): > > Yes, installed on my Synology too. Setting up the folders is very easy and can be done with the same gui as you are using. I’ve set it up like this: Doesn’t help however. @Joka also tells you to create a settings file. This is only needed if you want to deviate from the default settings. The manual suggest to create a settings file with only in it. If you want to use Voicerss instead of the Google API, which is default, then you would enter some settings into the settings file. I’ve… I: - select the image - choose edit - choose volume - click add folder - go to docker/sonos/settings (folders which I added) and click Select ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/0/e094dcdbbc9b9d4621bcfa4e5a3c4c4c53d4995d.png) But then… I cannot type app/settings, as it says it is an incorrect value ☹ Any idea? ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [July 3, 2020, 8:16am UTC](https://community.homey.app/t/sonos-say/6697/64 "2020-07-03T08:16:18Z")
I’ll try to show how I did it: **Step 1: Add Registry:** _You already did this step, but for the whole story, I think it is important to have the correct registry_ Open Docker, go to registry and search for “chrisns”. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/c/4cd1e98f9f8f3999f64b0b9ad3825a8657d47890.png) There you see the ‘docker-node-sonos-http-api’, click this and hit the ‘download’ button. Leave ‘latest’ and hit OK. The image will be downloaded now. **Step 2; Create container** Go to ‘image’ and search the docker-node-sonos-http-api image. Click it and hit the ‘launch’ button: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/e/a/eafdc1dbf9b39d7c83fe882347e9699e03761736.png) **Step 3; Configure container** Give the container a meaningful name, or leave it as is, but that’s up to you. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/d/c/dc81e2a57d3350f25de6136dff283eefca8e0f9b.png) Hit the ‘Advanced Settings’ button. On the ‘Advanced Settings’ page, check the ‘enable auto-restart’ option. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/4/24012176c3da0f7230273b41d682eecb2b00a9ae.png) On the ‘volume’; _this is where the volumes get created, but only once. The reason ‘we’ do this is to keep persistence across docker image updates. What we basically do is expose local directories on your NAS to the docker container for it to use these directories and files inside the container._ According to the manual we need to have 4 folders: - clips - settings - cache - presets If these are not present, we are going to create these during this setup, if they are present, then just select them and do not create them. Hit the ‘add folder’ button: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/7/1771d61301175a1602ddcd00124a3cd171993c84.png) Browse to the folder you want to create the ‘new’ folders in. And select it (!DO NOT click the select button just yet). _What I typically do is create a new folder with a name corresponding to the docker image and create subfolders inside it._ Click the ‘create folder’ button and give it the first name of list above (eg clips). When the folder is created hit the ‘select button’. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/c/a/ca9d4e5c64a161a68b21efb693422fdcebca1af3.png) The folder will be added to the list: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/4/f43a0bed32fa0273846e468a728bc66b92ce5ea6.png) Now we have to add a mount path, these are the following: - clips → /app/static/clips - settings → /app/settings - cache → /app/cache - presets → /app/presets Repeat these steps to create / select all folders, it should look like the following: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/7/77930ad20ae09ef31e81ba910cb95e9cfe0ada34.png) Go to the tab ‘network’ and check the ‘Use the same network as Docker Host’. _This makes sure the image uses the ‘ports’ on host (your NAS) also called the ‘host’ network. Be sure there is nothing else running on port 5005, which is used by this image. If port 5005 is already in use by another application / docker or whatever, the image creation will fail._ ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/4/6/46f827899950767d83812398cd2173e28831dc77.png) There are no other settings needed, so hit the ‘Apply’ button on the bottom of the screen. Now if everything is set up, hit the ‘next’ button: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/4/748b360cae594587dba48c5ec77fe7a0cbd604a1.png) On the Summary page, all settings are displayed again for a final check, hit ‘apply’ if you agree with hit. And since the checkbox is checked to start the container after hitting ‘apply’, it should now start. Uncheck it if you want to do the final steps too. ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/5/75a09c1accad3600ff2cfdbdc9e87eb609cfda53.png) The final steps: 1. Open powershell (or terminal if using mac) window and type “ssh username@nas-ip” (replace username with your admin account and the nas-ip with the IP address or hostname of your NAS device). 2. Enter yes at accepting the key 3. Enter your password 4. enter the command: “sudo su -” The dash sign on the end is important. Now enter your password again. 5. Be sure the container is not running and change to the container directory, you have created it during the previous manuel. (cd /volume1/docker/sonos for example) 6. Enter the following commands: > ``` > curl https://raw.githubusercontent.com/jishi/node-sonos-http-api/master/presets/example.json > presets/example.json > echo {} > settings/settings.json > > ``` 1. type exit and exit again and start the container. More info can be found on [GitHub - chrisns/docker-node-sonos-http-api: Docker wrapper for https://github.com/jishi/node-sonos-http-api](https://github.com/chrisns/docker-node-sonos-http-api). There you go. Hopefully it works for you. //updated the steps to include the last (optional) steps too ---
**Author:** ![Henk\_Renting](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/henk_renting/32/87634_2.png) [@Henk\_Renting](https://community.homey.app/u/Henk_Renting)\ **Post date:** [July 3, 2020, 1:24pm UTC](https://community.homey.app/t/sonos-say/6697/65 "2020-07-03T13:24:43Z")
Hi Martijn, That is one extended and clear manual! Thanks! Unfortunately the container keeps (crashing and) restarting… ☹ - So I have: uninstalled/remove the container and all settings from Docker. - Uninstalled Docker, checking that all containers have to me removed as well - Restarted my Synology - Installed Docker - Followed your instructions, just as you wrote But no luck. The container keeps restarting… ☹ I am afraid something else is wrong here… ---
**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\ **Post date:** [July 3, 2020, 4:28pm UTC](https://community.homey.app/t/sonos-say/6697/66 "2020-07-03T16:28:20Z")
![chrome_2020-07-03_18-27-21](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/a/fa16bfb325c547a90b266758ae0d614d64a46fa4.png) @Ludvig ^^ Downloaded 2.0.1 from community app-store and get this when searching for speakers. ![chrome_2020-07-03_18-30-53](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/a/0/a0a97463301d64a3259a88121b1fd24e5b4a4305.png) Docker running on a Synology and guide followed from Martijn ---
**Author:** ![Ludvig](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ludvig/32/129091_2.png) [@Ludvig](https://community.homey.app/u/Ludvig)\ **Post date:** [July 3, 2020, 4:43pm UTC](https://community.homey.app/t/sonos-say/6697/67 "2020-07-03T16:43:02Z")
Mm have sen this before. Don’t know why. Uninstall the app and install it again. Solved it for me. @MadMonkey do you know why? ---
**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\ **Post date:** [July 3, 2020, 4:51pm UTC](https://community.homey.app/t/sonos-say/6697/68 "2020-07-03T16:51:06Z")
Synology is complaining about a missing settings.json? ---
**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\ **Post date:** [July 3, 2020, 4:53pm UTC](https://community.homey.app/t/sonos-say/6697/69 "2020-07-03T16:53:25Z")
![chrome_2020-07-03_18-39-47](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/3/73719da54c111f6dd4dbb25ab48db0f01d31341d.png) ---
**Author:** ![Ludvig](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ludvig/32/129091_2.png) [@Ludvig](https://community.homey.app/u/Ludvig)\ **Post date:** [July 3, 2020, 5:05pm UTC](https://community.homey.app/t/sonos-say/6697/70 "2020-07-03T17:05:51Z")
Mm that’s because you can setup a custom configuration in node-Sonos. Have custom zones etc. that should not be the problem here. Sounds like a homey issue. Did the reinstall help? ---
**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\ **Post date:** [July 3, 2020, 5:52pm UTC](https://community.homey.app/t/sonos-say/6697/71 "2020-07-03T17:52:28Z")
Yes it did, thnx ---
**Author:** ![Ludvig](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ludvig/32/129091_2.png) [@Ludvig](https://community.homey.app/u/Ludvig)\ **Post date:** [July 3, 2020, 6:34pm UTC](https://community.homey.app/t/sonos-say/6697/72 "2020-07-03T18:34:14Z")
Sweet. Feels like some kind of a Homey issue. Had the same issue and the same fix worked for me. ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [July 4, 2020, 11:41am UTC](https://community.homey.app/t/sonos-say/6697/73 "2020-07-04T11:41:48Z")
Yes there is probably something else wrong, but who knows. What you could try is to run the docker with elevated rights so it runs under root account. Do this by stopping the container and hitting the edit button. Over there you can check the box at execute container at high privilage, and hitting the yes button at the warning: ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/6/6/66eb17d0f10d8a9ffdc8891c2aae3a25c745af68.png) You also could try and create both the settings file and the example.json. 1. Open powershell (or terminal if using mac) window and type “ssh username@nas-ip” (replace usename with your admin account and the nas-ip with the IP address or hostname of your NAS device). 2. Enter yes at accepting the key 3. Enter your password 4. enter the command: “sudo su -” The dash sign on the end is important. Now enter your password again. 5. Be sure the container is not running and move to the container directory, you have created it during the previous manuel. (cd /volume1/docker/sonos for example) 6. Enter the following commands: > ``` > curl https://raw.githubusercontent.com/jishi/node-sonos-http-api/master/presets/example.json > presets/example.json > echo {} > settings/settings.json > > ``` 1. type exit and exit again and start the container. Hopefully it works, if not, i’m out of idea’s 😉 ---
**Author:** ![danone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/danone/32/115743_2.png) [@danone](https://community.homey.app/u/danone)\ **Post date:** [July 5, 2020, 1:20am UTC](https://community.homey.app/t/sonos-say/6697/74 "2020-07-05T01:20:14Z")
Thanks a lot the useful and comprehensive step by step guide @Martijn_Hoogenbosch the container run with no problems from the first try. On the other hand, the app would not find my speakers. Neither uninstall/install nor restarting the app fixed it. In the end a PTP sorted out. Hope this would help somebody. ---
**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\ **Post date:** [July 5, 2020, 9:54am UTC](https://community.homey.app/t/sonos-say/6697/75 "2020-07-05T09:54:07Z")
The app only finds speakers from my S2 app. Is it somehow possible to also discover the speakers on my other S1 app? ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [July 5, 2020, 12:32pm UTC](https://community.homey.app/t/sonos-say/6697/76 "2020-07-05T12:32:15Z")
if you go to [http://IP:5005/zones](http://IP:5005/zones), do you see your S1 speakers listed? If not, the app won’t find them. ---
**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\ **Post date:** [July 5, 2020, 12:35pm UTC](https://community.homey.app/t/sonos-say/6697/77 "2020-07-05T12:35:50Z")
It just S2 speakers there. But there must be something, like filling some stuff in the settings file maybe? ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [July 5, 2020, 12:42pm UTC](https://community.homey.app/t/sonos-say/6697/78 "2020-07-05T12:42:31Z")
Mmm… cannot find any on the readme, [https://github.com/jishi/node-sonos-http-api](https://github.com/jishi/node-sonos-http-api), infact I only find S2 seems to be still supported… so they didn’t even know for sure it S2 was supported. It probably does a upnp / network scan and it probably has found your S2 system first. But that’s just a guess ---
**Author:** ![Rocodamelshekima](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rocodamelshekima/32/8209_2.png) [@Rocodamelshekima](https://community.homey.app/u/Rocodamelshekima)\ **Post date:** [July 5, 2020, 12:43pm UTC](https://community.homey.app/t/sonos-say/6697/79 "2020-07-05T12:43:03Z")
![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/2/a/2adda02d278d17fc151db3c7bb12b92268f0235b.jpeg) ---
**Author:** ![Martijn\_Hoogenbosch](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martijn_hoogenbosch/32/10647_2.png) [@Martijn\_Hoogenbosch](https://community.homey.app/u/Martijn_Hoogenbosch)\ **Post date:** [July 5, 2020, 12:49pm UTC](https://community.homey.app/t/sonos-say/6697/80 "2020-07-05T12:49:46Z")
I can only find HouseholdControlID in the url they mention, but don’t know what to do with this in the settings.json…good luck 😉 [Previous page](https://community.homey.app/t/sonos-say/6697.md?page=3) [Next page](https://community.homey.app/t/sonos-say/6697.md?page=5)