Virtual Devices
Virtual devices give an existing measurement or several physical devices one reusable device identity. They appear in ordinary device and room views, while their details retain the physical source and current quality. From Devices, the Virtual device wizard offers an existing projection and four additional types: aggregate sensor, numeric converter, light group, and thermostat controller.
A virtual thermostat controls real outputs only after its actuator profile and installed equipment are qualified and explicitly activated. A saved controller can remain a draft. The UI’s requested mode is not proof that a relay is active or safe.
Create and repair a measurement
Choose the type
In Devices, select Add Device, then Virtual. Choose Aggregate sensor to combine temperature readings, or Numeric converter to transform one physical numeric input. Use the existing Projection option for a mapped view of an existing device.
Select and preview inputs
For an aggregate, select compatible physical temperature sources and configure its operator, maximum source age and minimum valid source count. The preview explains excluded, missing or stale sources. For a converter, select one physical numeric source, declare the output quantity and unit, and choose the typed conversion policy. Affine, piecewise, NTC beta and Steinhart–Hart are available; use calibrated coefficients and valid input/output domains for a thermistor. Check the preview with representative samples before saving.
Save and inspect
Open the created device’s detail page to read its value, unit, source quality, age and binding diagnostics. An unavailable current value does not erase its previous history. A converted temperature can feed an aggregate or thermostat only when its declared quantity, unit and quality are valid.
Edit or repair
Use the device’s Edit or Repair action when a source is replaced or disappears. Rebind the source and review the preview before saving. A repair retains the virtual output identity and history; it does not turn old samples into fresh ones.
A voltage input is not itself a temperature. Use a converter with explicit calibration when the physical source reports voltage; use a native temperature helper only when it actually exposes a valid Celsius value, unit and quality.
Create and use a light group
Choose Light group in the Virtual wizard, name it and select physical light channels. Preview the capabilities shared by every member, then choose which common controls to expose. The group detail lets you inspect its members and edit or repair the binding when a physical channel changes. Controls for power, brightness or color appear only when compatible with all selected members.
A group may show mixed or unknown state. After a command, inspect member outcomes if the parent reports partial success; a successful member must not conceal a failed or offline one. The same common controls are available in the panel and from room or scene control. If a physical light and its group are both assigned to a room, that physical light contributes once to room state. Group membership does not create an extra energy meter or replace physical-device provenance.
If two groups in the same room share a physical light, room lighting reports an overlap conflict and refuses the room command. Open the room’s Lighting roles dialog, keep one group participating, and set the other group’s role to Hidden. This excludes that group from the room’s lighting state and commands. The group remains listed in the roles dialog so you can restore its participation; restoring an overlap brings the conflict back. This room role preserves group membership, direct device controls and device visibility settings.
Create a thermostat controller
Choose Thermostat controller in the Virtual wizard. Select a valid ambient temperature source: a physical sensor, aggregate, or qualified numeric converter. Bind only supported heating and cooling outputs. Configure the actual installation’s setpoints and deadband, and preview the actuator profile before saving. Unsupported or conflicting output combinations are rejected.
For a heating installation with floor protection, select a separate floor temperature input and supply the installed system’s floor limit and recovery hysteresis. At or above the limit the controller releases heat; invalid or stale mandatory floor input inhibits heating. Heat can resume only with a fresh floor reading strictly below the limit minus hysteresis and with every other guard clear. Do not use a room average as the floor probe or assume a default safe floor temperature.
You can bind physical window contacts and configure automatic window detection independently. An open contact or detected window event pauses output. When the pause clears, the controller reevaluates the latest mode and setpoint, including changes made while paused. Off, input faults, floor protection and uncertain output state take priority over comfort demand. Heating and cooling outputs must not be active together.
After saving, open the thermostat detail to inspect the requested mode, actual heating/cooling activity, floor reading, protective reason, and installation status. Use Edit or Repair to replace a sensor or output and recheck the profile. A controller without completed qualification remains a draft; configuration or UI preview alone never energizes it. The panel and room climate controls use the same requested-setting path and should be checked against the reported activity and diagnostics.
For a live installation, the operator must verify physical input behavior, sensor calibration and age, output isolation, bounded command/restart behavior, independent equipment protection, and any opposed-output interlock under a concrete approved procedure. Record the qualification against the installed profile before activation.
Room readings and input freshness
Room climate readings count an aggregate’s physical sources once. To include a sensor-role aggregate, use the room’s all-sources averaging strategy. When selected aggregates overlap, the room temperature is withheld and the panel explains the conflict. Change climate participation so one measurement represents each physical source; individual device controls remain available.
The thermostat detail lists the freshness of each configured room, floor and window input, including its sample age and allowed age. Missing, stale or incompatible sources remain visible. Runtime updates and reconnects refresh these diagnostics without allowing an older HTTP response to replace newer state.
Battery and radio sensors
Each thermostat input has a maximum sample age. A reading older than that is stale: a stale room temperature stops heating and cooling, a stale window contact counts as unknown and pauses output, and a stale floor reading inhibits heating. The input becomes usable again with its next report.
Battery radio sensors (Zigbee, Bluetooth) save power by reporting rarely: many send a reading only when the value changes, plus a heartbeat every 30–60 minutes. They work with the thermostat when the maximum age is a little longer than their reporting interval. The editor shows how often each selected sensor has been reporting since Smart Panel started. It warns when the maximum age is shorter than the longest gap between reports, and offers a recommended value: the longest gap plus half of it, so one late report does not stop the thermostat.
The same guidance appears wherever a virtual device has a maximum age: aggregate sensors, numeric converters, dew points, and a thermostat member’s floor or cooled-surface probe. Aggregates, converters and dew points start with a maximum age of 60 seconds, which suits wired sensors but not radio ones. When one maximum age covers several sensors, as in an aggregate or a dew point, the advice follows the slowest of them. A stale source is left out of an aggregate, so the aggregate stays available while enough of its sources are fresh, but its value then comes from fewer sensors.
A dew point also needs its temperature and humidity samples to be close in time (the maximum skew, 5 seconds by default). Two separate radio sensors report at unrelated times and would rarely meet that, so take both inputs from one combined temperature and humidity sensor. Most combined sensors send both values in the same report, but some report each value on its own schedule; check that yours sends both within the maximum skew (the dew point editor shows each input’s age, and reports a skew error when they are too far apart), or configure its reporting so it does.
The trade-off is reaction time. With a maximum age of 90 minutes, the thermostat may act on a reading up to 90 minutes old, and it notices a sensor that stopped working only after that time. For a faster response, use a sensor that reports more often, or configure periodic reporting on the device where it supports it. For Zigbee2MQTT devices, see value freshness.
Automatic window detection (without a contact) looks for a fast drop of the room temperature while heating, or a fast rise while cooling. With the recommended settings it needs at least three readings within three minutes, none older than two minutes, so a room temperature reading at least every 90 seconds. The editor shows that requirement and warns when the room sensor usually reports less often. Sensors that report on change speed up while the temperature falls, but a battery radio sensor rarely reports that often. Without enough readings detection cannot start a pause, so it misses open windows but never stops the thermostat by mistake. With a slow room sensor, bind a window contact instead.
Window contacts usually report only when they open or close. They stay usable between changes only if the device also sends heartbeats (most battery contacts do, together with their battery level) and the maximum age covers the heartbeat interval.