Temperature, policies, and kWh, on one HVAC console
MeetCarbon Cloud HVAC keeps connectors, controlled objects, groups, scenes, and policies on one ledger. Timers, temperature overruns, and occupancy can send on/off, setpoint, mode, and fan speed. Energy is compared before and after a policy. Contracted savings use baseline and actual kWh in M&V. Lighting loops stay in smart lighting. Building utility ledgers stay in energy management.
- API / MQTT
- Connectors bring in objects
- Groups
- Control a space in one go
- 3 triggers
- Timer, overrun, occupancy
- M&V
- Baseline against actual kWh
- Office group · AI tip awaiting confirmConfirm
- Meeting room · overrun policy firedRunning
- March M&V · baseline to checkSettle
From connected objects to savings you can check
Four stages map to pages already in the product. Scenes, policies, and kWh follow the same objects.
Connect
Sync site objects through an API or MQTT connector. Confirm discovered devices into the object list.
Group
Group by office, meeting room, and other spaces, and save common setpoints as scenes.
Dispatch
A timer, temperature overrun, or occupancy event sends on/off, setpoint, mode, or fan speed.
Check
Compare kWh before and after the policy. Contracted projects record baseline and actual in M&V.
What you see when you open smart HVAC
The menu groups watch, objects, policies, and energy with audit. Pick any item to see the work it does.
Overview
See objects online, policies running, and today’s kWh. AI tips dispatch only after someone confirms.
- Switch area and project
- Confirm before dispatch
- Figures are samples
Counts, kWh, and saving rates in the sample windows illustrate layout only.
Choose how it fires, then what it sends
Three triggers can already be set on a policy. The target can be a group, a space, or one object.
Runs by clock and weekday, for example off after hours and on before arrival.
AI tips on the overview dispatch only after confirmation. The confirm is written to the activity log.
Move the cooling setpoint, see sample daily kWh
One sample terminal shows the kWh gap versus a 24°C base. Quoted savings use policy effect, or baseline and actual in M&V.
Sample cooling: each +1°C reduces daily kWh by 4%
The sample scales linearly with setpoint. It omits load, outdoor temperature, and how many units run together. Quoted savings use policy effect, or a filled M&V baseline and actual.
Admins watch the overview, authors write policies, settlement checks the baseline
Duty staff watch live values and events. Authors write groups and triggers. Settlement reads M&V, not the sample numbers on the overview.
Are online units, policies, and tips to confirm in order today?
- Objects online
- Policies running
- AI tips waiting for confirm
Connectors, discovery, and manual control land on the same objects
Every command has to match an object. Lighting policies are not sent from here, and the building utility ledger is not rebuilt here.
API connector
Register an API link per site and sync objects and points.
MQTT connector
The same connector page supports MQTT. The last sync is stored the same way as API.
Discovered
Found devices stay pending until they enter the ledger and can be picked by a group or policy.
Manual on site
Switch, change setpoint, or change mode on an object. The control log keeps the command.
Policy runs
Timer, overrun, and occupancy dispatches enter the run log for effect analysis.
What this page does not rebuild
- On/off, brightness, and lighting loops stay in smart lighting.
- Electricity, water, gas, and heat ledgers stay in energy management.
- Thing models and protocol adapters stay in IoT device management.
- Hospital clean zones are monitored and alarmed. A policy change needs written approval.
Opening a work order is one policy action. Repair progress, spare parts, and a ticket desk are outside this product.
Connect objects and groups first, then turn a policy on
Use this order for the first office zone. An M&V baseline can be filled later. Control and logs can run before that.
- 1Site and connector address
- 2List of terminals to control
- 3Office and meeting groups
- 4Timer or overrun temperature band
- 5For a contract: baseline kWh and share ratio
Without a room-temperature point, an overrun policy will not include that object. A timer policy can run first.
- 01
Connect
Register API or MQTT and finish one sync.
You get · Objects and points - 02
Confirm
Move discovered devices into the ledger.
You get · Controlled objects - 03
Group
Group by space and save an arrival scene.
You get · Groups and scenes - 04
Write a policy
Pick timer, overrun, or occupancy, and fill the actions.
You get · A policy that can run - 05
Read the log
Confirm the command in live monitor and the control log.
You get · A trace - 06
Check savings
Fill before/after in policy effect, or baseline and actual in M&V.
You get · Savings you can check
Objects, policies, effect, and audit stay on one ledger
Smart HVAC covers terminal control and savings checks. Lighting, building totals, protocols, and building operations each have their own product.
Discover, then control
After a sync, unconfirmed devices stay on the discovered list.
Groups and scenes
Send one command to an office or meeting room. Scenes hold the usual actions.
Three triggers
Timer, temperature overrun, and occupancy. Actions include setpoint, mode, and fan.
Before and after
Policy effect lists kWh and power before and after a run.
Baseline and actual
Record saved kWh and the saving rate each month, with the share ratio.
Commands leave a trace
Manual, policy, and confirmed tips go to the control log or the activity log.
How neighboring products connect
Terminal temperature and HVAC policies stay on this page. Loops, ledgers, protocols, and building operations live in their own products.
Offices, rooms, public areas, and contracts share the same policies
These four match setups you can already configure.
Settle control and ledger boundaries first
How do smart HVAC and smart lighting divide the work?
Temperature, mode, fan, and heating or cooling hours are sent from this page. On/off, brightness, and lighting loops stay in smart lighting. An HVAC policy does not change a light.
How does this relate to energy management?
This page covers HVAC-object kWh, before and after a policy, and M&V. Building electricity, water, gas, and heat ledgers stay in energy management.
Can the kWh on this page be quoted?
Quote them only as samples. Overview and setpoint figures illustrate the layout. Quoted savings use before and after in policy effect, or a filled baseline and actual in M&V.
Do overview tips change the setpoint on their own?
They do not. A tip dispatches only after someone confirms. The confirm is written to the activity log.
Can repairs be tracked here after a work order is opened?
Opening a work order is an optional policy action. Repair progress and spare parts are handled in the operations product.
Can a policy be sent straight to a hospital clean zone?
Clean rooms and negative-pressure zones are monitored and alarmed. A policy change is sent only after written approval from the hospital.
Lock groups and policies for one office zone first
Tell us whether you need timed on/off, a temperature overrun, or a contract check. We will walk through objects, policies, logs, and M&V for that scope.