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