Device Access Overview
Pick how you connect (MQTT / gateway / Modbus…), then how you prove identity (one-type-one-secret / one-device-one-code). After activate, only the device MQTT account opens the long session — first-pass, remote clarity.
How you connect
| Form | What you do | Doc |
|---|---|---|
| MQTT direct | Device opens its own gmqtt session | MQTT Direct |
| MQTT gateway | Scan owned-gateway QR, attach children; debug Read/Write builds frames | MQTT Gateway |
| Modbus RTU | Same as gateway path under the owned gateway; no hand-written hex | Modbus RTU |
| Modbus / HTTP / TCP / UDP | Protocol into the same semantics | TCP · HTTP · UDP · Modbus TCP |
How you prove identity
| Mode | In one line | Doc |
|---|---|---|
| One-type-one-secret | Shared product secret → activate → per-device MQTT account | One-Type-One-Secret |
| One-device-one-code | Unique code + DeviceSecret; cleaner labeling / scanning | One-Device-One-Code |
Hard rule: ProductSecret never logs into MQTT. Layers: Architecture.