Wireless Security

advanced

Overview

The WVC wireless mesh uses 128-bit symmetric-key encryption with automatic key rotation to secure all communication between the base station and every paired device, including the knob and displays such as the WDD-LITE, BassWatch, and RTC. This article explains how the security model works and why the system is not susceptible to interception or signal hijacking by consumer RF devices.


How the Encrypted Mesh Works

First-Time Pairing

When a knob connects to a base station for the first time, the two devices establish a secure session. Until that session is negotiated, which requires firmware 3.0.0 or newer on both the knob and the base station, the link runs on a shared default key. Once negotiation succeeds, the pair switches to a uniquely derived 128-bit key set used only for that one link, and no other device in the mesh holds it.

From the point session keys are in place onward, every data packet (whether sent from the knob to the base station or vice versa) is fully encrypted using those keys. A new knob or unit added to the mesh later goes through the same pairing flow and is issued its own unique session keys.

Automatic Key Rotation

The base station periodically replaces the session keys with newly derived ones during normal operation. Rotation happens automatically in the background while you use the system. You never need to trigger it, approve it, or even know it happened.

Refresh pacing (base station firmware 4.8.2 and later): each paired device is refreshed at most once per hour. Earlier firmware paced the refresh purely by how much traffic a link was carrying, so a display sitting on a live analysis view could be refreshed every few minutes. Spacing the refreshes out keeps exactly the same protection while giving the link far fewer opportunities to be interrupted part-way through a key handover. A refresh that is held back because the hour has not yet elapsed is not skipped permanently; it simply runs at the next check once the window has passed.

Both devices confirm they have received the new keys before switching to them, and from firmware 4.8.2 the base station repeats that final confirmation so a single dropped message cannot leave the two ends holding different keys. The old keys are then discarded.

In effect, the encryption keys protecting your link are refreshed repeatedly throughout normal use. Even an attacker who managed to capture a single packet's encryption material would find that material useless once the link moved on to its next key set.

Mesh Security

When a secondary WVC unit or an additional knob is added to the mesh, it goes through its own first-time pairing with the primary unit. That pair gets its own independent session keys, subject to the same rotation. Each device pair in the mesh has its own unique encryption keys that are continuously recycled, so capturing traffic on one link reveals nothing about any other link.


Why Signal Interception Is Not Practical

For an attacker to take control of the system, they would need to:

  1. Capture the encrypted wireless packets being transmitted.
  2. Recover the 128-bit session key in real time.
  3. Reverse-engineer the proprietary wireless protocol used over the link.
  4. Spoof the knob's network identity and replicate its encrypted packet structure correctly.
  5. Complete all of the above before the next key rotation invalidates whatever they captured.

No consumer RF device, including tools such as the Flipper Zero, has the computational capability to accomplish this. Recovering a 128-bit symmetric key in real time is well beyond the reach of consumer or hobbyist hardware. The repeated key rotation adds a second layer of protection: even a theoretical key recovery would have a limited useful life before the link rotates onto a new key.


On base station firmware earlier than 4.8.2, a paired knob or display could occasionally lose its link during one of these background key refreshes and stay on "Reconnecting" from then on. The state survived a restart, and the only way back was Forget Base on the paired device followed by a fresh pairing.

Firmware 4.8.2 fixes that at the source: the refresh is paced to at most once per hour per device and the closing confirmation is repeated, so a single lost message no longer strands the pair. Update the base station, and update the paired device as well so both ends carry the fix (WDD-LITE 4.9.1 or later, BassWatch 4.8.1 or later). If a device is already stuck, forget the base and pair it once more after updating; it should not recur.

Note

Only encrypted pairings are affected, which on the WVC family means every pairing. See Troubleshooting for the full symptom list.


Verifying Encrypted Comms on Your Unit

You can confirm that encrypted communications are active on the wireless knob at any time:

  1. Long-press the encoder on the knob to open the menu.
  2. Navigate to Knob Info.
  3. Confirm Encrypted Comms is shown as Yes.

The status is also visible on the RTC remote's System Info screen (under the Encrypted row). The WVC base station itself has no built-in screen, so the diagnostic is read from the knob or RTC remote rather than from the base. The LF Audio AuralSync app does not currently surface the encryption-comms status separately.