Silvair BACnet Gateway and BMS Integration

The silvair BACnet gateway is an on-premise BACnet/IP bridge between a commissioned Bluetooth NLC lighting system and a Building Management System (BMS). It exposes documented group and device objects, while allowing selected group-level commands. It adds supervisory visibility and coordination; it does not replace local lighting logic or directly control HVAC. [1][2]

This article is written for BMS designers, electrical specifiers, and integrators. It uses current official documents as its technical baseline and separates confirmed product behavior from project-level decisions.

Applicable Gateway Model and Documentation

This page applies to the Silvair BACnet GW hardware identified in the current PICS as product model Minew G1-E, application software 1.1 and firmware revision 1.3.8 (5 March 2026). “SGW-104” is the document code for the Silvair BACnet Gateway user manual, revision 3.2; “SGW-105” is the document code for the BACnet PICS, revision 1.2. They are not two alternative gateway hardware models. All numeric limits and object details below are tied to those documents and must be rechecked when the firmware, PICS, or project configuration changes. [1][2]

Why Connect Bluetooth NLC Lighting to a BMS?

A silvair BMS integration connects local lighting information to building operations. Bluetooth NLC lighting can continue to handle occupancy response, daylight response, wall control, scenes, scheduling, and zone automation. The BMS can then view selected status and use it in higher-level building logic. This division supports a practical lighting BMS integration without making the BMS the mandatory controller for every lighting event. The silvair BMS integration boundary should be documented in both the controls narrative and BMS point list.

• BMS visibility of group occupancy, ambient light, energy, light state, and health
• Centralized maintenance and alarm workflows
• Selected building-mode commands: light-level set and scene recall
• Inputs for cross-system logic, subject to the BMS design and project commissioning

How the Gateway Architecture Works

Luminaires / sensors / controllers  →  Bluetooth NLC lighting network  →  Silvair BACnet Gateway  →  BACnet/IP objects  →  BMS

The silvair BACnet gateway collects supported lighting-network information and represents it as BACnet objects. On writable objects, a BMS write becomes a group-addressed Bluetooth mesh message. This Bluetooth NLC BACnet architecture preserves distributed lighting operation while offering the BMS a standards-based integration boundary. A Bluetooth NLC BACnet project should document the group-to-object mapping before BMS graphics are built. [1][2]

Local network boundary and BACnet/IP

The silvair BACnet gateway is specified for on-premise integration, has one 10/100 Ethernet RJ45 port with PoE support, and uses BACnet/IP 1.30. SGW-104 states that the gateway itself is not capable of Internet communication. That is a device boundary, not a claim that the wider BMS is offline or secure by default. A wireless lighting BMS architecture still needs its own upstream security and remote-access design: remote access, segmentation, authentication, and upstream connectivity are determined by the project network. The Silvair BACnet PICS describes BACnet/IP with non-BBMD functionality; where cross-subnet discovery is required, the BMS network design must determine BBMD or other routing arrangements rather than assuming they are built into the gateway. [1][2]

Capacity, Area Scope, and Expansion

Capacity must be read at the gateway scope. For the silvair BACnet gateway, SGW-104 specifies approximately 200 Bluetooth mesh devices per gateway, up to 100 lighting zones per gateway, and one Area per gateway. The PICS summarizes this as up to 200 nodes and up to 100 groups per Area; within the cited architecture, that Area is the single Area controlled by the gateway. It is not a statement that one gateway can manage unlimited Areas. A multi-Area project should plan one gateway per represented Area and validate the resulting BMS point count, IP plan, and BACnet device/object-instance allocation. [1][2]

BACnet Objects: What the BMS Can Read and Write

The object types, units, and direction below follow SGW-105 rather than inferred BACnet conventions. Structured View objects also represent the Project, Area, Zone, and group topology, so operators can relate points to the lighting installation. A Silvair BACnet point list should record the configured object names and instance ranges at handover. [2]

COV and refresh behavior

The PICS supports SubscribeCOV and COV notifications, and the user manual says data is shared through COV. That does not mean every value is a fixed-latency real-time stream. Most listed status objects are recomputed immediately after a valid new message from a group member; Group Energy Use is computed every 15 minutes. Integrators should test subscriptions, point freshness, and BMS alarm delays for the exact configuration instead of promising universal push behavior. [1][2]

Occupancy, Ambient Light, and Energy: Engineering Limits

Group Occupancy Status is a current aggregated zone signal, not a people count, occupant-tracking feed, or complete utilization analysis. Group Ambient Light Level is an average in lx, using the most recent valid ambient-light information from group members. These inputs can inform dashboards or BMS logic, but sensor coverage, group boundaries, and hold-time settings must be reviewed before using them outside lighting control. [2]

Group Energy Use is energy, not instantaneous power: the PICS defines an Analog Input in Wh and a Sum aggregation. It is calculated every 15 minutes from Precise Total Device Energy Use received in Sensor Status messages from active nodes; unknown or invalid values are ignored. Therefore, compatible devices must actually report that energy data. Do not label this point as W, use it as a demand measurement, or equate it with the separate cloud Energy Monitoring service. [2]

Health Status and BMS Alarm Mapping

The gateway provides useful, defined health states rather than an undefined “fault” flag. Group Health Status can report No-Fault, Member Fault, Lost & No-Fault, Lost & Fault, or All Lost. Device Health Status can report No-Fault, Light Source error, Control Gear error, or System error. The BMS alarm priority, routing, and maintenance procedure remain project-configured decisions. [2]

The table is an example mapping, not a manufacturer-defined alarm policy. Site teams should validate state-to-alarm rules, suppress transient conditions appropriately, and retain the documented project configuration.

BMS Commands, Scenes, and Control Ownership

Group Light Level Set is an Analog Output with a 0–100% range. Each write sends Light Lightness Linear Set Unacknowledged messages to the configured group address. Group Scene Recall is a Multi-State Output with four valid states, mapped as Scene Recall 0 through Scene Recall 3 in the PICS. These are recall values, not fixed business names: “Cleaning” or “After Hours” is only an example if the project team has configured that meaning in Silvair. A BMS cannot use this object to create arbitrary scene parameters. [2]

When a group command is already in progress, the PICS describes a single-element queue: a newer write replaces a queued value. More importantly, the documents do not define one universal priority order for BMS commands, occupancy logic, daylight control, manual wall control, schedules, and scenes. The integration specification should explicitly test override duration, manual intervention, return-to-auto behavior, and command ownership. This is essential for a reliable Bluetooth mesh BACnet gateway deployment. It should also be reviewed when a Bluetooth mesh BACnet gateway is moved, reconfigured, or replaced. A silvair BMS integration specification should assign the responsible party for those tests.

Lighting Data for HVAC and Other Systems

A silvair BMS integration can expose occupancy and lighting status as inputs to BMS automation. The gateway does not directly operate HVAC equipment. A Lighting Group also may not match an HVAC Zone: sensor coverage, zone geometry, occupancy hold times, and BMS control logic all affect whether the data is suitable for an HVAC sequence. Treat the signal as one engineered input, not a guaranteed HVAC occupancy determination or a promised energy-saving outcome.

Lighting sensor  →  Bluetooth NLC group status  →  BACnet/IP object  →  BMS logic  →  HVAC / security / dashboard

Network Design, Commissioning, and Acceptance

Network requirements to confirm

• Unique BACnet device identity and coordinated object-instance range; the configuration uses a BACnet Device ID starting number.
• DHCP or static IPv4 addressing, subnet mask, gateway, BACnet port (default 47808 when left empty), and BMS reachability.
• VLAN and firewall rules that permit the necessary BACnet/IP traffic. Design cross-subnet discovery and BBMD responsibilities at the BMS-network level; do not assume gateway BBMD capability.
• Physical Ethernet/PoE or approved power, gateway placement within mesh range, and a completed lighting-network quality check.
• Access control for BMS servers and project network operations. Do not claim BACnet/SC, TLS, or a specific remote-access feature unless separately documented for the deployed version.

Commissioning checklist

Example: Office Area Integration

In an office Area, Silvair local sensing and control can operate the lighting zones. The gateway supplies Group Occupancy Status, Group Energy Use, light state, and health points to the BMS. The BMS uses a defined building mode to write a Group Scene Recall value after hours, while a project-configured alarm rule turns a Group Health Status condition into a maintenance ticket. The BMS team separately decides whether occupancy is an appropriate input for the corresponding HVAC zone. This example requires configured scenes, point mapping, network access, and commissioning; it is not a customer case study or a savings claim. It is a lighting BMS integration scenario, not an automatic HVAC control scheme, and the same wireless lighting BMS workflow should be tested end to end.

FY LIGHTING Solutions for BACnet BMS Projects

FY LIGHTING can support project discussions around luminaire form factor, driver integration, mounting, and technical coordination for a Silvair-based BMS project. However, support for 0–10 V, DALI, or PWM alone does not establish Bluetooth NLC compatibility, and FY LIGHTING should not be represented as manufacturing the Silvair BACnet Gateway. Specify a FY LIGHTING luminaire as Silvair-compatible only after the exact device, control component, firmware, project design, and applicable qualification evidence have been verified. This protects the procurement team and keeps the lighting BMS integration claim evidence-based. It also supports a wireless lighting BMS scope that is credible at tender and handover.

Technical Sources and Scope

Silvair, “SGW-104 Silvair BACnet Gateway user manual,” rev. 3.2, 5 March 2026: Official PDF

Silvair, “SGW-105 Silvair BACnet PICS,” rev. 1.2, 5 March 2026: Official PDF

BACnet International, BTL listing for Silvair BACnet GW: BTL listing

Key factual statements in this article are tied to [1] SGW-104 and [2] SGW-105. Confirm the version supplied for the actual project before design release, procurement, or final commissioning. In every Bluetooth NLC BACnet and lighting BMS integration package, retain this version record with the final point list.

FAQ

Which Silvair BACnet Gateway model is covered here?

The current official documents identify the product as Silvair BACnet GW, model Minew G1-E. This article uses SGW-104 user manual rev. 3.2 and SGW-105 PICS rev. 1.2, both dated 5 March 2026.

How many nodes and groups can one gateway support?

The cited SGW-104 manual specifies up to approximately 200 Bluetooth mesh devices, up to 100 lighting zones, and one Area per gateway. Plan additional gateways for additional represented Areas and verify the project configuration. This is a wireless lighting BMS capacity boundary, not a site-wide device total.

Does the gateway support BACnet/IP and BTL listing?

The user manual specifies BACnet/IP 1.30. The PICS identifies a B-ASC profile, and the BACnet International listing identifies Silvair BACnet GW as BTL Listed. Verify the listing and deployed version during procurement. That verification is part of a silvair BMS integration and Bluetooth NLC BACnet design review; it should include the selected Bluetooth mesh BACnet gateway configuration.

What is the difference between Group Energy Use and Energy Monitoring?

Group Energy Use is a local BACnet Analog Input in Wh, summed from active nodes and computed every 15 minutes. It is not instantaneous power and is not automatically equivalent to a cloud Energy Monitoring service.

Can a BMS override occupancy and daylight control?

A BMS can write documented group level and scene-recall objects, but no universal priority or return-to-auto rule should be assumed. Define and test ownership, manual intervention, and recovery behavior in the project configuration.

What happens if BACnet communication is lost?

The required local lighting behavior must be demonstrated in commissioning. The gateway is an integration layer; local control ownership and recovery behavior depend on the configured lighting project and BMS design.

Can one gateway connect multiple lighting Areas?

Not within the cited SGW-104 scope: it specifies one Area per gateway. A multi-Area project should allocate gateways and BMS objects accordingly.

Can BACnet occupancy data be used for HVAC automation?

Potentially, as one BMS input. Confirm that lighting-group coverage, hold time, zone mapping, and BMS logic make it appropriate; a Lighting Group is not automatically an HVAC Zone.

What belongs in a BACnet integration point list?

Include the applicable document/firmware version, gateway and Area names, object names and instances, read/write direction, units, COV or update expectations, alarm mapping, command ownership, network details, and signed test evidence.

Does a luminaire need Bluetooth NLC qualification to be called Silvair-compatible?

Yes—compatibility must be verified for the exact product and control configuration. Driver-interface support alone is not proof of Bluetooth NLC or Silvair project compatibility.