[{"data":1,"prerenderedAt":456},["ShallowReactive",2],{"navigation_docs_fr":3,"-fr-articles-klstr-one-provisioning":181,"-fr-articles-klstr-one-provisioning-surround":451},[4,22,40,54,72,126,144],{"title":5,"icon":6,"path":7,"stem":8,"children":9,"page":21},"Getting Started","i-lucide-rocket","\u002Ffr\u002Ftutorials","fr\u002F1.tutorials",[10,13,17],{"title":5,"path":11,"stem":12},"\u002Ffr\u002Ftutorials\u002Fgetting-started","fr\u002F1.tutorials\u002F1.getting-started",{"title":14,"path":15,"stem":16},"Setup KLSTR.one","\u002Ffr\u002Ftutorials\u002Fsetup-klstr-one","fr\u002F1.tutorials\u002F2.setup-klstr-one",{"title":18,"path":19,"stem":20},"Setup KLSTR.nano","\u002Ffr\u002Ftutorials\u002Fsetup-klstr-nano","fr\u002F1.tutorials\u002F3.setup-klstr-nano",false,{"title":23,"icon":24,"path":25,"stem":26,"children":27,"page":21},"KLSTR.one","i-lucide-cpu","\u002Ffr\u002Fklstr-one","fr\u002F2.klstr-one",[28,32,36],{"title":29,"path":30,"stem":31},"KLSTR.one Overview","\u002Ffr\u002Fklstr-one\u002Foverview","fr\u002F2.klstr-one\u002F1.overview",{"title":33,"path":34,"stem":35},"KLSTR.one Installation","\u002Ffr\u002Fklstr-one\u002Finstallation","fr\u002F2.klstr-one\u002F2.installation",{"title":37,"path":38,"stem":39},"KLSTR.one Specifications","\u002Ffr\u002Fklstr-one\u002Fspecifications","fr\u002F2.klstr-one\u002F3.specifications",{"title":41,"icon":42,"path":43,"stem":44,"children":45,"page":21},"Admin","i-lucide-shield-check","\u002Ffr\u002Fadmin","fr\u002F3.admin",[46,50],{"title":47,"path":48,"stem":49},"Admin Dashboard","\u002Ffr\u002Fadmin\u002Fdashboard","fr\u002F3.admin\u002F1.dashboard",{"title":51,"path":52,"stem":53},"Internal Release Notes","\u002Ffr\u002Fadmin\u002Frelease-notes","fr\u002F3.admin\u002F2.release-notes",{"title":55,"icon":56,"path":57,"stem":58,"children":59,"page":21},"KLSTR.nano","i-lucide-microchip","\u002Ffr\u002Fklstr-nano","fr\u002F3.klstr-nano",[60,64,68],{"title":61,"path":62,"stem":63},"KLSTR.nano Overview","\u002Ffr\u002Fklstr-nano\u002Foverview","fr\u002F3.klstr-nano\u002F1.overview",{"title":65,"path":66,"stem":67},"KLSTR.nano Installation","\u002Ffr\u002Fklstr-nano\u002Finstallation","fr\u002F3.klstr-nano\u002F2.installation",{"title":69,"path":70,"stem":71},"KLSTR.nano Specifications","\u002Ffr\u002Fklstr-nano\u002Fspecifications","fr\u002F3.klstr-nano\u002F3.specifications",{"title":73,"icon":74,"path":75,"stem":76,"children":77,"page":21},"Developer Guide","i-lucide-code","\u002Ffr\u002Fdeveloper","fr\u002F4.developer",[78,82,86,90,94,114],{"title":79,"path":80,"stem":81},"Overview","\u002Ffr\u002Fdeveloper\u002Foverview","fr\u002F4.developer\u002F0.overview",{"title":83,"path":84,"stem":85},"Choosing a Module","\u002Ffr\u002Fdeveloper\u002Fchoosing-a-module","fr\u002F4.developer\u002F1.choosing-a-module",{"title":87,"path":88,"stem":89},"Dual-Mode Operation","\u002Ffr\u002Fdeveloper\u002Fdual-mode","fr\u002F4.developer\u002F2.dual-mode",{"title":91,"path":92,"stem":93},"Fleet Management","\u002Ffr\u002Fdeveloper\u002Ffleet-management","fr\u002F4.developer\u002F3.fleet-management",{"title":23,"path":95,"stem":96,"children":97,"page":21},"\u002Ffr\u002Fdeveloper\u002Fklstr-one","fr\u002F4.developer\u002F4.klstr-one",[98,102,106,110],{"title":99,"path":100,"stem":101},"KLSTR.one: Hardware Integration","\u002Ffr\u002Fdeveloper\u002Fklstr-one\u002Fhardware-integration","fr\u002F4.developer\u002F4.klstr-one\u002F1.hardware-integration",{"title":103,"path":104,"stem":105},"KLSTR.one: Provisioning","\u002Ffr\u002Fdeveloper\u002Fklstr-one\u002Fprovisioning","fr\u002F4.developer\u002F4.klstr-one\u002F2.provisioning",{"title":107,"path":108,"stem":109},"KLSTR.one: RDM Protocol","\u002Ffr\u002Fdeveloper\u002Fklstr-one\u002Frdm-protocol","fr\u002F4.developer\u002F4.klstr-one\u002F3.rdm-protocol",{"title":111,"path":112,"stem":113},"Internal (Partner Only)","\u002Ffr\u002Fdeveloper\u002Fklstr-one\u002Finternal","fr\u002F4.developer\u002F4.klstr-one\u002F4.internal",{"title":55,"path":115,"stem":116,"children":117,"page":21},"\u002Ffr\u002Fdeveloper\u002Fklstr-nano","fr\u002F4.developer\u002F5.klstr-nano",[118,122],{"title":119,"path":120,"stem":121},"KLSTR.nano: Hardware Integration","\u002Ffr\u002Fdeveloper\u002Fklstr-nano\u002Fhardware-integration","fr\u002F4.developer\u002F5.klstr-nano\u002F1.hardware-integration",{"title":123,"path":124,"stem":125},"KLSTR.nano: Provisioning","\u002Ffr\u002Fdeveloper\u002Fklstr-nano\u002Fprovisioning","fr\u002F4.developer\u002F5.klstr-nano\u002F2.provisioning",{"title":127,"icon":128,"path":129,"stem":130,"children":131,"page":21},"FAQ","i-lucide-circle-help","\u002Ffr\u002Ffaq","fr\u002F5.faq",[132,136,140],{"title":133,"path":134,"stem":135},"General Questions","\u002Ffr\u002Ffaq\u002Fgeneral","fr\u002F5.faq\u002F1.general",{"title":137,"path":138,"stem":139},"Connectivity","\u002Ffr\u002Ffaq\u002Fconnectivity","fr\u002F5.faq\u002F2.connectivity",{"title":141,"path":142,"stem":143},"Troubleshooting","\u002Ffr\u002Ffaq\u002Ftroubleshooting","fr\u002F5.faq\u002F3.troubleshooting",{"title":145,"icon":146,"path":147,"stem":148,"children":149,"page":21},"Articles","i-lucide-newspaper","\u002Ffr\u002Farticles","fr\u002F6.articles",[150,153,157,161,165,169,173,177],{"title":79,"path":151,"stem":152},"\u002Ffr\u002Farticles\u002Foverview","fr\u002F6.articles\u002F0.overview",{"title":154,"path":155,"stem":156},"KLSTR Integration Guide for Fixture Manufacturers","\u002Ffr\u002Farticles\u002Fintegration-guide","fr\u002F6.articles\u002F1.integration-guide",{"title":158,"path":159,"stem":160},"RDM Protocol Reference for KLSTR.one","\u002Ffr\u002Farticles\u002Frdm-protocol","fr\u002F6.articles\u002F2.rdm-protocol",{"title":162,"path":163,"stem":164},"KLSTR.one Provisioning Guide","\u002Ffr\u002Farticles\u002Fklstr-one-provisioning","fr\u002F6.articles\u002F3.klstr-one-provisioning",{"title":166,"path":167,"stem":168},"KLSTR.one Integration Guide","\u002Ffr\u002Farticles\u002Fklstr-one-plug-in-integration","fr\u002F6.articles\u002F4.klstr-one-plug-in-integration",{"title":170,"path":171,"stem":172},"KLSTR.nano Provisioning Guide","\u002Ffr\u002Farticles\u002Fklstr-nano-provisioning","fr\u002F6.articles\u002F5.klstr-nano-provisioning",{"title":174,"path":175,"stem":176},"KLSTR.nano Plug-In Integration","\u002Ffr\u002Farticles\u002Fklstr-nano-plug-in-integration","fr\u002F6.articles\u002F6.klstr-nano-plug-in-integration",{"title":178,"path":179,"stem":180},"Hello","\u002Ffr\u002Farticles\u002Fhello","fr\u002F6.articles\u002F7.hello",{"id":182,"title":162,"body":183,"description":444,"extension":445,"links":446,"meta":447,"navigation":448,"path":163,"seo":449,"stem":164,"__hash__":450},"docs_fr\u002Ffr\u002F6.articles\u002F3.klstr-one-provisioning.md",{"type":184,"value":185,"toc":429},"minimark",[186,190,194,197,202,218,222,227,239,243,266,270,273,299,303,324,328,335,346,350,353,364,370,373],[187,188,189],"p",{},"By KLSTR Engineering · 2026-04-10 KLSTR.one Provisioning manufacturer firmware",[191,192,162],"h1",{"id":193},"klstrone-provisioning-guide",[187,195,196],{},"This guide covers the provisioning workflow for KLSTR.one devices as a fixture manufacturer or system integrator.",[198,199,201],"h2",{"id":200},"prerequisites","Prerequisites",[203,204,205,209,212,215],"ul",{},[206,207,208],"li",{},"Active manufacturer account on the KLSTR. portal",[206,210,211],{},"KLSTR.ctrl software installed (latest version)",[206,213,214],{},"Ethernet connection to KLSTR.one",[206,216,217],{},"Device allocation available in your manufacturer budget",[198,219,221],{"id":220},"provisioning-workflow","Provisioning Workflow",[223,224,226],"h3",{"id":225},"_1-physical-setup","1. Physical setup",[228,229,230,233,236],"ol",{},[206,231,232],{},"Connect the KLSTR.one to your network via Ethernet.",[206,234,235],{},"Power the device using the supplied 12–48 V DC adapter or PoE.",[206,237,238],{},"Wait for the status LED to show a slow blue pulse (network ready, no configuration).",[223,240,242],{"id":241},"_2-discover-and-claim-the-device","2. Discover and claim the device",[228,244,245,248,256,263],{},[206,246,247],{},"Open KLSTR.ctrl on a computer connected to the same network.",[206,249,250,251,255],{},"The KLSTR.one should appear in the ",[252,253,254],"strong",{},"Device Discovery"," panel within 5 seconds.",[206,257,258,259,262],{},"Click the device and select ",[252,260,261],{},"Claim Device",".",[206,264,265],{},"Enter your manufacturer credentials to bind the device to your account.",[223,267,269],{"id":268},"_3-configure-the-device","3. Configure the device",[187,271,272],{},"After claiming, configure the device for your use case:",[228,274,275,281,287,293],{},[206,276,277,280],{},[252,278,279],{},"Device Name"," — assign a meaningful name for fleet management.",[206,282,283,286],{},[252,284,285],{},"DMX Universe"," — assign the Art-Net \u002F sACN universe.",[206,288,289,292],{},[252,290,291],{},"Operating Mode"," — select standalone, bridge, or redundant mode.",[206,294,295,298],{},[252,296,297],{},"Fixture Model"," — select the registered fixture model from your portfolio.",[223,300,302],{"id":301},"_4-update-firmware","4. Update firmware",[228,304,305,312,318,321],{},[206,306,307,308,311],{},"In KLSTR.ctrl, go to the device's ",[252,309,310],{},"Firmware"," tab.",[206,313,314,315,262],{},"If an update is available, click ",[252,316,317],{},"Update Firmware",[206,319,320],{},"The device will reboot automatically after the update (~60 seconds).",[206,322,323],{},"Verify the new firmware version in the device info panel.",[223,325,327],{"id":326},"_5-register-in-fleet","5. Register in fleet",[187,329,330,331,334],{},"Once provisioned, the device is automatically visible in the manufacturer portal under ",[252,332,333],{},"Fleet > Devices",". Verify:",[203,336,337,340,343],{},[206,338,339],{},"Device serial number and firmware version",[206,341,342],{},"Assigned fixture model",[206,344,345],{},"Network status (online\u002Foffline)",[198,347,349],{"id":348},"production-line-integration","Production Line Integration",[187,351,352],{},"For high-volume manufacturing, KLSTR. provides a REST API for automated provisioning. The API supports:",[203,354,355,358,361],{},[206,356,357],{},"Bulk device claiming",[206,359,360],{},"Automated firmware deployment",[206,362,363],{},"License assignment via serial number batch upload",[187,365,366,367,262],{},"API documentation is available in the manufacturer portal under ",[252,368,369],{},"Developer > API Reference",[198,371,141],{"id":372},"troubleshooting",[374,375,376,392],"table",{},[377,378,379],"thead",{},[380,381,382,386,389],"tr",{},[383,384,385],"th",{},"Symptom",[383,387,388],{},"Cause",[383,390,391],{},"Solution",[393,394,395,407,418],"tbody",{},[380,396,397,401,404],{},[398,399,400],"td",{},"Device not discovered",[398,402,403],{},"Network misconfiguration",[398,405,406],{},"Ensure KLSTR.one and KLSTR.ctrl are on the same subnet; check firewall rules for mDNS",[380,408,409,412,415],{},[398,410,411],{},"Claim fails",[398,413,414],{},"Allocation exhausted",[398,416,417],{},"Request additional device allocation in the manufacturer portal",[380,419,420,423,426],{},[398,421,422],{},"Firmware update stuck",[398,424,425],{},"Power interruption",[398,427,428],{},"Do not power cycle during update; if stuck > 5 min, contact support",{"title":430,"searchDepth":431,"depth":431,"links":432},"",2,[433,434,442,443],{"id":200,"depth":431,"text":201},{"id":220,"depth":431,"text":221,"children":435},[436,438,439,440,441],{"id":225,"depth":437,"text":226},3,{"id":241,"depth":437,"text":242},{"id":268,"depth":437,"text":269},{"id":301,"depth":437,"text":302},{"id":326,"depth":437,"text":327},{"id":348,"depth":431,"text":349},{"id":372,"depth":431,"text":141},"How to provision KLSTR.one devices — activation, network setup, firmware updates, and fleet registration.","md",null,{},true,{"title":162,"description":444},"PLAilGfO1Bcv9aGLL0VhZYhGqLqfx1Y2x68m6Nhf7pQ",[452,454],{"title":158,"path":159,"stem":160,"description":453,"children":-1},"Technical reference for RDM (E1.20) support in KLSTR.one devices",{"title":166,"path":167,"stem":168,"description":455,"children":-1},"Hardware and network integration guide for the KLSTR.one device — Ethernet, DMX, Art-Net\u002FsACN configuration, and dual-mode operation with KLSTR.nano.",1781710619685]