One lock.
A different key
for every door.
Bitting gives every resident their own Wi-Fi password, and a way to see it, change it, and check what is connected, without calling anyone.
It runs on the DPSK pools you already have in RUCKUS One. No Property Management, no Edge, no unit hierarchy, no migration.
Three things, then residents are self-serve
A property here is a DPSK pool plus its identity group, which is all the platform needs to be asked for.
- 1
Connect your RUCKUS tenant
An API credential scoped to DPSK, not an administrator token. It is checked against RUCKUS One before it is stored, and encrypted with a key of its own.
- 2
Register a property
Pick a pool, name it, and its units are ready. Its own rules for minimum passphrase length and notification settings are read from the platform rather than retyped.
- 3
Issue claim codes
One per unit, for a welcome letter. Shown once, stored only as a hash, and replaceable when a letter goes missing.
Have a claim code?
If your building gave you a code like K7QM9-XR42W-FH8TN, it is for the Bitting resident app, which is still being built and is not available to download yet.
Keep the letter. Your code stays valid for the period printed on it. If you need your Wi-Fi password before then, ask your property manager.
Where this is
Bitting is in development and not generally available. The operator console is live, and account creation is by invitation while it is tested against real tenants.
If you run RUCKUS One with DPSK and this sounds useful, get in touch. Early deployments are how the rough edges get found.