Tesla Operating System Support via Local + Relay Connectivity

Important: If you are reading this and want this feature and are willing to be a tester please reach out.

Overview

Enable Tesla in-car browser control of the Echobox audiophile app by providing a reliable connection mechanism that works across hotspot, home networks, and event environments.

This feature should prioritize robust connectivity over zero-config discovery, given known limitations with local networking (mDNS, private IP access) in constrained environments like Tesla’s browser and public Wi-Fi.

Problem

Users want to control the Echobox app from a Tesla browser by connecting to a local web UI hosted on their Android device.

However:

• mDNS/Bonjour is unreliable across networks (blocked multicast, AP isolation, etc.)

• Tesla browser may not reliably support .local resolution or private IP access

• Event/show networks are often hostile to peer-to-peer discovery

• Relying solely on local discovery leads to inconsistent user experience

Goals

• Provide a consistent and user-friendly connection flow from Tesla browser → Echobox app

• Support offline/local-first usage where possible

• Ensure functionality works at:

  • Home networks

  • Phone hotspot

  • Live shows / public Wi-Fi

• Avoid breaking existing networking features (UPnP, local control)

Proposed Solution (Hybrid Approach)

1. Local Control Mode (Primary for Hotspot / LAN)

When enabled, the app:

• Starts a lightweight HTTP server on the device

• Optionally advertises via mDNS (_echobox._tcp)

• Displays connection info in-app:

  • Local IP URL (e.g. http://192.168.1.42:port)

  • mDNS URL (e.g. http://echobox.local:port)

  • QR code for quick access

  • Short pairing code

Notes:

• mDNS is treated as a bonus convenience, not required

• MulticastLock is only acquired while this mode is active

• Service names include unique instance IDs to avoid conflicts

2. Tesla Mode (Enhanced UX)

A dedicated mode optimized for Tesla usage:

• Automatically:

  • Enables hotspot (if possible)

  • Starts local server

• Displays a simplified “Connect your Tesla” screen:

  • Large QR code

  • Direct IP URL

  • Optional .local URL

3. Cloud Relay / Remote Access (Fallback)

For maximum reliability:

• App establishes an outbound secure tunnel (WebSocket/WebRTC/HTTPS)

• Generates a session URL:

  https://echobox.app/session/{id} 

• Tesla browser connects via public internet

Benefits:

• Works even if:

  • Local network blocks multicast

  • Tesla browser blocks private IPs

  • User is on restrictive Wi-Fi

4. Connection Priority Strategy

Client (Tesla browser) attempts:

1. Direct IP (fastest, most reliable locally)

2. mDNS hostname (.local) if supported

3. Cloud relay URL (guaranteed fallback)

Non-Goals

• Do not rely solely on mDNS for discovery

• Do not require users to configure routers or DNS

• Do not modify or interfere with existing UPnP functionality

Technical Considerations

Networking

• mDNS (UDP 5353) and UPnP/SSDP (UDP 1900) operate independently

• Ensure lifecycle isolation between:

  • mDNS advertising

  • UPnP discovery

  • HTTP server

Android Constraints

• Use MulticastLock only when needed

• Handle vendor-specific network behavior

• Keep services foreground when active to avoid throttling

Service Identity

• Include unique instance ID in:

  • mDNS service name

  • TXT records

  • Web UI session

Security

• Local mode:

  • Optional pairing code

• Relay mode:

  • Authenticated session tokens

  • Expiring URLs

UX Flow

1. User opens Echobox → taps “Connect Tesla”

2. App shows:

   • QR code

   • URL(s)

3. Tesla connects via:

   • Hotspot (recommended)

4. If local fails:

   • User uses relay URL

Risks & Mitigations

Success Criteria

• Tesla browser can consistently connect in:

  • Hotspot scenario ✅

  • Home Wi-Fi ✅

  • Public/show environments ✅

• Minimal user friction (≤ 2 steps to connect)

• No regression in existing networking features

Summary

Implement a hybrid connectivity model:

• Local-first (IP + optional mDNS)

• Cloud-backed fallback

This ensures reliability across real-world conditions while still supporting zero-config discovery where available.