![]() Try to connect to HA using another device in the same subnet as the Sonos devices.Validating why it's not working is a dependent on the network setup & equipment in place. This should only really be necessary if there's a NAT in place or if there's a Docker network misconfiguration. In this case, the HA would be listening on its 1.2.3.4 interface but the Sonos devices would be trying to reach 5.6.7.8. Additionally it will tell you what IP that HA is advertising as (i.e., is telling Sonos devices to connect to instead of the listening IP). It will tell you what IP:port that HA is listening on and the IP of the Sonos device that can't reach it. See this example error message for how it will look in the Repairs message in a future version. ![]() Isolating Sonos devices in a secured VLAN is not trivial, and if it's not working properly can introduce significant problems to performance and reliability. Something like UDP Broadcast Relay on OPNsense could be used for this.ĭoes your Docker config expose the HA IP as you expect, and does port 1400 need to be opened on the container? Besides appropriate firewall rules, you would also need a tool which re-broadcasts broadcast/multicast packets across subnet boundaries. Discovery relies on multicast (mDNS and/or SSDP) which does not route between subnets. This is why your Sonos app only works if you connect to the same network as your speakers and why you need to add a YAML config for the integration. That being said, you also have the problem of discovery not working across subnets.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |