# Sonos speakers not found / openhab bind’s to wrong interface? **URL:** \ **Category:** Bindings\ **Tags:** sonos, network, openhab3\ **Created:** [January 22, 2022, 9:49am UTC](https://community.openhab.org/t/sonos-speakers-not-found-openhab-bind-s-to-wrong-interface/132216 "2022-01-22T09:49:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![rickrack](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/5fc32e/32.png) [@rickrack](https://community.openhab.org/u/rickrack)\ **Post date:** [January 22, 2022, 9:49am UTC](https://community.openhab.org/t/sonos-speakers-not-found-openhab-bind-s-to-wrong-interface/132216/1 "2022-01-22T09:49:04Z")
Hey guys, I got an sonos issue here. Probably you guys are tired of this question already but I could need a hand here. So that’s the story: First the Sonos binding worked just fine. I used openhab 3.1 and the speaker was recognized immediately and worked like a charm. Then after the whole log4j security issue I updated my docker container from 3.1 to 3.2. Well I messed that update up and had to start over with a clean openhab 3.2 installation. That was on me and is not the point here. Anyways since OH3.2 the sonos speakers can’t be found anymore. I checked the documentation which says the boxes set the TTL to 1 and you have to make sure openhab is on the same network. So I checked the container and the network id of the container is assigned to network “host”. With that I would say they are on the same network. Then I did a tcpdump on the raspberry and hit the scan button on OH3 UI. During the scan I can see packets from the sonos speaker addressed to my raspberry. So the request from OH is sent and the answers at least received from the host. Next thing was a check on the openhab.log there is something which made me curious: ```auto 2022-01-21 21:00:38.831 [INFO] [.core.internal.i18n.I18nProviderImpl] - Time zone set to 'Europe/Berlin'. 2022-01-21 21:01:03.352 [WARN] [org.openhab.core.net.NetUtil] - Found multiple local interfaces - ignoring 169.254.106.54 2022-01-21 21:01:03.357 [WARN] [org.openhab.core.net.NetUtil] - Found multiple local interfaces - ignoring 169.254.202.26 2022-01-21 21:01:03.362 [WARN] [org.openhab.core.net.NetUtil] - Found multiple local interfaces - ignoring 169.254.19.221 2022-01-21 21:01:03.366 [WARN] [org.openhab.core.net.NetUtil] - Found multiple local interfaces - ignoring 172.18.0.1 2022-01-21 21:01:03.371 [WARN] [org.openhab.core.net.NetUtil] - Found multiple local interfaces - ignoring 172.19.0.1 **2022-01-21 21:01:03.376 [WARN] [org.openhab.core.net.NetUtil] - Found multiple local interfaces - ignoring 192.xxx.xxx.134** ``` OH finds multiple interfaces on the host. What’s pretty obvious for me, because there a there but the last line is my eth0 interface and got ignored. I believe now this is the reason for the sonos issue. Can I adjust to which interface openhab is binded? Any other ideas? Thanks for your help! Greetings rick ---
**Author:** ![Wolfgang\_S](https://community.openhab.org/user_avatar/community.openhab.org/wolfgang_s/32/52719_2.png) [@Wolfgang\_S](https://community.openhab.org/u/Wolfgang_S)\ **Post date:** [January 22, 2022, 10:25am UTC](https://community.openhab.org/t/sonos-speakers-not-found-openhab-bind-s-to-wrong-interface/132216/2 "2022-01-22T10:25:42Z")
Logged in as admin user go to settings =\> network. You can set the primary network address. ---
**Author:** ![rickrack](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/5fc32e/32.png) [@rickrack](https://community.openhab.org/u/rickrack)\ **Post date:** [January 22, 2022, 9:37pm UTC](https://community.openhab.org/t/sonos-speakers-not-found-openhab-bind-s-to-wrong-interface/132216/3 "2022-01-22T21:37:53Z")
Hey Wolfgang, Ok setting the IP was easy. How could I missed that? xD Unfortunately that did not help. Guess I have to turn on some debug logs and look deeper into into. ---
**Author:** ![Wolfgang\_S](https://community.openhab.org/user_avatar/community.openhab.org/wolfgang_s/32/52719_2.png) [@Wolfgang\_S](https://community.openhab.org/u/Wolfgang_S)\ **Post date:** [January 22, 2022, 10:15pm UTC](https://community.openhab.org/t/sonos-speakers-not-found-openhab-bind-s-to-wrong-interface/132216/4 "2022-01-22T22:15:46Z")
> [@rickrack](#): > > Unfortunately that did not help. Did you do a restart of openhab service ? I assume that setting only applies after a restart of it. ---
**Author:** ![rickrack](https://community.openhab.org/letter_avatar_proxy/v4/letter/r/5fc32e/32.png) [@rickrack](https://community.openhab.org/u/rickrack)\ **Post date:** [January 23, 2022, 10:12am UTC](https://community.openhab.org/t/sonos-speakers-not-found-openhab-bind-s-to-wrong-interface/132216/5 "2022-01-23T10:12:08Z")
Yes sir… restarted the openhab container and just and case the sonos speaker