> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/input-and-output-io-devices/quickswitch-devices/quickswitch-frequently-asked-questions.md). # QuickSwitch frequently asked questions Find answers about QuickSwitch licensing, availability, cabling, protocol, and ordering. Find answers about QuickSwitch licensing, compatibility, availability, and ordering. ### How does QuickSwitch licensing work? There is no license requirement to enable QuickSwitch hardware. It is a base feature. ### Which Command Centre version supports QuickSwitch? Supported from version 9.20 onwards. ### Does a QuickSwitch board have the same footprint? Yes, it will have the same footprint (mounting screws). ### Do I need to change wiring? No, the connectors on the original boards will be able to be left connected to the building wiring and connected to the new QuickSwitch boards as they were before. ### Do QuickSwitch boards support Wiegand or OSDP? All boards will support HBUS only at launch. OSDP or Wiegand readers can be supported with the addition of Expansion Hubs like the OSDP Hub. ### Could existing site cabling fail to support HBUS? Yes, sites using legacy systems may lack the necessary infrastructure for the QuickSwitch approach. Channel Partners must validate that existing cabling supports HBUS communication and remains usable. ### Are additional competitor boards planned? No additional boards have been confirmed. ### Which regions offer QuickSwitch? Available in all Gallagher serviced regions. ### When are QuickSwitch devices available? Now. ### Can I add boards to an existing QuickSwitch site? Yes. Order connectors separately. They are available in several pack sizes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/input-and-output-io-devices/quickswitch-devices/quickswitch-frequently-asked-questions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.