Skip to content
Innomesh
Portal

Alerts

This reference covers the full catalogue of alerts that appear in the Innomesh Portal Hotlist. Each alert type is documented with its trigger conditions, severity level, grace period behaviour, and the subscription tiers to which it applies.

Alert Severity Levels

Alerts are classified into five severity levels:

SeverityDescription
CriticalImmediate attention required; service is impaired
HighSignificant issue that may impact service
MediumNotable condition that warrants investigation
LowMinor issue or informational warning
NoticeInformational event with no service impact

Alert Categories

Innomesh Environment and Edge Compute Host Alerts

These alerts monitor the health of the Innomesh servers and edge compute hosts that power your environment.

📝 Note
Host CPU alerts use a 2-minute threshold window to prevent one-off spikes from triggering critical alerts.
AlertTriggerTierSeverityGrace Period
Host StorageEdge compute server’s local disk usage exceeds 80%Space VC, Space CEMediumYes
Host StorageEdge compute server’s local disk usage exceeds 90%Space VC, Space CECriticalYes
Host MemoryEdge compute server’s memory usage exceeds 80%Space VC, Space CEMediumYes
Host MemoryEdge compute server’s memory usage exceeds 90%Space VC, Space CECriticalYes
Host CPUEdge compute server’s CPU usage exceeds 80% (sustained 2 minutes)Space VC, Space CEMediumYes
Host CPUEdge compute server’s CPU usage exceeds 90% (sustained 2 minutes)Space VC, Space CECriticalYes
Host HealthEdge compute server fails to respond to 3 consecutive service-status pingsSpace VC, Space CECriticalNo
LicensingNumber of rooms exceeds the subscribed Innomesh room licence countAllCriticalYes
Alert InfluxHigh influx of Low, Medium, or High severity alerts detectedAllCriticalNo
📝 Note
In a high-availability (HA) setup, Host Health triggers an automatic host rotation and the issue self-resolves.

Room Alerts

Room-level alerts track the operational health of individual rooms.

AlertTriggerTierSeverityGrace Period
Room HealthRoom fails to respond to 5 ping requests from InnomeshSpace VC, Space CECriticalYes
User Interface UnhealthyA Space CE touch panel (HTML5 or VC-4 Gateway) is disconnected from the roomSpace CEHighYes
Gateway Device ConnectionA VC-4 Gateway device is reported disconnected or offlineSpace VCHighYes
Room MemoryRoom’s memory usage exceeds 400MBSpace VC, Space CELowYes
Room MemoryRoom’s memory usage exceeds 600MBSpace VC, Space CEMediumYes
Room CPURoom CPU exceeds 6% (Space CE) or 20% (Space VC)Space VC, Space CEMediumYes
Room CPURoom CPU exceeds 12% (Space CE) or 25% (Space VC)Space VC, Space CEHighYes
Room StuckRoom is stalled within Crestron VC-4 (stuck in “Starting” state)Space VCCriticalNo
Device Set HealthA device set in the room becomes unhealthySpace VCMediumNo
Room Has Undocked MicrophonesOne or more microphones are undocked while the room is powered offSpace VC, Space CELowYes

Device Endpoint Alerts

Endpoint alerts cover connectivity and communication for individual devices.

AlertTriggerTierSeverityGrace Period
Endpoint ConnectionHigh-criticality Crestron native endpoint reported as disconnected (touch panels, NVX encoders/decoders, HDMI switchers)Space VCHighYes
Endpoint ConnectionAny other Crestron native endpoint reported as disconnectedSpace VCMediumYes
Endpoint CommunicationHigh-criticality third-party endpoint not communicating (projectors, LCDs, DSPs, matrixes, switchers, recorders, PDUs, AV network switches)Space VC, Space CEHighYes
Endpoint CommunicationLow-criticality endpoint not communicating (people-counting cameras, IP clocks)Space VC, Space CELowYes
Endpoint CommunicationAny other endpoint not communicatingSpace VC, Space CEMediumYes
Endpoint RespondingHigh-criticality endpoint not responding to network pingsPulseHighYes
Endpoint RespondingAny other endpoint not responding to network pingsPulseMediumYes
Endpoint ReachabilityInnomesh Sight fails to connect to a deviceSightLowNo
Endpoint AuthenticationInnomesh Space or Sight fails to authenticate to a deviceSpace VC, Space CE, SightLowNo
Endpoint Lamp HoursProjector is nearing its lamp life threshold (see Projector Lamp Life Thresholds below)Space VC, Space CE, SightLowNo
Endpoint TemperatureEndpoint exceeds its recommended operating temperatureSpace VC, Space CE, SightLowNo
Endpoint Battery LevelBattery level for a device endpoint (typically a wireless microphone) drops below 20%Space VC, Space CE, SightMediumYes
Endpoint Battery ErrorBattery for a device endpoint reports an errorSpace VC, Space CE, SightMediumYes
Peripheral HealthA peripheral device is disconnected from the host device (e.g. USB cameras on MTR, speakers on DSPs)MTR Integration, Zoom IntegrationLowYes
Q-Sys CPU UsageQ-Sys device CPU usage exceeds 80%Q-Sys IntegrationMediumYes
Q-Sys Memory UsageQ-Sys device memory usage exceeds 80%Q-Sys IntegrationMediumYes
Q-Sys Disk UsageQ-Sys device disk usage exceeds 80%Q-Sys IntegrationMediumYes

Room Information Alerts

Low-severity notifications that flag missing or anomalous room metadata.

AlertTriggerTierSeverityGrace Period
Room Information MissingNo information associated with a roomAllNoticeYes
Room Information AnomalyRequired room information fields are not populatedAllNoticeYes
Non-Standard Room NameRoom name is detected to be non-standard (for tenants using standard room names)AllNoticeYes

Projector Lamp Life Thresholds

Lamp hour alerts trigger when a projector’s lamp usage reaches the manufacturer-recommended replacement threshold. If a specific model is not listed, Innomesh falls back to the manufacturer’s DEFAULT value below. If the projector is not covered by any manufacturer, it defaults to 1,500 hours.

BrandDefaultExample model-specific overrides
Epson15,000 hoursEB-1410 / EB-1410WI: 3,100; EB-1420 / 1430 (all variants): 3,600; EB-1450 / 1460 (all variants): 4,600; EB-1470 / 1485 / L610U / L730U / L735U / PU2216B: 17,500; EB-G5450WU / G6900WU / Z10000U / Z10005U / Z11000WNL: 1,600; EB-Z8450WU / Z9900WNL: 2,100
NEC3,600 hoursNP1150 / NP1250 / NP2250 / NP3150 / NP3250 / NP3250W: 1,800; PA500U / PA500X / PA550W / PA600X: 2,700; PA622 / PA622U / PA672 / PA672U / PA672W: 3,600; PA1004UL / PA803UL / PX803UL: 20,000; PA804UL: 17,000; PH1000 / PH1000U: 1,600
Panasonic6,000 hoursFW430 / PT-FW30U / PT-FX00U: 6,000; PT-FRZ50 (all variants): 20,000; PT-MZ570 / PT-RQ22K / PT-RQ35KE / PT-RZ120 (all variants) / PT-RZ24KE / PT-RZ570 (all variants) / PT-RZ660 (all variants) / PT-RZ670 (all variants) / PT-RZ770 (all variants) / RZ970: 20,000
Samsung50,000 hours
Sony3,000 hoursVPL-FH300 / VPL-FW300: 2,100; VPL-FH300L: 6,000; VPL-FH35 / VPL-FH36: 2,500; VPL-FH500L: 5,600; VPL-FHZ120: 10,000; VPL-FHZ55 / FHZ57 / FHZ58 / FHZ60 / FHZ65 / FHZ66 / FHZ70 / FHZ75 / FHZ85 / FHZ90 / FHZ90L / FHZ91L / FHZ120L / FHZ131L / FHZ700 / PHZ10 / PHZ11: 17,500; VPL-FW300L / VPL-FWZ700L: 20,000

Thresholds can be customised per device if the default does not match your maintenance schedule.

Device Endpoint Temperature Thresholds

Temperature alerts fire when a device exceeds its maximum operating temperature. The default threshold is 40 degrees Celsius unless a device-specific override is defined.

BrandModelThreshold (C)
AMXDGX60
AMXDVX55
ExtronIN-160860
ExtronCrosspoint DTP65
PanasonicDefault60
PanasonicRZ47068
PanasonicRZ57075

Grace Periods

Many alerts include a grace period during which the condition must persist before the alert is published to the Hotlist. This prevents transient events from generating unnecessary noise. Grace period durations are indicated in the alert catalogue for each alert type.

On this page