Lytbit Lab: the interoperability bench

Why a controls company needs a bench

“Compatible” on a datasheet usually means two devices share a protocol. It doesn’t tell you whether a sensor’s hold time and a driver’s fade rate add up to a pause that annoys people, whether a gateway drops points under load, or whether a firmware update on one side quietly breaks the other. Those are the problems that create callbacks, and almost none of them show up until the system is in a ceiling.

So we test the combination before it gets there. Our rule on projects is the same one we apply to commissioning: test everything, even the parts that “just work”. The bench simply moves that rule upstream, to a place where a failure costs an afternoon instead of a lift rental and a second site visit.

Bench Notes

Every test produces a Bench Note. Each one follows the same structure:

1. The question, in one sentence.
2. The setup: device categories, protocols, firmware versions, wiring, and network configuration.
3. The procedure: what we triggered, measured, and logged.
4. The results, with the data attached.
5. What we’d do: our recommendation, and the conditions under which it would change.
6. Open issues: what we couldn’t resolve, and who we’ve asked.

Project Bench Notes go to the client as part of the approach. Notes on general questions are published on our blog under the Lytbit Lab byline, so engineers and owners who never hire us can still use them.

What the lab is not

The Lab is not a certification body. A Bench Note doesn’t replace a DLC listing, DALI-2 certification, or a BACnet Testing Laboratories listing; it answers the narrower, more practical question of whether specific devices work together in a specific sequence.

It’s also not a showroom. Nothing is on the bench because someone paid to put it there, and no manufacturer can buy a favorable write-up. That independence is the reason the bench exists.

Starting a conversation with the lab

Use the form on this page or write to lab@lytbit.com. The most useful first message includes the devices involved and their firmware versions, the question you need answered, your deadline, and whether the results can be published. A person replies within one business day. If you can, include photos of the device labels; firmware and hardware revisions are often printed there.

For protocol background before you write, see our integrations directory, our guidance on PoE lighting, and our IoT hardware integration service.