Universal Mobile Remote for AV and Multiroom Systems

Mobile App as Universal Remote for AV and Multiroom

We integrate and develop mobile apps that replace all remotes with a single smartphone. One tap — and your LG webOS TV starts Netflix, the Denon AVR-X receiver switches to HDMI 1, and the Sonos One plays a playlist in the living room. The stack is Flutter 3.x with a single codebase for iOS and Android, Kotlin Multiplatform for the gateway, and Node.js for the backend. With over 5 years of experience and more than 10 projects, we deliver reliable control.

Problems We Solve

Different protocols and incompatibility. A single home may use HDMI CEC (for Sony, LG TVs), IP Control (Denon, Yamaha), REST API (Sonos), UPnP (old streamers), and IR (Broadlink). Combining them into a unified interface is a non-trivial task. We implement a universal gateway on Node.js that converts and routes commands between protocols. For example, the "turn off everything" command sends a CEC signal via Pulse-Eight, an IP packet to the receiver, and an IR signal via Broadlink RM4. The gateway operates with latency under 100 ms.

Multiroom audio synchronization. Playing one source in multiple rooms with less than 1 ms latency is a technical challenge solved either by Sonos grouping (REST API) or by Snapcast on Raspberry Pi. Snapcast offers greater flexibility (open source, support for any audio streams), but Sonos is 5 times more accurate in synchronization (1 ms vs 5 ms). For tasks where sync is critical (video+audio in different rooms), we recommend Sonos; for background music, Snapcast. Cost savings on equipment when using Snapcast can reach $300 per zone, which is up to 3 times cheaper than Sonos Ports.

How Multiroom Audio Synchronization Is Achieved

Using Sonos grouping via local REST API provides latency <1 ms. For Snapcast, we configure a server on Raspberry Pi 4 with multiroom streaming. Each Snapcast client (ESP32 or Android) connects to the server via an Ogg stream. This approach can unite up to 6 zones with latency no more than 5 ms. One of our clients saved over $1,000 by integrating Snapcast for 4 zones instead of purchasing additional Sonos Ports.

How We Integrate Devices and What Stack We Use

Example: Sonos and Snapcast Integration

For a client with 6 rooms, we set up multiroom via Sonos Port in each zone. The Flutter app connects to the Sonos HTTP API and allows grouping zones, adjusting volume, and switching tracks. Additionally, we integrated Snapcast for local sources (Kodi media server). Result: a user starts a podcast in one room, and the same track plays in another with synchronization.

AV Control Protocols

HDMI CEC standard

Multiroom Audio

Comparison: Snapcast is 5 times less accurate than Sonos (5ms vs 1ms) but wins in flexibility and no brand lock-in. For large systems (10+ zones), Snapcast is more cost-effective — savings can reach $300 per zone.

Work Process

1. Analysis — equipment inventory, protocol identification, compatibility testing (2–3 days).
2. Design — backend architecture (gateway), mobile framework selection (Flutter/React Native).
3. Development — connection implementation, remote UI/UX, testing on real devices (3–6 weeks).
4. Integration — IR database setup (1000+ models), HomeKit binding.
5. Testing — load testing, offline mode verification.
6. Deployment — publish to App Store/Google Play, remote access configuration.

Timelines and What's Included

Basic integration (one protocol, one device) — from 3 weeks. Full remote (multiple protocols, multiroom, IR) — 2–4 months. Budget for a typical project varies depending on complexity: for simple systems from $5,000, for complex up to $25,000. The cost includes the app source code, backend gateway, documentation, testing on your equipment, and one month of support. Contact us for an accurate quote based on your equipment set.

How We Guarantee Quality

We use CI/CD (GitHub Actions, TestFlight), code review, and unit tests. Engineers hold Google (Flutter) and Apple (iOS) certifications. Over 10 multimedia smart home projects. Order a demo version in 2 weeks to evaluate control convenience.

Why Order Development from Us

Experience integrating dozens of protocols, proprietary developments (IR database of 1000+ models, Snapcast bridge). Warranty on all integrations for 6 months. Get a consultation — we will prepare a demo in 2 weeks.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.