Skip to content
visibleDMX
Log in
Remote monitoring for Pharos installations

See what needs attention. From anywhere.

Bring every site, Pharos controller, and RDM fixture into one view. Find faults, inspect device history, and act remotely with the context you need.

Log in to console Explore the tools
visibleDMX Dashboard Sites

Harbour Hall

Site details and monitoring information

Site Information

Europe/Stockholm

Total Fixtures: 48

Nodes

2

All nodes online

System Health

Attention required

3 fixtures unavailable

Controllers

Main stage

LPC 1 · 0040223

Fixtures32
NodeEdge 01

Foyer

Express Control · 0040251

Fixtures16
NodeEdge 02

Site overview

Attention required (3)
Online
44
Offline
1
Stale
1
Unreachable
1
Unknown
1
Fixtures Status DMX
Main stage 07 Offline 1.049
Foyer 12 Unreachable 2.089
Main stage 18 Stale 1.137
Site overview · Example data. Controllers first, then the fixtures that need attention.

From a site-wide view to a single fixture.

Start with the problems, follow them to the controller or fixture, and choose the next step. The same console brings monitoring, alerts, and remote access together.

Problems first

Open a site with attention required already selected. Distinguish offline, stale, and unreachable fixtures, then filter by status across controllers.

Offline and recovery alerts

Choose recipients, an offline delay, and a repeat-alert window for each site. Receive offline and recovery notifications while limiting repeated emails.

RDM controls with command feedback

Check a fixture on demand and edit supported RDM parameters, including labels, DMX addresses, and personalities. Follow the command result in the console.

A route to the local controller

Download a node’s VPN profile when provisioned. Connect with your VPN client to reach the Pharos controller on its local network.

The detail behind the status.

A fixture going offline is only the starting point. See the controller, connection, and device history together to understand where to look next.

Know the controller

Inspect the hardware model, serial number, IP address, firmware, and uploaded project, with further network and system details when reported.

Follow the history

Review fixture uptime, sensor readings, and RDM communication counters over selectable periods from 12 hours to 30 days.

Maintain the edge

Inspect node CPU and memory trends, pause controller polling during maintenance, and install published, signed edge software releases.

Give each team the right access

Invite colleagues to specific sites with read, write, or site-admin permissions. Keep site access and alert recipients under your control.