Smart lighting

Switches, scenes and energy, on one lighting desk

MeetCarbon Cloud smart lighting keeps multi-vendor gateways, luminaires, groups, scenes and strategies on one ledger. On, off, brightness and color temperature go out by luminaire, group or scene. Energy is compared by device, circuit and area. Cameras and panic buttons on the pole stay in smart street lights. Whole-building electricity, water, gas and heat stay in the energy management system.

Book a demo See pricing

Multi-gateway: Vendor adapters, one control surface
Groups & scenes: Batch on, off and dim by space
Five strategies: Timer, sun, sensor, event, composite
Three bases: Metered, estimated or hybrid energy

Lighting overview

Sample data

96%

Online

78%

Lights on

186

Today

kWh · sample

Energy mix

Roads42%
Parking28%
Common areas18%
Offices12%

Open

Main-road circuit offlineImportant
Sunrise strategy failed onceNotice

Path

From gateway claim to energy review

Luminaires land on the ledger first, then groups, then automatic execution. Circuit energy is how you check that a strategy ran as intended.

01
Connect a gateway
Register vendor, address and project, test the link, then sync spaces and devices.
Gateways
02
Claim devices
Claimed luminaires show online state, switch, brightness and color temperature.
Device list
03
Groups and scenes
Group by road, floor or function. Save common brightness levels as one-tap scenes.
Groups · scenes
04
Strategies run
Timer, sunrise, sensor, event or composite strategies hit their target by priority.
Policy center
05
Compare energy
Read energy, power and on-hours by device, circuit, area, group or site.
Energy overview
06
Events and audit
Offline, failed commands and manual actions stay in events, control logs and operation logs.
Ops & audit

Tour

Walk the lighting desk menu

These eight items match the live overview, topology, devices, groups, strategies, energy and operations pages. Base settings are covered under onboarding.

Smart lighting / Overview

Overview

On site

In-page tabs

Online rateLights-on rateToday’s energy

This page answers

Start with whether the estate is online, how much is on, and how much energy landed today. Abnormal circuits drill down from here.

Online, lights-on and alarms on one screen
Switch site so projects are not blended
Sample or metered marks stay next to the numbers

SampleOnline rate

Online96%

Lights on78%

Today186 kWh · sample

Alarms2

Online rate and kilowatt-hours in the sample cards explain the layout. They are not a site’s operating result.

States

Luminaires, policies and energy bases stay distinct

Online does not mean switched on. A policy sends commands only while enabled. Energy figures need a metered, estimated or hybrid mark.

Luminaire

Comms and the switch are separate. Brightness is 0–100%. Color temperature is in kelvin.

Online
Last report inside the offline threshold
Online
Offline
Comms lost, filed as a lighting event
Offline
On
Switch state is on
On
Off
Switch state is off
Off

Policy

Types: timer, sunrise and sunset, sensor, event, composite. Disabled policies do not fire.

Enabled
Sends to the target when conditions match
On
Disabled
Configuration stays, execution stops
Off

Energy basis

The same energy page can switch basis so an estimate is not read as a meter.

Metered
From a circuit or luminaire meter
Meter
Estimated
Power times hours on
Estimate
Hybrid
Meter where present, estimate elsewhere
Hybrid

9 statesThe offline threshold is a minute setting in base configuration. Failed policy runs stay on the policy list. They are not rewritten as a successful lights-off.

Who uses it

Facilities, operations, energy and integrators open different pages

The same lights-on: facilities want the scene, operations want offline, energy wants the circuit, integrators want the gateway link.

Question to answer

Will the road and lobby follow the scene tonight?

What they check

Enabled timer and sunrise policies
Whether groups cover the main road and lobby
Whether the scene run succeeded

Modules

Groups & scenesPolicy centerOverview

Savings sketch

Estimate energy from power, hours and brightness

Move the four controls to see the gap between the baseline window and the strategy window. The result follows the inputs.

Installed power80 kW

Baseline hours per day12 h

Strategy hours per day8 h

Brightness in strategy hours70%

Sample tariff0.80 CNY/kWh

Baseline hours use full power. Strategy hours scale power by the brightness percent. The window is fixed at 30 days and shown beside the result.

Strategy window uses less

+15,360kWh

Sample energy saved: 15,360 kWh
Sample bill gap: 12,288 CNY
Sketch days: 30

This sketch is a quantity illustration. It does not forecast a site savings rate and it is not a retrofit quote. Where meters exist, use the metered or hybrid figure in energy detail. Bills follow the local invoice.

Loop

See the lights, command them, then read the energy

A change starts on the overview and ends in the logs. Each step can return to the space tree and the group.

1
Read the overview
Online rate, lights-on rate and today’s energy decide whether to drill in.
2
Locate on the tree
Open a floor or road segment and confirm which group it is.
3
Run a scene or one light
Groups take a scene. One luminaire takes switch, brightness and color temperature.
4
Policies fire by priority
Enabled policies trigger on time. Failures stay on the list.
5
Compare the circuit
Pick metered, estimated or hybrid and read energy and on-hours.
6
File the event
Offline, control results and manual actions go to three logs.

Boundary

The luminaire ledger stays here

Switches, scenes, strategies and lighting energy live in smart lighting. Pole payloads, the building ledger, HVAC and protocol onboarding have their own products.

This product covers

Register, enable and connection-test multi-vendor gateways
Claim luminaires, then switch, brightness and color temperature
Group control and scene execution
Timer, sunrise, sensor, event and composite policies
Lighting energy overview and detail: metered, estimated, hybrid
Events, control log, comms and operation log

Neighboring products cover

Commands go to a lighting gateway that is already connected. Electricity settlement stays on the utility bill. Emission reports stay in the inventory.

Go-live

Five steps to bring one estate online

Connect the gateway, claim devices, group them, enable one policy, then see the circuit on the energy page.

Before you start

1Gateway vendor, address and project id
2Building, floor or road list
3Luminaires and their circuits
4Energy basis: metered, estimated or hybrid

Turn on offline alarms and the minute threshold in base settings after the gateway is reporting steadily.

1
Register the gateway
Enter vendor type and address, then run the connection test.
Done when · Test passes
2
Sync and claim
After spaces and devices sync, move them from unclaimed to the device list.
Done when · Online state on the list
3
Groups and scenes
Group roads, parking and the lobby, and save two everyday scenes.
Done when · Batch on and off works
4
Enable one policy
Pick timer or sunrise, set the target and priority, then enable it.
Done when · Run history is visible
5
Open energy
Pick site and time window, confirm the basis, then export.
Done when · Circuit energy exports

Platform

Many sites, many vendors, an action trail

The same lighting desk separates projects. Manual commands and policy triggers both leave a record. Deployment and price are on the pricing page.

Many projects

Campus, building and road keep their own overview, devices and energy.

Vendor adapters

Gateways join by vendor type. The control surface stays switch, brightness and color temperature.

Action trail

Manual control and policy triggers land in the operation log, control log and run history.

Energy export

Overview and detail export by time window for the monthly review.

SaaS

Opened per project, on the same MeetCarbon Cloud account as the other building products.

On-premises

When gateways can only reach the intranet, the platform can sit on the customer side.

Often opened together

Energy managementLighting energy joins the building breakdown.View Smart street lightsPole and payload services.View PricingSaaS, on-premises and implementation.View

Scenes

Buildings, roads and retrofits share this ledger

The space tree holds floors and road segments together. Other devices on the pole still go to smart street lights.

Campus and buildings

Lobby, corridor and garage grouped by floor. Office and meeting saved as scenes.

Roads and parking

Main roads and parking controlled by segment. Sunrise policies target the road group.

Common-area energy

Lighting-circuit energy enters the monthly compare, then the building breakdown.

Multi-vendor retrofit

Existing gateways stay on site. The platform adapts by vendor, then claims devices.

FAQ

Policies, savings rates and neighbors

Four boundaries customers check before go-live.

Once a policy is enabled, do the lights change on their own?

When enabled, a matching trigger sends switch, brightness, color temperature or a scene to the target group or device. The result is in run history and the control log. Disabled policies do not fire. People can still operate a device or a group by hand.

Is the savings rate on the page a commitment?

Figures on the overview and in this page’s sketch are marked as samples. Site energy follows the detail page and is marked metered, estimated or hybrid. Bills follow the local invoice.

How does this split from smart street lights?

Smart lighting covers switch, brightness, scenes, policies and lighting energy. Poles, cameras, broadcast, environment sensing and panic buttons stay in smart street lights.

How does this split from EMS and smart HVAC?

Lighting energy stays on its circuits here and can roll into the EMS breakdown. Temperature, fan and heating or cooling hours stay in smart HVAC and are not sent from a lighting policy.

Lay out one campus, lights and circuits

Tell us the gateway vendor, whether the scope is buildings or roads, and who switches lights by hand today. We demo groups, policies and the energy compare on that structure.