Control4
Reference documentation for Control4 DriverWorks subsystems, written from the shipping implementation rather than from published SDK docs.
Two capabilities a camera driver can opt into from its manifest: building its own control panel at runtime, and handing over stream and snapshot URLs on demand instead of declaring them once. Both are driven entirely with proxy notifications. Extras are not specific to cameras and are worth knowing wherever a driver needs controls its proxy does not define.
A project-wide agent that records what each streaming driver played, in which room, and hands that history back to Navigator so a listener can resume it in one tap. This is the command surface a driver talks to.
An opt in experience that unifies events, security and cameras into one timeline with actions attached. Nothing about it is specific to a camera brand, or to cameras at all. This is the integration path for a driver that wants to appear in it.
Every document is published as markdown alongside the page.
Agents should start at llms.txt for the index,
llms-full.txt for everything in one file, or
index.json for a machine readable manifest.