AcuRite delays AcuRite NOW rollout, pushing back My AcuRite shutdown after app “falls short”

If you own an AcuRite weather station, rain gauge, or indoor thermometer, you were supposed to lose My AcuRite by the end of May and move to AcuRite NOW. That handoff was originally set for May 30, but AcuRite now says the new app is not ready, and the transition needs more time. “Has raised serious questions and concerns among many long-time users,” VP of product development Jeff Bovee told Ars Technica, in explaining why the change is delayed.

To be clear on the stakes: AcuRite’s devices were built to stream readings via companion software, and the companion software is the interface between your hardware and everything you do with its data. The company had told customers that My AcuRite would shut down at the end of May, and that device owners would instead use AcuRite NOW, an iOS and Android app launched in June 2025, to control their gadgets. The delay is basically an admission that the “new controls everything” story is not currently true for many users, at least not without tradeoffs.

When Ars first reported the situation in May, AcuRite NOW lacked several capabilities that existed in My AcuRite. That list matters because it is not about aesthetics. Users could not do things like rename multiple temperature sensors, report temperatures in non-integers, or use an online dashboard option. Each item is a small daily friction that becomes a bigger trust problem when you have been using the same workflow for a long time and the new app does not match it.

There is also the data pipeline angle, which is where “companion app” quietly stops being a consumer convenience and starts becoming operational infrastructure. Users highlighted problems uploading data to weather sites, which means the readings from the physical devices may not land where people want them, when they want them. For weather enthusiasts and hobbyists who feed external sites or track trends across platforms, upload reliability can be as important as whether the app loads.

Then there is the layout complaint, described by users as “a poor layout with wasted space.” That kind of feedback often sounds subjective, but it connects to a practical reality: weather stations and sensors produce many signals. If the interface requires extra taps or hides key fields, you will feel it every time you check conditions. And if AcuRite is asking users to adopt a new interface while also missing power-user features like sensor renaming and non-integer temperature reporting, the overall experience becomes harder to defend.

Why the delay now? The Ars Technica account frames it as the company acknowledging that the May 30 transition plan has “raised serious questions and concerns among many long-time users.” This is the sort of moment where a board or leadership team has to decide whether to double down on migration timelines or treat the product as not meeting the bar yet. For AcuRite, the cost of the delay is straightforward: keeping My AcuRite alive longer, supporting more legacy complexity, and taking another round of feedback. The cost of not delaying is also straightforward, but harder to quantify: user trust erosion and churn risk, especially among long-time customers who “worked fine” with the old software, even if they were not asking for change.

There is also a broader industry incentive underneath all of this. IoT and smart device ecosystems typically rely on companion apps and backend services. When those apps change or shut down, customers do not just switch UI preferences. They lose functionality, historical continuity, and sometimes data export paths. Regulators are rarely in the day-to-day details for consumer weather gadgets, but the pattern is increasingly relevant to governance conversations around data portability, consumer protection, and product continuity. Even without a specific regulatory trigger in this story, the second-order implication is that delayed migrations can become a reputational issue that regulators, consumer advocates, and lawmakers notice over time when users feel locked in.

For executives at device and platform companies, this is a reminder that app migrations are not “version upgrades.” They are deprecations in disguise. When AcuRite originally set a shutdown date for My AcuRite and told customers to use AcuRite NOW for control, it created a hard deadline. Once users report missing features and upload problems, that deadline turns into an operational and brand decision. AcuRite has chosen to extend the runway by delaying plans to force the switch, and the message to peers is blunt: the transition must meet core feature expectations, or the migration becomes a fight with the people already paying for the hardware.