Symptoms
An added wireless room sensor reports temperature but the thermostat still controls from its wall sensor. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: An added wireless room sensor reports temperature but the thermostat still controls from its wall sensor.
- Control test: Compare the app's active sensing source at different schedule periods.
- A confirmed correction must meet this outcome: The controller explicitly names the desired active sensor during the test period.
Write down the exact sequence that reproduces the failure and the moment it stops. Intermittent failures are easiest to isolate when the same short test is repeated before and after one change.
Why It Happens
Cloud commands and local temperature control are separate functions. Heating or cooling equipment can appear online without a valid physical demand, and safety interlocks must take priority over an app setting.
The important distinction is whether sensor not assigned to comfort profile or unsupported sensor averaging explains the observed difference. Schedule uses wall thermostat remains another plausible explanation until the comparison rules it out.
Three competing explanations
- Sensor not assigned to comfort profile.
- Unsupported sensor averaging.
- Schedule uses wall thermostat.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports sensor not assigned to comfort profile does not automatically exclude unsupported sensor averaging; the comparison needs to separate them.
Before Making Changes
Preserve normal heating or cooling safeguards. Leave electrical panels, refrigeration components and combustion systems to qualified technicians. Never rely on an unsupported sensor for freeze protection.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare the app's active sensing source at different schedule periods. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Sensor not assigned to comfort profile | If the failing state changes under the comparison, sensor not assigned to comfort profile is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Unsupported sensor averaging | If the first change has no effect but a supported configuration differs, unsupported sensor averaging moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Schedule uses wall thermostat | If both earlier paths are contradicted, investigate whether schedule uses wall thermostat accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Assign the room sensor to one test schedule period if supported. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Capture the current behavior
An added wireless room sensor reports temperature but the thermostat still controls from its wall sensor. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare the app's active sensing source at different schedule periods. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Correct the supported setting
Assign the room sensor to one test schedule period if supported. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
The controller explicitly names the desired active sensor during the test period. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for sensor not assigned to comfort profile, unsupported sensor averaging and schedule uses wall thermostat separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Review event-level evidence
Inspect sensor selection rules and group membership across occupancy modes. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Isolate a second independent variable
Revisit the comparison: Compare the app's active sensing source at different schedule periods. If the first suspected cause is not supported, compare the behavior predicted by unsupported sensor averaging with the behavior predicted by schedule uses wall thermostat. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: The controller explicitly names the desired active sensor during the test period. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the HVAC manufacturer or a licensed heating and cooling technician. Safety boundary: Never rely on an unsupported sensor for freeze protection.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming sensor not assigned to comfort profile is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare the app's active sensing source at different schedule periods.
- Skipping this safety boundary: Never rely on an unsupported sensor for freeze protection.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: The controller explicitly names the desired active sensor during the test period. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare the app's active sensing source at different schedule periods.
- Check the stated pass result: The controller explicitly names the desired active sensor during the test period.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Inspect sensor selection rules and group membership across occupancy modes. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the HVAC manufacturer or a licensed heating and cooling technician, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether sensor not assigned to comfort profile, unsupported sensor averaging and schedule uses wall thermostat were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: The controller explicitly names the desired active sensor during the test period. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: An added wireless room sensor reports temperature but the thermostat still controls from its wall sensor. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
FAQ
How can I tell whether sensor not assigned to comfort profile is responsible?
Run the controlled comparison: Compare the app's active sensing source at different schedule periods. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is unsupported sensor averaging rather than sensor not assigned to comfort profile?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Inspect sensor selection rules and group membership across occupancy modes. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: The controller explicitly names the desired active sensor during the test period. If it fails after the normal workflow is repeated, document whether schedule uses wall thermostat still explains the remaining behavior and escalate with non-sensitive observations.