PJLink displays
Projector and display status.
Reviewed capabilities
Section titled “Reviewed capabilities”- Read AV equipment and room health (live). Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. PJLink Class 1 queries only: power state, lamp hours, input, identity and reported hardware errors. Standby is not an outage.
- Read network equipment (live). Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. PJLink Class 1 queries only: power state, lamp hours, input, identity and reported hardware errors. Standby is not an outage.
- Read network sites (live). Enable network monitoring and configure the connector in the existing integration settings. A site connector agent or an explicitly authorized local deployment with access to the AV management network. Read-only monitoring. Offline, unsupported, stale and unknown observations remain distinct. Live hardware/account pilot validation is still required. Up to 64 explicitly configured endpoints with shared protocol credentials and port. Each endpoint can be mapped to a campus; one site agent binding per connector. PJLink Class 1 queries only: power state, lamp hours, input, identity and reported hardware errors. Standby is not an outage.
Requirements
Section titled “Requirements”- An enabled connector, a compatible vendor service and appropriate Plugboard permissions. Live handlers require real configuration and provider access.
- Provider credentials and permissions must be configured by the school’s administrator. Never paste credentials into documentation.
- A hosted deployment needs a connector agent on the school network; a self-hosted deployment needs authorised network reachability.
This is a source capability reference, not evidence of a successful connection to your vendor account. Check the connector and version available in your deployment.
Next steps
Section titled “Next steps”For an available connector, open Admin → Connectors and check its configuration fields, requirements and permissions. Use Test connection before relying on synced records.
See connector configuration for shared setup concepts and the capability reference for reviewed support and limitations.