From 2c83f0f003b90b0ab5c4788e89fe27d87929da40 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Fri, 5 Jun 2020 12:34:24 -0500 Subject: [PATCH] Note that sonos will now try port 1400 first and then increment if it is in use (#13672) --- source/_integrations/sonos.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/sonos.markdown b/source/_integrations/sonos.markdown index 3df1e2937ac..aa9bf4517b0 100644 --- a/source/_integrations/sonos.markdown +++ b/source/_integrations/sonos.markdown @@ -149,7 +149,7 @@ sonos: interface_addr: 192.0.2.1 ``` -The Sonos speakers will attempt to connect back to Home Assistant to deliver change events (using TCP port 1400). You can change the IP address that Home Assistant advertises to Sonos speakers. This can help in NAT scenarios such as when _not_ using the Docker option `--net=host`: +The Sonos speakers will attempt to connect back to Home Assistant to deliver change events. By default, Home Assistant will listen on port 1400 but will try the next 100 ports above 1400 if it is in use. You can change the IP address that Home Assistant advertises to Sonos speakers. This can help in NAT scenarios such as when _not_ using the Docker option `--net=host`: ```yaml # Example configuration.yaml entry modifying the advertised host address sonos: