Issue link: https://read.uberflip.com/i/1545681
LoRaWAN ® Device Identification QR Codes for Automated Onboarding Specification TS018- 1.0.0 ©2026 LoRa Alliance ® Page 8 of 17 The authors reserve the right to change specifications without notice. Note: As 48 characters are consumed by the mandatory information, 80 191 characters remain for the optional extensions. 192 4.2.1 SchemaID 193 194 The SchemaID is used to indicate the schema that should be applied to the remaining data of 195 the identifier. The SchemaID consists of two characters and is currently defined in the Table 196 2. 197 198 199 Schema ID Description D0 Device Schema Version 0 – the schema described in this document Table 2: Schema IDs 200 201 4.2.2 JoinEUI 202 203 JoinEUI [TS001], formerly AppEUI, is the initial JoinEUI value used by the device after 204 shipment (in case the device uses multiple JoinEUIs) that uniquely identifies the JS [TS002]. 205 206 The JoinEUI value SHALL use a hexadecimal representation resulting in 16 characters. 207 4.2.3 DevEUI 208 209 The DevEUI [TS001] value SHALL use a hexadecimal representation resulting in 16 210 characters. 211 4.2.4 ProfileID 212 213 The ProfileID encodes a VendorID and VendorProfileID as defined in Table 3. They SHALL 214 use a hexadecimal representation resulting in 8 characters. 215 216 ProfileID VendorID VendorProfileID Size (Bytes) 2 2 217 Table 3: ProfileID 218 219 VendorID is assigned by the LoRa Alliance [VID]. The VendorID, 0xFFFF, is to be utilized prior 220 to commercial production of a device. 221 222 VendorProfileID is assigned by the device manufacturer for commercial products. Because 223 the ProfileID may be used as an index on a Device Profile database or payload decoding 224 database, the manufacturer SHALL use a distinct VendorProfileID for devices with different 225 Device Profiles [TS014] or payload encodings. 226