Complete reverse-engineering of the DWARFLAB Android app (v3.4.0) protocol
and implementation of a working CLI tool to control DWARF II telescopes.
Analysis (from APK decompilation with jadx):
- Extracted 17 protobuf definitions (382 messages) from embedded descriptors
- Mapped all 323 WebSocket command IDs across 16 modules
- Documented the full protocol: BLE discovery, WebSocket control (port 9900),
RTSP preview, WsPacket envelope (proto v2.3)
- Documented the Android UI structure (screens, navigation, shooting modes)
- Key discovery: telescope responds with type=3 (reply), not type=1 (response),
and several commands are fire-and-forget (RGB, camera open/close)
dwarfctl Go client:
- Protobuf bindings generated from extracted .proto files (397 messages)
- WebSocket transport layer with request-response matching and notification fan-out
- Typed API covering cameras, motors, astrophotography, focus, tracking, system, power
- Cobra CLI with 30+ subcommands and --debug traffic logging
- 57 unit tests (transport round-trip, command routing, proto encoding)
- Validated on real hardware: state, photo, motor slew (all directions/speeds),
focus, RGB, time/location sync all confirmed working
💘 Generated with Crush
Assisted-by: Crush:glm-5.2
41 lines
528 B
Protocol Buffer
41 lines
528 B
Protocol Buffer
syntax = "proto3";
|
|
option go_package = "github.com/antitbone/dwarfctl/proto;pb";
|
|
message ReqStartTrack {
|
|
int32 x = 1;
|
|
int32 y = 2;
|
|
int32 w = 3;
|
|
int32 h = 4;
|
|
int32 cam_id = 5;
|
|
}
|
|
|
|
message ReqStopTrack {
|
|
}
|
|
|
|
message ReqPauseTrack {
|
|
}
|
|
|
|
message ReqContinueTrack {
|
|
}
|
|
|
|
message ReqStartSentryMode {
|
|
int32 type = 1;
|
|
}
|
|
|
|
message ReqStopSentryMode {
|
|
}
|
|
|
|
message ReqMOTTrackOne {
|
|
int32 id = 1;
|
|
}
|
|
|
|
message ReqUFOAutoHandMode {
|
|
int32 mode = 1;
|
|
}
|
|
|
|
message ReqStartTrackClick {
|
|
int32 x = 1;
|
|
int32 y = 2;
|
|
int32 cam_id = 3;
|
|
}
|
|
|