DSH Plugins Marketplace

DSH Plugins

Plugins

/

dsh-watch-phone

d

dsh-watch-phone

Manifest valid

Talk to your local DSH from a smartwatch: HTTP bridge with chat, offline STT/TTS and the watch APK bundled.

hasBundlePatch

dsh-watch-phone

Hold-to-talk chat between an Android smartwatch — or any other Android phone — and DeepSeek Harness running on your phone (or on a PC — anything that runs DSH).

Press the green pill, speak, release: the audio is transcribed on the DSH host, the transcript lands in the text box so you can fix what the recogniser misheard, and after you press send it goes to a real DSH session (the same one you see in the app, with your preset, persona and model). The reply is spoken back with a local TTS voice. No cloud round-trip for the client itself, and no keyboard on a 240 dp round screen.

One APK serves both: the layout is a two-row composer below 320 dp of width (the watch) and a normal single-row composer above it (every phone), so a second handset can talk to the same bridge without a second build.

watch APK  ──HTTP──▶  this plugin (0.0.0.0:38402)
   │                    ├─ POST /chat → DSH agent session → reply text
   │                    ├─ POST /stt  → ctx.get('speechToText')  (local ASR)
   │                    └─ POST /tts  → MiMo speech API (local cache) or fallback proxy
   └─ bundled at /watch/app.apk

Requirements

  • DSH 0.2.1-rc.2 ≤ version < 0.3.0 (tested against 0.2.2-rc.1).
  • For local speech-to-text: a build with the speechToText service (e.g. the official @deepseek-ai/dsh-experimental-speech-to-text-sensevoice bundle). Without it /stt returns 503 and the watch reports “没听清,再说一次”.
  • For local text-to-speech: a Xiaomi MiMo sk-… key (https://api.xiaomimimo.com/v1), or set proxyBase to another machine that answers /tts.
  • An Android watch that can run the bundled APK (built and verified on a 480×480 round AMOLED watch, Android 14 / armv7).

Install

# 1. the bridge
dsh plugin --profile <your-profile> add dsh-watch-phone

# 2. the watch app: the bundle ships the APK, fetch it from the bridge
curl -O http://<host>:38402/watch/app.apk
adb install -r app.apk
adb shell pm grant com.dsh.watchchat android.permission.RECORD_AUDIO

The client finds the host by itself, on whatever network the two devices happen to share — hotspot, home Wi-Fi, office Wi-Fi, a new subnet after DHCP moved the phone. In order it tries:

  1. the address saved in its settings,
  2. the last addresses that worked (rolling list of 8),
  3. a UDP broadcast probe — the bridge answers dsh-watch? on port 38403 with {"service":"dsh-watch-phone","port":38402,"urls":[…]},
  4. mDNS / DNS-SD — the bridge publishes _dsh-watch._tcp.local,
  5. a scan of every local /24 for port 38402,
  6. the documentation-range defaults as a last resort.

Anything it finds is verified with GET /health before being adopted, so a stale address is never silently kept. You can also type an address in — tap the status line at the top, or long-press the chat area.

Build the watch app yourself

The prebuilt APK is only signed with a throwaway key, so rebuild it if you want to change the UI. The full Android source lives in watch-app/ — JDK 17, Gradle 8.7 (wrapper included), SDK 34:

cd watch-app
echo "sdk.dir=/path/to/Android/Sdk" > local.properties
./gradlew assembleRelease        # add keystore.properties to sign it
adb install -r app/build/outputs/apk/release/app-release.apk

The watch has no text-to-speech service and no SpeechRecognizer (Xiaomi ships neither), which is exactly why all speech work happens on the phone: the watch records a WAV, posts it to /stt, shows the reply, and plays whatever /tts returns.

Repository layout

PathWhat it is
index.js, cordis.patch.yml, locale/, docs/, icon.svgthe plugin bundle itself (dsh.bundle.patch)
assets/dsh-watch-chat.apkthe prebuilt watch client served by GET /watch/app.apk
watch-app/full Android source of that client (Gradle project, no keystore)
tools/scan-ports.mjsfinds a watch's random wireless-debugging port (node tools/scan-ports.mjs <ip>)
pc-bridge/the desktop-only predecessor: a PC DSH plugin with Vosk speech-to-text and SAPI text-to-speech, plus the /relay TCP helper used to reach a watch's wireless-debugging port from another subnet
.github/workflows/build-watch-app.ymlcompiles watch-app/ on every push and uploads the unsigned APK
.github/workflows/publish.ymlpublishes the bundle to npm through Trusted Publishing (OIDC, no token)

Everything in this repository is sanitised: addresses are documentation ranges (RFC 5737 — 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24), Wi-Fi names and hotspot passwords are placeholders, and no keystore, device serial or machine path is committed. pc-bridge/ resolves its paths from the file location or from DSH_WATCH_BRIDGE_DIR / DSH_PHONE_DIR / DSH_PYTHON.

Configuration

Add these keys to the bundle's row config (cordis.patch.yml):

KeyDefaultMeaning
port38402HTTP listen port (all interfaces).
discoveryPort38403UDP port that answers the client's dsh-watch? broadcast with the bridge's URLs.
token''When set, every route except /health, /log and /watch/app.apk requires Authorization: Bearer <token>.
sessionIdwatch-voiceDSH session id the watch talks to. Reused if it already exists.
cwdprocess.cwd()Working directory for that session.
allowExecfalseEnables POST /exec (shell on the host). Leave off unless you know why.
allowRelayfalseEnables POST /relay (raw TCP relay, used to reach a watch on another subnet).
proxyBase''Fallback host for /stt and /tts, e.g. http://192.0.2.10:38401.
logFile<home>/.dsh/watch-phone/bridge.logBridge log; recordings are archived next to it in rec/.
tts.apiKey—MiMo key. If omitted, the plugin reads the local-voice plugin's saved settings (/root/.dsh/dsh-go/plugins/local-voice/data/settings.json).
tts.baseURLhttps://api.xiaomimimo.com/v1MiMo endpoint.
tts.modelmimo-v2.5-ttsAlso supports mimo-v2.5-tts-voicedesign.
tts.voiceBingTangVoice id (e.g. 冰糖).
tts.instruction''Optional style instruction sent as the first message.

Example that keeps the shell off but pins the voice:

- id: watch-phone
  name: dsh-watch-phone
  config:
    port: 38402
    sessionId: watch-voice
    tts:
      apiKey: sk-...
      voice: 冰糖

HTTP API

RouteMethodBodyResult
/healthGET—{ ok, service, host, platform, uptime, stt, chat, features }
/chatPOST{"text":"…"}{ ok:true, reply } — goes through a real DSH session when @deepseek-ai/dsh-agent is resolvable, otherwise straight to the model
/sttPOSTmultipart (audio) or raw WAV{ ok, text, bytes, language, seconds, peak, gain }
/ttsPOST{"text":"…"}audio/wav bytes
/resetPOST—clears the conversation
/logGET?lines=80tail of the bridge log
/watch/app.apkGET—the bundled watch APK
/execPOST{"cmd":"…"}{ ok, code, stdout, stderr, ms } — needs allowExec
/relayPOST/GET{port,targetHost,targetPort}starts / lists TCP relays — needs allowRelay
/configGET/POST{"allowExec":true}loopback only: read or flip the runtime switches; remembered in ~/.dsh/watch-phone/settings.json

Flipping the operator switches on a phone

allowExec and allowRelay deliberately cannot be turned on from the LAN. On a phone you reach loopback with adb, so the switch stays available without exposing it:

adb forward tcp:13842 tcp:38402
curl -s http://127.0.0.1:13842/config                                  # read
curl -s -X POST http://127.0.0.1:13842/config -d '{"allowExec":true}'  # enable

This is how the watch is deployed over a hotspot: allowRelay lets the host open a TCP tunnel to the watch's wireless-debugging port while adb stays on the PC.

Verified on hardware

Last end-to-end run: 2026-11-18, bundle 0.1.8.

WhatSetupResult
Cross-subnet discoverywatch on the phone's own hotspot (10.x), bridge on the Wi-Fi addresswatch broadcast dsh-watch?, got the URL list, GET /health 200, chat round-trip
Second handset as a clientanother Android phone on the same Wi-Fi as the bridgediscovered over broadcast with no configuration, phone layout (single-row composer), chat round-trip
Third-party probePC on the same Wi-Fi, raw UDPreply listed all three interfaces: hotspot, Wi-Fi and cellular
Local ASRsynthesised Mandarin WAV posted to /stt{"text":"今天天气怎么样?","seconds":2.45}, sensevoice-local, language:auto
Dictation does not sendheld the watch microphone while audio played nearbytranscript appeared in the input box + toast, chat area stayed empty — nothing was sent
One session everywherewatch, phone and second handset at onceall three talk to the same watch-voice session, so the history is shared by design

Two device-side quirks worth knowing when you automate a deployment: a Xiaomi/HyperOS phone refuses adb install until Settings → Developer options → Install via USB is allowed, and adb shell input text does not reach text fields unless USB debugging (Security settings) is on. Neither affects the app itself.

Notes and limits

  • Speech never sends itself. The transcript is written into the input box (cursor at the end) and a toast says so; you read it, fix it, then press send. That is the difference between a dictation shortcut and a chat app that mis-sends a garbled question.
  • Discovery needs the two devices on the same L2 segment for the broadcast/mDNS steps; the /24 scan covers most home and office networks, and the manual address entry always works. Some Android builds drop broadcast UDP with the screen off — that is why the saved and recent addresses are tried first, and why mDNS and the /24 scan are kept as fallbacks.
  • /stt normalises any WAV to 16 kHz mono 16-bit and lifts quiet recordings (peak < 6000 → up to 40× gain), because watch microphones record very low.
  • The reply is read from the last assistant message of the finished turn, and only its text parts — reasoning and tool calls are never spoken.
  • Sessions are real DSH sessions: the chat shows up in the app's sidebar with an auto-generated title, your preset, persona and model. If a session log is ever corrupted by an older version, delete <dsh home>/sessions/*/<sessionId> and it is recreated.
  • The bridge is plain HTTP on your LAN; set token if the network is not trusted, and keep allowExec/allowRelay off by default.
  • Verified end-to-end on a Xiaomi Watch 5 (M2505W1) with Android 14 talking to DSH Go on Android: watch microphone → local sensevoice ASR (0.2–0.8 s warm) → DSH session → MiMo TTS (24 kHz WAV) → watch speaker. Other watches/ABIs are untested.

License

MIT. The bundled APK is built from watch-app/ in the same project and carries the same license; see assets/SOURCE.md.

Comments

Loading…