Microsoft’s early vision of Cortana as an ambient, everywhere assistant found one of its most stylish physical expressions in GLAS — a translucent-OLED thermostat built by Johnson Controls and powered by Windows 10 IoT Core — but the product’s life cycle and evolution also tell a cautionary tale about platform bets, voice-assistant politics, and the real-world demands of connected-device customers. m]
When Johnson Controls unveiled GLAS at CES 2018 it leaned on two long-standing strengths: hardware design rooted in 135 years of building-control experience, and a new partnership with Microsoft that promised to make a thermostat more than a temperature dial. The device combined a translucent 5.9-inch OLED touchscreen, multiple environmental sensors, and voice interaction through Microsoft’s Cortana, running atop Windows 10 IoT Core with connectivity and analytics routed through Microsoft Azure. Johnson Controls positioned GLAS as a hybrid: a polished consumer-facing device with bona fide enterprise-grade backend plumbing.
That combination made sense on paper. Heating, ventilation and air conditioning (HVAC) remain the single largest energy expense for homes and commercial buildings, and a thermostat that can blend occupancy detection, air-quality telemetry and cloud-based analytics seems a compelling energy- and health-focused proposition. GLAS promised to report humidity, total volatile organic compounds (tVOC), equivalent CO2 (eCO2), and—when online—external air quality indices and pollen/UV information, while offering “smart” setback and pre-start controls to reduce run time and cost. Johnson Controls also emphasized that GLAS would stay up to date via Azure-delivered updates and remote management.
The feature list was explicitly broader than “just HVAC”:
Yet the product’s software behavior and platform dependencies created problems in practice. Early hands-on reviews described Cortana’s voice interactions on GLAS as capable but uneven, constrained by Cortana’s lower market adoption relative to Alexa and Google Assistant. More pragmatically, GLAS initially depended heavily on cloud services for some features, and that dependency raised questions about long-term feature stability and vendor support—questions that would later prove prescient.
Within a few years the device’s Cortana functionality itself was deactivated. Reports and company communications confirmed that Johnson Controls issued a firmware update that removed Cortana voice services from GLAS, leaving Alexa and Google Assistant as the voice-control options for many owners. Observers framed the removal as part of a larger retrenchment of Cortana from consumer-facing voice dominance toward a more enterprise-focused Microsoft strategy; Johnson Controls’ move underscored the market reality that consumer voice choice is driven by usage and ecosystem momentum.
This mid-course correction holds an important lesson: hardware that bakes in a single assistant risks becoming brittle if that assistant loses consumer traction or if vendor priorities change.
However, the GLAS story also exposes the operational vulnerabilities of connected devices:
Why the strategy faltered, at least in the GLAS case, has several dimensions:
GLAS taught a simple but important lesson for the modern connected home: the experience you sell at launch must be sustainable across the device’s lifetime. That means picking voice and cloud partners with long-term viability, providing robust local fallbacks, and committing to a realistic support lifecycle. For homeowners and building managers alike, the GLAS story is now part design case study, part cautionary tale—and a reminder that in IoT, aesthetics and ambition must be matched by operational endurance.
Source: Mashable Microsoft puts Cortana and Windows 10 in a new smart thermostat
When Johnson Controls unveiled GLAS at CES 2018 it leaned on two long-standing strengths: hardware design rooted in 135 years of building-control experience, and a new partnership with Microsoft that promised to make a thermostat more than a temperature dial. The device combined a translucent 5.9-inch OLED touchscreen, multiple environmental sensors, and voice interaction through Microsoft’s Cortana, running atop Windows 10 IoT Core with connectivity and analytics routed through Microsoft Azure. Johnson Controls positioned GLAS as a hybrid: a polished consumer-facing device with bona fide enterprise-grade backend plumbing.That combination made sense on paper. Heating, ventilation and air conditioning (HVAC) remain the single largest energy expense for homes and commercial buildings, and a thermostat that can blend occupancy detection, air-quality telemetry and cloud-based analytics seems a compelling energy- and health-focused proposition. GLAS promised to report humidity, total volatile organic compounds (tVOC), equivalent CO2 (eCO2), and—when online—external air quality indices and pollen/UV information, while offering “smart” setback and pre-start controls to reduce run time and cost. Johnson Controls also emphasized that GLAS would stay up to date via Azure-delivered updates and remote management.
Technical anatomy: what GLAS actually shipped with
The hardware
- Display: GLAS was built around a translucent OLED touchscreen (5.9 inches in Johnson Controls’ specs), chosen to deliver a high-end, “art object” look that would visually recede when idle and present a vibrant surface when active. The translucent effect was one of the thermostat’s most distinctive design cues.
- Sensors: The thermostat package included ambient temperature, humidity, a motion sensor for occupancy detection, and air-quality sensors for tVOC and eCO2. When connected, GLAS could augment its on-site sensing with external environmental data—pollen, AQI, UV index—pulled from cloud sources to provide a fuller picture of indoor/outdoor conditions.
- Connectivity and security: Johnson Controls built GLAS on Windows 10 IoT Core, relying on Azure IoT services for device management and analytics. Early briefings and technical notes highlighted BitLocker encryption for data at rest in Azure and a device-management pipeline via Azure IoT Hub, signaling a focus on secure update and telemetry channels.
The software and voice stack
- Operating system: GLAS ran a tailored Windows 10 IoT Core image, with a custom UWP-like interface for the thermostat. That choice enabled the use of Microsoft’s Cortana skills and Azure services out of the box, while promising a familiar developer model for OEMs who adopt Windows IoT.
- Voice assistant: At launch GLAS shipped with Cortana built into the device, enabling voice adjustments (“Hey Cortana, set the temperature to 68 degrees”), calendar and productivity integration, and natural-language queries surfaced on the thermostat itself. The Cortana integration was one of the headline differentiators compared with legacy thermostats and other smart-home products.
- Cloud services: Azure was presented as more than just a connectivity route: Johnson Controls promoted Azure IoT as the foundation for data collection, analytics and enterprise integration—useful for commercial deployments where fleet-level device management matters. The pitch framed GLAS as the consumer face of a broader building-automation strategy.
The positioning: a high-end challenger in a crowded category
GLAS entered a market already set by Nest, Ecobee and a raft of commodity programmable thermostats. Johnson Controls’ play was clear: compete on industrial design and on telemetry depth, lean on Microsoft for a unique voice capability, and position GLAS as a premium $319 thermostat with enterprise-friendly back-end services. That price put GLAS squarely against higher-end smart thermostats rather than budget options. Johnson Controls also guarded a corporate credibility edge—the company literally invented the electric room thermostat—trying to convert that history into modern smart-home relevance.The feature list was explicitly broader than “just HVAC”:
- Environmental monitoring and indoor-air insights (tVOC, eCO2, humidity).
- Occupancy-aware scheduling and automation.
- A full touchscreen UI for glanceable data beyond temperature.
- Voice control and productivity integration via Cortana (calendar, traffic, briefings).
- Azure-enabled device management and potential integration with building management systems for commercial customers.
Early reception: design applause, product caveats
GLAS earned early design honors—an Innovation Awards honoree recognition at CES 2018—but reviewers and early adopters flagged a mix of charm and friction. The translucent OLED and polished surface consistently received praise: reviewers called the aesthetic “gorgeous” and “museum-grade,” and many buyers said it upgraded the look of a thermostat niche that had been painfully utilitarian for years.Yet the product’s software behavior and platform dependencies created problems in practice. Early hands-on reviews described Cortana’s voice interactions on GLAS as capable but uneven, constrained by Cortana’s lower market adoption relative to Alexa and Google Assistant. More pragmatically, GLAS initially depended heavily on cloud services for some features, and that dependency raised questions about long-term feature stability and vendor support—questions that would later prove prescient.
The pivot: adding Alexa and Google Assistant, later removing Cortana
One of the most instructive parts of the GLAS story is how voice support evolved. Despite launching with Cortana prominence, Johnson Controls later added support for Amazon Alexa and Google Assistant, acknowledging which assistants had critical mass in the smart-home ecosystem. By mid-2018 the company was supporting multiple assistants so that GLAS owners could choose their preferred voice ecosystem while still using the device’s built-in Cortana features for GLAS-specific controls. VentureBeat and other outlets covered the shift as GLAS moved toward multi-assistant support to broaden appeal.Within a few years the device’s Cortana functionality itself was deactivated. Reports and company communications confirmed that Johnson Controls issued a firmware update that removed Cortana voice services from GLAS, leaving Alexa and Google Assistant as the voice-control options for many owners. Observers framed the removal as part of a larger retrenchment of Cortana from consumer-facing voice dominance toward a more enterprise-focused Microsoft strategy; Johnson Controls’ move underscored the market reality that consumer voice choice is driven by usage and ecosystem momentum.
This mid-course correction holds an important lesson: hardware that bakes in a single assistant risks becoming brittle if that assistant loses consumer traction or if vendor priorities change.
Security, privacy and update resilience: strengths and unanswered questions
Johnson Controls and Microsoft emphasized secure design and enterprise-grade update pipelines. Azure IoT Hub and BitLocker encryption were cited as parts of the stack to protect telemetry and stored data; Azure’s device-management capabilities also promised long-term patching and fleet control for commercial customers. These are real strengths when implemented and maintained: enterprise device management reduces fragmentation and improves visibility into security posture across many deployed units.However, the GLAS story also exposes the operational vulnerabilities of connected devices:
- Feature-dependence on cloud services: Several GLAS features relied on cloud connectivity for enriched air-quality data, push updates, and remote app control. If cloud services are altered, deprecated, or discontinued, those features can atrophy—even if the on-device functions continue. That risk matters more for devices priced as premium, long-life home fixtures than it does for throwaway peripherals.
- Voice and microphone lifecycle: With Cortana removed, the microphone and voice stack lost utility. A microphone and speaker that no longer connect to the originally advertised assistant raise questions about telemetry collection (is the mic still active?), transparency to users, and whether the device’s update path intentionally renders hardware features stale. Industry coverage noted owner frustration when mic/speaker functionality became obsolete following the Cortana deprecation.
- Support lifecycle and discontinuation: Johnson Controls eventually discontinued the GLAS thermostat as a product and halted feature updates for the companion app, while committing to continue limited customer support and warranty coverage. Product discontinuation is a reality of consumer IoT: manufacturers may cease active development, leaving devices functionally frozen. For homeowners who expect a thermostat to last a decade, the economics of replacement and the moral hazard of embedded obsolescence loom large.
Business and platform implications: why Microsoft’s IoT gamble mattered (and ultimately under-delivered)
From Microsoft’s perspective, GLAS was a hairline crack in a wider strategy: make Windows and Azure the substrate of the intelligent edge. A thermostat that runs Windows 10 IoT Core and sits on Azure feeds product and platform narratives simultaneously—an elegant proof-point for Microsoft. For Johnson Controls, the partnership promised a shortcut to modernized features and to enterprise-grade device management. The early messaging explicitly courted building and enterprise customers as much as homeowners.Why the strategy faltered, at least in the GLAS case, has several dimensions:
- Ecosystem gravity: Amazon and Google won the voice battle in consumer smart homes. Cortana’s lower adoption (and Microsoft’s subsequent refocusing of Cortana strategy) reduced the value of having Cortana on the device. Smart-home buyers gravitated toward assistants that already controlled lights, speakers and third-party integrations at scale. Johnson Controls’ later addition of Alexa and Google Assistant was an admission that platform choice matters.
- Product longevity vs. cloud dependence: A thermostat is a long-lived appliance. Consumers expect a multi-year lifecycle. When vendors tether features tightly to a cloud or to a single assistant, they create single points of failure that can erode the value proposition over time. GLAS’s discontinuation and Cortana removal amplified this risk.
- Time-to-market and product maturity: GLAS received praise for design but also criticism for execution. Long delays between unveiling and widely available firmware-stable releases frustrated buyers; early reviews called certain software behaviors inconsistent. Those problems make an elegant hardware offering less defensible in the face of more mature players.
Consumer guide: what GLAS owners and prospective buyers should know
If you own a GLAS thermostat, or are considering whether to buy a premium connected thermostat in 2026 or beyond, here are practical takeaways:- Check current support status: The device was discontinued and app feature updates ceased; Johnson Controls has published a discontinuation notice and continues limited customer support and warranty coverage. Owners should consult the manufacturer’s discontinuation statement and support channels for specifics.
- Voice functionality may change: GLAS removed Cortana in a software update; voice control options shifted toward Alexa and Google Assistant for many owners. If you rely on a particular voice assistant’s integrations (calendar, email, productivity), verify whether the device still supports that assistant and how the assistant’s features map to GLAS-specific controls.
- Don’t assume perpetual feature parity: Features dependent on cloud services—enriched outdoor AQI feeds, remote API calls, or push-notification-based automations—may degrade or disappear if the supporting cloud services are changed. Back up expectations: treat connected thermostats as devices with a finite feature lifetime unless the vendor commits to long-term support.
- Consider local-control alternatives: If longevity and privacy are priorities, evaluate thermostats that offer robust local-control modes or better third-party integration (e.g., community-supported APIs or Home Assistant integrations). Some homeowners prioritize local automation and open APIs over flashy displays and voice assistants. Community forums and open-source projects can extend functionality for motivated users, but require technical investment.
Critical analysis: what GLAS did well — and where it missed the mark
Notable strengths
- Industrial design and user interface: GLAS raised consumer expectations for what a thermostat could look like. The translucent OLED and minimal hardware aesthetic forced the industry to reckon with design as an important differentiator in smart-home peripherals. Many reviewers praised the visual identity and the elegant UI approach.
- Sensor suite and environmental focus: By focusing on indoor-air metrics (tVOC, eCO2) as well as traditional HVAC control, GLAS pushed the thermostat conversation from comfort to health. This shift matters as indoor air quality gains public attention. Johnson Controls’ building-automation background gave GLAS credibility on sensor fidelity and value for air-quality-driven ventilation.
- Enterprise-ready backend: Leveraging Azure IoT Hub and enterprise device management was a logical advantage for Johnson Controls; for commercial deployments where fleet management matters, GLAS’s cloud-first architecture was a competitive differentiator.
Key risks and missed opportunities
- Platform lock-in to a weak consumer assistant: Shipping prominently with Cortana exposed GLAS to the assistant’s market weaknesses. When the assistant lost consumer traction and Microsoft refocused Cortana, GLAS owners faced degraded capabilities. Multi-assistant support should have been a day-one priority.
- Expectation vs. operational reality: The initial marketing emphasized “always connected” telemetry and dynamic control; real-world deployments revealed that connectivity, update cadence, and feature readiness varied, leaving early buyers to cope with software rough edges. A device mounted to the wall invites long-term expectations and, when those are not met, buyer disappointment is amplified.
- Lifecycle communication and deprecation: The discontinuation and decision to limit app updates illustrates a thorny IoT issue: manufacturers must clearly communicate support lifecycles for installed, expensive, in-wall devices. GLAS’s lifecycle decision left some users feeling the warranty and device-value calculus had changed after purchase. A clearer, longer-term support commitment could have softened that blow.
Broader lessons for vendors and consumers in smart-home hardware
- Vendors should anticipate and plan for ecosystem flux. Voice platforms evolve rapidly; tying core features to the fortunes of a single assistant creates strategic fragility. Multi-assistant strategies and well-documented local-control fallbacks are pragmatic hedges.
- Design matters, but design alone does not sell longevity. Beautiful hardware must be matched by rigorous software QA, predictable update cadence, and honest lifecycle agreements. Consumers treat in-wall devices as long-term infrastructure—vendor commitments should reflect that.
- Enterprise-grade backends (Azure, AWS IoT, etc.) confer real benefits for fleet management, telemetry and updates. But vendors must match technical capability with sustained commercial commitment; cloud dependencies are two-way contracts, not just feature toggles.
- Finally, privacy and transparency should be non-negotiable. Mic and telemetric sensors must be accompanied by clear user controls and lifecycle promises. When a voice assistant is removed, vendors owe clarity about whether on-device hardware remains active and how data is handled.
Conclusion: GLAS as a design success with a cautionary aftertaste
GLAS was an ambitious product: a beautiful, sensor-rich thermostat that attempted to combine Johnson Controls’ deep building-automation pedigree with Microsoft’s cloud and voice-platform muscle. For a moment, it looked like a credible third path between commodity thermostats and a purely consumer-focused Nest-like approach. But design and early feature promise cannot insulate a hardware product from platform momentum, ecosystem choices and vendor support realities.GLAS taught a simple but important lesson for the modern connected home: the experience you sell at launch must be sustainable across the device’s lifetime. That means picking voice and cloud partners with long-term viability, providing robust local fallbacks, and committing to a realistic support lifecycle. For homeowners and building managers alike, the GLAS story is now part design case study, part cautionary tale—and a reminder that in IoT, aesthetics and ambition must be matched by operational endurance.
Source: Mashable Microsoft puts Cortana and Windows 10 in a new smart thermostat