[{"data":1,"prerenderedAt":613},["ShallowReactive",2],{"navigation_docs_fr":3,"-fr-developer-fleet-management":181,"-fr-developer-fleet-management-surround":608},[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":91,"body":183,"description":601,"extension":602,"links":603,"meta":604,"navigation":605,"path":92,"seo":606,"stem":93,"__hash__":607},"docs_fr\u002Ffr\u002F4.developer\u002F3.fleet-management.md",{"type":184,"value":185,"toc":584},"minimark",[186,199,204,213,218,221,249,253,260,336,339,343,346,364,367,370,373,376,380,391,402,406,508,512,518,524,528,534,537,540,547,551,554,560,563,567,570,581],[187,188,189,190,194,195,198],"p",{},"Once your devices are provisioned, the ",[191,192,193],"strong",{},"manufacturer portal"," and ",[191,196,197],{},"REST API"," give you full visibility and control over your fleet.",[200,201,203],"h2",{"id":202},"manufacturer-portal","Manufacturer portal",[187,205,206,207,212],{},"The portal is available at ",[208,209,211],"a",{"href":210},"\u002Ffr\u002Fportal","support.klstr.cloud\u002Fportal",". After logging in with your manufacturer credentials, you have access to:",[214,215,217],"h3",{"id":216},"dashboard","Dashboard",[187,219,220],{},"The dashboard shows an overview of your account:",[222,223,224,231,237,243],"ul",{},[225,226,227,230],"li",{},[191,228,229],{},"Provisioned devices"," — total count and breakdown by fixture model",[225,232,233,236],{},[191,234,235],{},"Online \u002F offline"," — real-time device status",[225,238,239,242],{},[191,240,241],{},"Allowance"," — devices provisioned vs. your allocation quota",[225,244,245,248],{},[191,246,247],{},"Budget"," — spend tracking against your manufacturer budget",[214,250,252],{"id":251},"device-list","Device list",[187,254,255,256,259],{},"The ",[191,257,258],{},"Fleet > Devices"," view shows every device bound to your account:",[261,262,263,276],"table",{},[264,265,266],"thead",{},[267,268,269,273],"tr",{},[270,271,272],"th",{},"Column",[270,274,275],{},"Description",[277,278,279,288,296,304,312,320,328],"tbody",{},[267,280,281,285],{},[282,283,284],"td",{},"Device name",[282,286,287],{},"The name assigned during provisioning",[267,289,290,293],{},[282,291,292],{},"Serial number",[282,294,295],{},"Unique hardware identifier",[267,297,298,301],{},[282,299,300],{},"Fixture model",[282,302,303],{},"The registered fixture model",[267,305,306,309],{},[282,307,308],{},"Firmware",[282,310,311],{},"Currently installed firmware version",[267,313,314,317],{},[282,315,316],{},"Status",[282,318,319],{},"Online, offline, or updating",[267,321,322,325],{},[282,323,324],{},"Last seen",[282,326,327],{},"Timestamp of the last heartbeat",[267,329,330,333],{},[282,331,332],{},"IP address",[282,334,335],{},"Current network address",[187,337,338],{},"You can filter by fixture model, status, or firmware version. Click any device to view its full configuration and history.",[214,340,342],{"id":341},"firmware-management","Firmware management",[187,344,345],{},"From the portal, you can:",[222,347,348,351,358,361],{},[225,349,350],{},"View available firmware versions per device model",[225,352,353,354,357],{},"Schedule ",[191,355,356],{},"OTA firmware updates"," for individual devices or batches",[225,359,360],{},"Track update progress and rollback if needed",[225,362,363],{},"View firmware changelog and release notes",[187,365,366],{},"Note",[187,368,369],{},"OTA updates require the device to be online and connected to the internet. For air-gapped installations, use KLSTR.ctrl with a USB-C connection.",[200,371,197],{"id":372},"rest-api",[187,374,375],{},"For production automation, KLSTR. provides a REST API that covers all portal functionality programmatically.",[214,377,379],{"id":378},"authentication","Authentication",[187,381,382,383,386,387,390],{},"All API requests require a ",[191,384,385],{},"manufacturer API key",", generated in the portal under ",[191,388,389],{},"Settings > API Keys",".",[392,393,398],"pre",{"className":394,"code":396,"language":397},[395],"language-text","Authorization: Bearer \u003Cyour-api-key>\n","text",[399,400,396],"code",{"__ignoreMap":401},"",[214,403,405],{"id":404},"key-endpoints","Key endpoints",[261,407,408,420],{},[264,409,410],{},[267,411,412,415,418],{},[270,413,414],{},"Method",[270,416,417],{},"Endpoint",[270,419,275],{},[277,421,422,435,447,460,472,484,496],{},[267,423,424,427,432],{},[282,425,426],{},"GET",[282,428,429],{},[399,430,431],{},"\u002Fapi\u002Fv1\u002Fdevices",[282,433,434],{},"List all devices in your fleet",[267,436,437,439,444],{},[282,438,426],{},[282,440,441],{},[399,442,443],{},"\u002Fapi\u002Fv1\u002Fdevices\u002F:serial",[282,445,446],{},"Get a specific device by serial number",[267,448,449,452,457],{},[282,450,451],{},"POST",[282,453,454],{},[399,455,456],{},"\u002Fapi\u002Fv1\u002Fdevices\u002Fclaim",[282,458,459],{},"Claim a new device",[267,461,462,465,469],{},[282,463,464],{},"PATCH",[282,466,467],{},[399,468,443],{},[282,470,471],{},"Update device configuration",[267,473,474,476,481],{},[282,475,426],{},[282,477,478],{},[399,479,480],{},"\u002Fapi\u002Fv1\u002Fallocation",[282,482,483],{},"View current allocation and budget",[267,485,486,488,493],{},[282,487,451],{},[282,489,490],{},[399,491,492],{},"\u002Fapi\u002Fv1\u002Ffirmware\u002Fdeploy",[282,494,495],{},"Schedule firmware update for a device or batch",[267,497,498,500,505],{},[282,499,426],{},[282,501,502],{},[399,503,504],{},"\u002Fapi\u002Fv1\u002Ffirmware\u002Fversions",[282,506,507],{},"List available firmware versions",[214,509,511],{"id":510},"example-list-devices","Example: List devices",[392,513,516],{"className":514,"code":515,"language":397},[395],"curl -H \"Authorization: Bearer $API_KEY\" \\  https:\u002F\u002Fapi.klstr.cloud\u002Fapi\u002Fv1\u002Fdevices\n",[399,517,515],{"__ignoreMap":401},[392,519,522],{"className":520,"code":521,"language":397},[395],"{  \"devices\": [    {      \"serial\": \"KN2-00A1B2C3\",      \"name\": \"venue-a-truss-1\",      \"model\": \"WashPro 500\",      \"firmware\": \"2.1.0\",      \"status\": \"online\",      \"last_seen\": \"2026-04-24T12:30:00Z\",      \"ip\": \"192.168.1.42\"    }  ],  \"total\": 142,  \"quota\": 500}\n",[399,523,521],{"__ignoreMap":401},[214,525,527],{"id":526},"example-bulk-firmware-update","Example: Bulk firmware update",[392,529,532],{"className":530,"code":531,"language":397},[395],"curl -X POST \\  -H \"Authorization: Bearer $API_KEY\" \\  -H \"Content-Type: application\u002Fjson\" \\  -d '{    \"firmware_version\": \"2.1.1\",    \"filter\": { \"model\": \"WashPro 500\", \"firmware_lt\": \"2.1.1\" }  }' \\  https:\u002F\u002Fapi.klstr.cloud\u002Fapi\u002Fv1\u002Ffirmware\u002Fdeploy\n",[399,533,531],{"__ignoreMap":401},[187,535,536],{},"This schedules an OTA update for all WashPro 500 devices running firmware older than 2.1.1.",[187,538,539],{},"Caution",[187,541,542,543,546],{},"The API is rate-limited to ",[191,544,545],{},"100 requests per minute"," per API key. For bulk operations, use the batch endpoints rather than iterating over individual devices.",[200,548,550],{"id":549},"bulk-provisioning-api","Bulk provisioning API",[187,552,553],{},"For production lines, the claim endpoint supports batch operations:",[392,555,558],{"className":556,"code":557,"language":397},[395],"curl -X POST \\  -H \"Authorization: Bearer $API_KEY\" \\  -H \"Content-Type: application\u002Fjson\" \\  -d '{    \"serials\": [\"KN2-00A1B2C3\", \"KN2-00A1B2C4\", \"KN2-00A1B2C5\"],    \"model\": \"WashPro 500\",    \"firmware\": \"2.1.0\"  }' \\  https:\u002F\u002Fapi.klstr.cloud\u002Fapi\u002Fv1\u002Fdevices\u002Fclaim\n",[399,559,557],{"__ignoreMap":401},[187,561,562],{},"This claims multiple devices, assigns them to a fixture model, and schedules firmware installation — all in a single request.",[200,564,566],{"id":565},"webhooks-coming-soon","Webhooks (coming soon)",[187,568,569],{},"KLSTR. is developing webhook support for real-time event notifications:",[222,571,572,575,578],{},[225,573,574],{},"Device comes online \u002F goes offline",[225,576,577],{},"Firmware update completed \u002F failed",[225,579,580],{},"Allocation threshold reached",[187,582,583],{},"Contact your account manager to join the webhook beta program.",{"title":401,"searchDepth":585,"depth":585,"links":586},2,[587,593,599,600],{"id":202,"depth":585,"text":203,"children":588},[589,591,592],{"id":216,"depth":590,"text":217},3,{"id":251,"depth":590,"text":252},{"id":341,"depth":590,"text":342},{"id":372,"depth":585,"text":197,"children":594},[595,596,597,598],{"id":378,"depth":590,"text":379},{"id":404,"depth":590,"text":405},{"id":510,"depth":590,"text":511},{"id":526,"depth":590,"text":527},{"id":549,"depth":585,"text":550},{"id":565,"depth":585,"text":566},"Managing your KLSTR. device fleet — manufacturer portal, device monitoring, budget tracking, and REST API for automation.","md",null,{},true,{"title":91,"description":601},"mQAyFYSSX_32trRCCxfX1IisBnkO5cTYH6GvEH_yu0w",[609,611],{"title":87,"path":88,"stem":89,"description":610,"children":-1},"How to use KLSTR.nano and KLSTR.one together — wiring, configuration, and communication between the two modules.",{"title":99,"path":100,"stem":101,"description":612,"children":-1},"Complete hardware integration reference for the KLSTR.one Module v1.x — Ethernet, bypass relays, power supply architecture, pinout, electrical parameters, and mechanical dimensions.",1781710617623]