The PDK Red Hub is the PoE bridge that connects up to 16 Red Wireless Locksets to PDK.io. It sits on the network via standard Ethernet, communicates with locks over Bluetooth Low Energy at up to 100 feet, and provisions automatically the first time it reaches the cloud. No manual pairing step at each door.
How the Red Hub fits into a PDK deployment
Every Red Wireless Cylindrical Lock and Red Wireless Deadbolt requires a Red Hub to communicate with PDK.io. The hub handles translation between the wireless network at the door and the IP network at the head end. PoE-powered from the existing switch by default, with a 12-24V DC fallback for non-PoE infrastructure. The low-profile white enclosure mounts to wall or ceiling and fits behind a drop tile or in a closet. Indoor use only.
Key features
- Supports up to 16 Red Wireless Locksets per hub: one device covers a full floor, suite, or wing
- PoE-powered from the existing switch; 12-24V DC fallback on non-PoE networks
- 100-foot BLE range gives flexible hub placement relative to lock locations
- Auto-provisions on PDK.io at first connection, same cloud enrollment as the rest of the PDK estate
- Bridges BLE to Ethernet with no additional controller required
- FCC and CE compliant; NDAA Section 889 compliant per PDK
Deployment notes
Plan one Red Hub per zone. The 100-foot BLE range is line-of-sight average; concrete walls and metal doors reduce effective range. Place the hub centrally within the door cluster it serves. A single hub is sufficient for most small multifamily floors (8 to 12 units), office suites, or classroom corridors. For larger deployments, add one hub per zone of up to 16 locks.
Is a PoE switch required?
How does the hub connect to PDK.io?
Can the hub be ceiling-mounted?
How many hubs does a typical project need?
What's the real-world BLE range?
Does the hub need to be paired to each lock manually?
Is the Red Hub NDAA Section 889 compliant?
Spec Sheet