01 / What We Need (Anonymized IDs Welcome)
24 hours of uplink JSON, zero radio keys
Share 24 continuous hours of JSON uplinks from 1 to 50+ endpoints (a 2-to-6-hour lab bench capture is also welcome). Hashed or masked 64-bit endpoint EUIs (epEui / EUI) and base-station EUIs (bsEui / gweui) work cleanly as long as each endpoint keeps a consistent pseudonym across the window. Never include NWKKEY, APPSKEY, or personal data.
02 / Accepted Drop-In Capture Formats
Fraunhofer ACMQTTI or native SC / AC JSON
Drop any of these directly into a .jsonl, .json, or .gz export with zero reformatting: (a) Fraunhofer IIS ACMQTTI MQTT dumps on mioty/<app>/<epEui>/uplink carrying baseStations, cnt, data, format, typeEui, and components; or (b) native Service Center (SC) and Application Center (AC) JSON exports from WEPTECH AVA, Swissphone, LZE, or BehrTech stacks.
mosquitto_sub -h <sc-broker-host> -p 8883 -u <user> -P <pass> \
-t 'mioty/+/+/uplink' -F '{"topic":"%t","payload":%p}' > mioty_24h_capture.jsonl
Current Conformance Disclosure: The mioty (/v1/ingest/mioty) Stage 1 to 4 suite (typeEui Blueprint bit-offset re-decode, Class Z ulAttach/ulDetach and BSSCI drop sealing, eta_mioty_v1 multi-base-station clock consensus, optional MS\x01 binary Ed25519 frames, and submetering-dispute preset) is schema-verified against ETSI TS 103 357-2 and Fraunhofer ACMQTTI mioty output schemas, with physical mioty hardware capture validation pending. Operator 24-hour capture packs are replayed in an isolated single-tenant sandbox (retention_policy: "sandbox").