TL;DR
A November 11, 2026, Scott’s Blog post documents an effort to reverse engineer a Coway Airmega IconS so it can be controlled without Coway’s cloud service. The report describes the motivation and an initial network-interception setup, but the supplied material does not establish that local control was achieved.
A November 11, 2026, report on Scott’s Blog describes an effort to reverse engineer Coway’s Airmega IconS and control it without relying on the company’s cloud service. The project responds to recurring problems with Coway’s online controls and aims to connect the purifier to Home Assistant and Apple Home locally, but the supplied report excerpt does not confirm that the cloud has been bypassed.
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The author says an existing Home Assistant integration communicates with Coway’s IoCare cloud service: it polls the service for purifier status and sends commands through it. Home Assistant then makes those controls available through Apple Home, including the author’s “Good Night” routine, which turns off lights and raises the purifier fan for white noise. The setup is convenient, but still depends on Coway’s servers.
According to the author, that dependency has caused repeated disruptions. The report lists Coway blocking the integration at one point, changes to its app and web-page layout breaking the integration, intermittent server outages, and an account ban that took weeks to resolve with customer support. The author also says the IconS is discontinued and worries that the cloud service may eventually be changed or withdrawn; that future possibility is a concern, not a reported Coway decision.
The author says the investigation began with a plan to place a Raspberry Pi between the purifier and the home router. The Pi would act as a Wi-Fi access point, redirect the purifier’s traffic through a proxy, and record communications for analysis. The post describes this as an initial approach and says the device’s certificate checks could make interception difficult. The available excerpt ends during this setup discussion, before reporting any captured protocol details or a working local-control method.
Keeping Purifier Controls at Home
The project highlights a practical consequence of cloud-dependent home devices: a working appliance can lose remote features when a manufacturer’s servers, app, or account policies change. In the author’s household, the cloud connection links a purifier fan routine to daily smart-home use. A local alternative, if achieved, could make that routine less dependent on outside service availability.
It also illustrates the distinction between owning hardware and having durable control over its network features. The report describes disruptions to a community-built integration, not a finding that Coway’s purifier is unsafe or that the company has discontinued support. Its broader relevance is that local control can reduce reliance on a vendor’s infrastructure, while requiring technical work and careful testing of the device’s communications.
Products Worth Considering
Jackery Explorer 1000 v2 Portable Power Station
Logitech MX Keys S Combo Wireless Keyboard and Mouse, Graphite
Jackery Solar Generator 1000 v2 with Two 100W Solar Panels, 1024Wh LiFePO4 Battery
As an affiliate, we earn on qualifying purchases.
From IoCare to Local Control
The author says the older Airmega in the household lacked Wi-Fi, so integrating it with Apple Home was not straightforward. After that device broke, the author bought the Wi-Fi-enabled Airmega IconS, which the post identifies as discontinued. The author names the Airmega 250S and MightyS as other Wi-Fi models, but does not say whether the same reverse-engineering approach works with them.
Coway’s phone app and cloud are not the only route described in the post: a community-maintained Home Assistant integration already bridges Coway’s service to Apple’s smart-home platform. However, because that integration sends commands through IoCare, it inherits the service’s availability and account restrictions. The new project seeks to change that architecture by examining the purifier’s network traffic rather than relying on the cloud integration.
“The device works. It really does improve air quality.”
— Scott’s Blog author
The Interception Test Is Unreported
The supplied excerpt does not say whether the Raspberry Pi setup successfully captured readable traffic, whether the purifier accepts a locally hosted service, or whether the author ultimately achieved control without Coway’s servers. The author frames certificate interception as conditional: success could depend on whether the purifier is unpatched, trusts relevant root certificates, and does not pin the cloud service’s certificate. Those points are presented as possibilities, not established findings about the IconS.
The post also refers to an October 2026 certificate-authority security incident as a possible opening for traffic interception. The supplied material does not provide enough independent evidence to verify the incident’s scope, duration, or effect on this purifier. It likewise does not establish whether Coway plans to end the service, charge for it, or continue supporting the integration.
A Local Protocol Still to Find
The next step in the described project is to inspect traffic between the purifier and its online service, then determine whether commands and status checks can be handled locally. The report excerpt does not give a timetable or state that this work has progressed beyond setting up an interception environment.
Readers looking for a confirmed result should check the full post or any later update from its author. Until a working method is documented, the existing integration remains cloud-dependent as described, and the IconS’s future support status is unresolved.
Key Questions
What is the author trying to change?
The author is investigating whether the Coway Airmega IconS can be controlled locally instead of sending status requests and commands through Coway’s IoCare cloud.
Does the report confirm that cloud-free control works?
No. The supplied excerpt describes a planned Raspberry Pi and proxy setup, but does not report a successful local-control method or show that the purifier has been disconnected from Coway’s service.
Why does the author want local control?
The author says the existing Home Assistant integration has been affected by server outages, changes to Coway’s app or site, and account restrictions. Local control could reduce dependence on those services if the project succeeds.
Is the Airmega IconS the only model discussed?
The IconS is the device under investigation. The author also mentions the Airmega 250S and MightyS as other Wi-Fi-enabled models, but the excerpt does not establish that the same method would work on them.
Source: scottjg.com
