#Openclaw node for android

1 messages · Page 1 of 1 (latest)

rustic ore
#

Getting a mismatch when is the next app update

serene etherBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

past widgetBOT
# rustic ore Getting a mismatch when is the next app update

I don’t have a release ETA for the Android app. The docs still say the Android app is not publicly released yet; current path is building it from source under apps/android: https://docs.openclaw.ai/platforms/android

For the mismatch: first thing I need is your gateway version:

openclaw --version

Also send the exact mismatch text from the Android app/logs. If it’s a protocol/version mismatch, the usual fix is to update/rebuild the Android app and gateway from the same OpenClaw revision, then re-pair if needed.

rustic ore
#

Help diagnose this OpenClaw Android gateway connection failure.

Please:

  • pick one route only: same machine, same LAN, Tailscale, or public URL
  • classify this as pairing/auth, TLS trust, wrong advertised route, wrong address/port, or gateway down
  • remember: Tailscale/public mobile routes require wss:// or Tailscale Serve; private LAN ws:// is still allowed
  • quote the exact app status/error below
  • tell me whether openclaw devices list should show a pending pairing request
  • if more signal is needed, ask for openclaw qr --json, openclaw devices list, and openclaw nodes status
  • give the next exact command or tap

Debug info:

past widgetBOT
# rustic ore Help diagnose this OpenClaw Android gateway connection failure. Please: - pick ...

Route: Tailscale via https://daniels-macbook-air.tailf6342d.ts.net.

Exact app status/error: Gateway error: protocol mismatch

Classification: pairing/auth handshake, specifically a client/gateway protocol version mismatch. It is not TLS trust, not wrong address/port, and not gateway down, because the Android app reached something OpenClaw enough to get a protocol rejection. The Tailscale/public route requirement is satisfied only if that URL is coming through Tailscale Serve/Funnel or another real wss:///HTTPS TLS endpoint.

openclaw devices list: I would not expect a pending pairing request from this attempt. Protocol mismatch happens before normal node pairing can complete/create the request.

Next command on the gateway Mac:

openclaw --version

If that doesn’t match the Android app era/version, update/rebuild the gateway and Android app from the same OpenClaw revision, then try the onboarding final check again.

If you want me to pin it down from logs/state, send: