Add reverse-engineered WiFi/UART/cloud protocol documentation - #7
Open
Sebbeben wants to merge 4 commits into
Open
Add reverse-engineered WiFi/UART/cloud protocol documentation#7Sebbeben wants to merge 4 commits into
Sebbeben wants to merge 4 commits into
Conversation
protocol/: the dongle's WiFi LAN control protocol (TCP/UDP 51515, @h* command set + * machine passthrough), the JURA UART protocol (9600 8N1, 0x5B codec, V1/V2), and the JURA cloud architecture. Plus REFERENCES.md and a README section. Clearly labeled reverse-engineered & not yet hardware-verified; no proprietary binaries included.
…ormant Adds protocol/firmware-images.md and updates cloud-architecture.md + README to reflect that the booted firmware has no ESP-AT/cloud client; the ESP-AT cloud image present in flash is never booted.
- wifi-local-protocol.md: mark VERIFIED on hardware (real @HP/@HY/@HI/@hl replies), fix SoftAP (WiFiFrog_<MAC>, open, 192.168.24.1), replace the wrong *-codec formula with the solved shuffle + TT237W S-box tables (same algorithm as JURA Bluetooth, Jutta-Proto/protocol-bt-cpp ByteEncDecoder). - src/wifi/ByteEncDecoder.{hpp,cpp,_test.cpp}: C++ reference codec + self-test (involution + decodes real captured frames to exact ASCII; g++ -Wall -Wextra clean). - README: status -> WiFi LAN protocol hardware-verified; codec reference added. - add .gitignore (shield the private firmware dump / .claude from this public fork).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
Reverse-engineered documentation of the JURA WiFi Connect (TT237W) dongle's protocols, under a new
protocol/folder:line-based
@H…command set (@HI/@HL/@HY/@HW/@HR/@HT/@HP/@HU/@HB/@HO/@HD/@HE), with the actualmachine commands tunnelled over a
*-prefixed keyed-nibble channel. This means the stock dongle canbe controlled locally over the LAN, with no cloud. Onboarding SoftAP SSID is
CoffeeMachine_<id>.@T1/@T2/@T3handshake, and the older V1 command vocabulary (HZ:/RE:/WE:/…). Largely yourprior work, summarised for context with full credit.
keycloak.pocketpilot.jura.com, realmJura),joeapi.jura.com,and the pocketpilot backend, observed from the J.O.E. app; plus the finding that the firmware's
+CIPUPDATE/download_rompath is stock ESP-AT example code pointing atiot.espressif.cnwith noTLS cert verification.
How it was derived
Static analysis (Ghidra/Xtensa) of a dongle's firmware dump and decompilation of the J.O.E. Android app.
Notes
J.O.E. APK) are included.
(see
REFERENCES.md).untouched.