Silvair Energy Monitoring and the occupancy-monitoring service turn a commissioned Bluetooth NLC lighting network into an operational data source. Energy estimates combine an Energy Profile with luminaire dimming-level history; occupancy results aggregate occupancy-sensor status into historical zone data. A Silvair Gateway is required for these connected services, and 15-minute aggregation supports analysis. The services are not a utility meter or a people-counting system. [Source: SN-222 rev. 5.0, 19 March 2026; SN-218 rev. 2.0, 25 October 2022.]

What Is Silvair Energy and Occupancy Monitoring?

Silvair Energy Monitoring estimates how much energy the lighting installation uses and can support comparisons with a defined pre-upgrade baseline. the occupancy-monitoring service describes detected presence over time in a zone or area. Together, they provide a monitored view of lighting operation and space activity without changing the fundamental local control behavior of the network.

The information path is: compatible commissioned luminaires and sensors → Bluetooth NLC network → Silvair Gateway → enabled connected service → Web App, downloadable data, or authorized API access. Bluetooth NLC energy monitoring is therefore a service architecture, not an automatic feature of every Bluetooth device. A project needs compatible control and sensor hardware, commissioning with Silvair tools, correctly assigned Energy Profiles where energy monitoring is used, a configured Gateway, the relevant service enabled, and appropriate project/API permissions.

What Is Required Before Monitoring Works?

A Bluetooth NLC or Bluetooth Mesh label alone does not establish monitoring eligibility. The project must first be commissioned and its topology, zones, areas, devices, Gateway coverage, service entitlement, and user access must be aligned. For energy analysis, the measured luminaire power characteristics must suit the intended Energy Profile. For occupancy analysis, the selected zones need occupancy-sensor inputs that represent the area being studied.

This is also where suppliers matter. A luminaire supplier should provide the controller, driver, and sensor compatibility information; confirm the relevant DALI or 0–10 V interface where applicable; supply measured power data at several representative dimming levels; and identify whether fixtures grouped in a zone have consistent power characteristics. FY LIGHTING can support project teams with fixture, driver, interface, power-test data, commissioning samples, and pilot-test coordination. Final compatibility must always be confirmed for the selected project rather than assumed from a generic claim.

How Does Silvair Estimate Lighting Energy Use?

Silvair Energy Monitoring estimates lighting energy use by combining the Energy Profile assigned to a zone with the reported dimming or output level of its luminaires over time. An Energy Profile records measured power values at several representative dimming levels. It is not an illuminance measurement and does not mean the system is reading lux at the workplane. [Source: SN-222 rev. 5.0, sections 3 and 7.]

The service uses the applicable profile and dimming history to calculate energy. It visualizes energy use by zone and area, while downloadable data is provided as 15-minute aggregates per device. This distinction matters: device-level downloadable records, zone/area visualization, and project-level savings views are related outputs, but they are not one universal automatic aggregation hierarchy.

Silvair Energy Monitoring cannot reliably compensate for an incorrect profile, unsuitable power measurements, or mixed luminaire behavior within a zone. The official application note also states that the service cannot distinguish different luminaire types within one zone, and that each luminaire must have constant power for each light level. Careful zone design is therefore part of data quality, not an administrative afterthought.

How Does Silvair Occupancy Monitoring Interpret Sensor Data?

Silvair Occupancy Monitoring aggregates occupancy-sensor status into historical zone-level occupancy data. The result represents detected presence over time, rather than the number of people, occupied desks, or percentage of seats in use. It can reveal recurring activity patterns, but it is not facial recognition, identification, or headcount measurement. [Source: SN-218 rev. 2.0, sections 1–2.]

For space utilization monitoring, the appropriate question is whether a zone appears regularly active during defined periods, not how many people were present at any one moment. Smart building occupancy data should be read with the room’s purpose, operating hours, hybrid-work routines, booking evidence, sensor coverage, and business requirements. A rarely detected training room may be intentionally reserved for infrequent events; a low percentage alone does not prove the room is unnecessary.

How Are Data Organized by Device, Zone, Area, and Project?

Silvair Energy Monitoring produces different outputs for different scopes. The table prevents a common overstatement: not every dataset is simply rolled up in the same format from device to project.

This structure supports lighting energy analytics without implying that the Web App necessarily supplies every metric at every level. It also gives facility teams a way to match the data source to the decision: investigate a device pattern, compare zones, review an area, or discuss a project baseline.

Occupancy Monitoring vs. Occupancy Control

Local occupancy control answers an immediate question: should lighting respond now? It can trigger lighting behavior from a sensor event inside the commissioned network. Silvair Occupancy Monitoring answers a historical question: what pattern of detected presence was recorded over time? The Gateway-connected service centralizes historical zone analytics through the Silvair Web App and APIs. [Source: SN-218 rev. 2.0; SN-221 rev. 2.13, 5 March 2026.]

The distinction should not be exaggerated. Compatible devices may expose device-level status or diagnostic information in commissioning workflows. The connected service adds centralized historical reporting for the defined monitoring scope; it does not erase all other diagnostic visibility. Bluetooth NLC energy monitoring similarly complements local control with a data layer rather than replacing normal lighting operation.

Silvair Web App, Data Downloads, and APIs

The Web App provides energy reporting by zone and area and occupancy reporting for the service scope. Energy downloads provide per-device, 15-minute aggregate data. Authorized project APIs can expose energy-consumption and zone-occupancy information for external facilities, sustainability, or smart-building systems. [Source: SN-222 rev. 5.0, section 4; SN-221 rev. 2.13, sections 6–7.]

Avoid treating these outputs as interchangeable. A report designed for a zone comparison is not the same as a device data download, and an API integration needs authorization, version awareness, and scope validation. Lighting energy analytics is most reliable when the team records the time range, data completeness, baseline assumption, and business question before interpreting a result.

Gateway Capacity and Network Planning

Both monitoring services require a Silvair Gateway. Silvair guidance indicates that one Gateway should monitor approximately 200 devices across all relevant areas; exceeding that scale can lead to inaccurate energy and occupancy reports. At least one device in every area using the service needs a direct connection to the Gateway. Gateway quantity also depends on building construction, device count, area distribution, and the connected services selected. [Source: Silvair FAQ; SN-213 Recommendations for Complex Lighting Installations.]

Capacity is not merely a purchasing number. A project with metal partitions, long distances, separated floors, or uneven area layouts may need a different plan from a similarly sized open building. During design, validate direct connectivity, area coverage, expected device count, and the monitoring service scope before treating the approximate 200-device figure as a complete design rule.

Data Accuracy, Outages, and Interpretation Limits

Silvair Energy Monitoring is calculated data. Errors can arise from unsuitable power measurements, an incorrect Energy Profile, inconsistent fixtures within a zone, unavailable dimming history, or loss of reporting continuity. A luminaire power interruption, sensor failure, Gateway offline event, and cloud/network interruption have different operational meanings and should be investigated separately.

For Silvair Occupancy Monitoring, a zero-occupancy period does not always prove that a space was unused. Silvair’s FAQ explains that a power failure may appear as zero occupancy rather than as a separately marked outage condition. Facility teams should compare occupancy results with Gateway, power, and network status before concluding that a space was vacant. [Source: SN-218 rev. 2.0, FAQ.]

These limits are especially important for smart building occupancy data. A result can support investigation, but it cannot by itself establish a causal explanation, prove a person count, or replace a documented outage log. Preserve source records and note any reliability or completeness issue alongside the conclusion.

How Facility Managers Can Use the Data

Facility managers can use Silvair Energy Monitoring to compare lighting patterns by zone or area, investigate unusual after-hours operation, assess control changes, and review a retrofit against a documented baseline. They can use Silvair Occupancy Monitoring to examine recurring zone activity and support space utilization monitoring. Combining the two helps teams ask better questions: does high energy align with known operating needs, or does low detected use suggest a scheduling or control review?

For example, high energy with low detected presence may justify checking schedules, minimum output settings, after-hours policies, or sensor coverage. High energy with high detected presence may be normal for an intensively used zone. The services show patterns; they do not automatically allocate savings among LED efficacy, occupancy sensing, daylight harvesting, scheduling, and high-end trim. Bluetooth NLC energy monitoring supports an evidence-led improvement loop, not a guaranteed causal breakdown.

What Should a Silvair-Ready Luminaire Supplier Provide?

A supplier supporting a Silvair-ready project should provide product-specific evidence rather than broad compatibility language. Useful material includes driver and controller details, sensor behavior, interface confirmation, measured power at representative dimming levels, fixture consistency for each planned Energy Profile, physical integration information, and samples for commissioning or pilot testing.

FY LIGHTING can help organize these inputs across the luminaire, driver, control interface, and power-test record so that the project team can validate the monitoring design before scale deployment. This is a practical path to better lighting energy analytics and fewer later corrections. Bluetooth NLC energy monitoring should be specified as a connected-service design with validated device coverage. Lighting energy analytics should retain documented assumptions when shared with stakeholders. Space utilization monitoring should be paired with operational context, and smart building occupancy data should be reviewed alongside power and Gateway status. This approach keeps space utilization monitoring focused on patterns and lets smart building occupancy data support investigation rather than replace operational judgment. It is not a substitute for Silvair’s project commissioning, service authorization, or final technical approval.

FAQ

Is Silvair Energy Monitoring a utility-grade electricity meter?

No. Silvair Energy Monitoring calculates estimated lighting use from Energy Profiles and dimming/output-level history. It is useful for trends, comparisons, and operational analysis, but billing, contractual settlement, or regulatory reporting should use appropriate metering and formal measurement-and-verification methods. [SN-222 rev. 5.0.]

Does Silvair Occupancy Monitoring count people or occupied seats?

No. It reports historical detected presence at zone or area scope. Silvair Occupancy Monitoring does not identify people, calculate an exact headcount, or establish a percentage of seats occupied. [SN-218 rev. 2.0.]

Is a Silvair Gateway required for monitoring?

Yes. A Silvair Gateway is required for the connected Energy Monitoring and Occupancy Monitoring services in the relevant area. Basic local lighting control is a separate network function. [Silvair FAQ.]

How many devices can one Silvair Gateway monitor?

Plan for approximately 200 devices across all relevant areas. More devices may reduce report accuracy, and the final Gateway plan depends on building construction, layout, device count, area distribution, and service scope. [Silvair FAQ; SN-213.]

How is an Energy Profile created?

It is based on measured luminaire power at several representative dimming levels and assigned to the applicable zone during project setup. The measurement must represent the actual fixture and driver behavior. [SN-222 rev. 5.0.]

Can different luminaire types share one Energy Profile?

Not safely as a general rule. The energy service cannot distinguish different luminaire types within a zone, so grouping fixtures with inconsistent power characteristics can reduce the quality of calculated results. [SN-222 rev. 5.0.]

What energy and occupancy data can be downloaded?

Energy downloads provide per-device, 15-minute aggregates. Occupancy information is available as historical zone-level data through the relevant service and authorized access methods; verify current project scope before specifying an integration. [SN-218 rev. 2.0; SN-221 rev. 2.13.]

What happens during a power or Gateway failure?

Do not interpret every gap or zero as normal vacancy. A power failure can appear as zero occupancy, while a Gateway, sensor, luminaire, or cloud/network interruption may affect data differently. Check operational status before drawing conclusions. [SN-218 rev. 2.0; SN-222 rev. 5.0.]

Can Silvair monitoring data be accessed through an API?

Yes, where the project has the relevant service and authorization. Silvair APIs include energy-consumption and occupancy access; implementation scope and permissions should be confirmed against the current API documentation. [SN-221 rev. 2.13, 5 March 2026.]

Can Silvair data support retrofit performance analysis?

Yes, for trend analysis, before/after comparison, and anomaly investigation against a documented baseline. It should not alone be presented as contractual energy confirmation or formal M&V; use meter data and an appropriate M&V method when that level of proof is required.

*Technical references checked on 4 September 2026: SN-218 Silvair Occupancy Monitoring Description, rev. 2.0, 25 October 2022; SN-221 Silvair APIs Application Note, rev. 2.13, 5 March 2026; SN-222 Silvair Energy Monitoring Application Note, rev. 5.0, 19 March 2026; Silvair FAQ and SN-213 Recommendations for Complex Lighting Installations. Verify current revisions before publication.*