What Runs on Port 1400
Port 1400 is the local control interface for Sonos smart speakers. Every Sonos device on your network listens on this port for HTTP and SOAP (Simple Object Access Protocol) commands that control playback, volume, grouping, and device settings.
When you tap "play" in the Sonos app, behind the scenes your phone sends an HTTP request to port 1400 on the speaker. When home automation systems like Home Assistant control your speakers, they're talking to port 1400. When third-party apps integrate with Sonos, they're sending commands to port 1400.1
This is the nervous system of the Sonos ecosystem—the port where control happens.
How It Works
Sonos speakers expose several interfaces on port 1400:
UPnP Services — The device description file at http://{speaker-ip}:1400/xml/device_description.xml documents all available services. These UPnP services handle everything from playback control to network configuration.
SOAP Protocol — Control commands use SOAP to call specific Sonos services. Want to change the volume? Send a SOAP request to the RenderingControl service. Want to play a track? Call the AVTransport service.2
HTTP Endpoints — Simple status queries use plain HTTP:
http://{ip}:1400/status/info— Device information (player ID, serial number, group ID, versions)http://{ip}:1400/status/batterystatus— Battery level for portable speakershttp://{ip}:1400/status— Connection and network information1
Event Subscriptions — Applications can subscribe to events from Sonos services. When something changes (track ends, volume adjusts, speaker joins a group), Sonos pushes notifications back to the subscriber. This is why Home Assistant needs speakers to connect back to port 1400 on the server—push updates flow both ways.3
The Unassigned Port That Found Its Purpose
Port 1400 sits in the registered port range (1024-49151). These ports are registered with IANA for specific services, but registration isn't mandatory and enforcement doesn't exist. Sonos chose 1400, started using it, and now it's the de facto standard for Sonos control.
No RFC defines it. No standards body blessed it. But thousands of Sonos speakers worldwide answer to port 1400, and an entire ecosystem of third-party tools depends on it.
This is how ports often work in practice—a company needs a port, picks one from the registered range that isn't conflicting with anything else they use, and starts listening. If the product succeeds, the port number becomes associated with that use.
Why This Matters for Home Networks
If you run Sonos speakers, port 1400 needs to be reachable on your local network. Firewalls between VLANs can break Sonos functionality if they block this port. Network segmentation strategies need to account for it.
Home automation systems need bidirectional access—they send commands to port 1400 on speakers, and speakers send event notifications back to port 1400 on the automation server.3
Port forwarding this to the Internet would be a terrible idea. These speakers expect to be on a trusted local network. There's no authentication on these endpoints. Anyone who can reach port 1400 can control your speakers.
Checking What's Listening
To see if something is listening on port 1400:
On Linux/Mac:
On Windows:
Query a Sonos speaker directly:
If you get back JSON with device information, you've found a Sonos speaker.
Related Ports
- Port 1443 — Sonos HTTPS endpoint for secure connections
- Port 3400, 3401, 3500 — Additional Sonos communication ports
- Port 1900 — SSDP (Simple Service Discovery Protocol) used by Sonos for device discovery4
Frequently Asked Questions About Port 1400
Byla tato stránka užitečná?