Jump to content

Talk:Airzone Cloud moves to a subscription-based model

Add topic
From Consumer Rights Wiki

Sourcing improvements and factual corrections

[edit source]

I'm an Airzone customer directly affected by this change and an HVAC installer working with Airzone systems professionally. I have several elements that may help address the sourcing concerns flagged on this article, and I'd like to propose changes before editing directly.

Elements I can contribute with verifiable sources:

  1. The original Airzone announcement newsletter, archived on the Wayback Machine on May 29, 2026 (the day after the announcement): https://web.archive.org/web/20260529164019/https://confort.airzonecontrol.com/airzone-cloud-fr-systemes1 The article currently dates the announcement to "early 2026" — it was actually May 28, 2026, with the paywall taking effect October 2026 (6-month free trial for existing users).
  2. A precision on the scope of the change: based on the official announcement, remote visualization remains free without subscription. Only remote control (sending commands) moves behind the paywall. The article currently states users "lose all remote access", which is imprecise.
  3. Information from Airzone France technical support confirming that the current Airzone Webserver model does not support the local API documented in Airzone's integration manual, and that a separate hardware product (AZX6WSPHUB, approximately €300) is required to obtain local API access independent of Airzone Cloud.

Elements I would prefer not to touch:

The Lawsuit section, including claims of action by FACUA and OCU. I have no independent source confirming these specific organizations are involved, but I don't want to remove content others have contributed without input from editors more familiar with the Spanish consumer protection landscape.

Would adding the elements above, with proper inline references, be an appropriate way to address the Incomplete flag ? Should I proceed with edits, or would you prefer I draft changes here first? Thanks. Matthias (talk) 13:26, 3 June 2026 (UTC)Reply

Hi Matthias,
We're absolutely happy for you to make those changes. In addition, if you see elements in the article that are unsourced and don't pass the sniff test, please feel free to delete them. If the original author, or another editor, feels streongly that that information should be included, they can always come back and re-add it with an appropriate source. Incomplete notices are often added by moderators or users who identify that there are substantial issues with an article and to notify readers that they should be careful about accepting it at face value, but who do not have the time or inclination to do the research themselves to research and fix the article, so something being retained in an article should not be seen as an endorsement of it by other editors.
As an aside, I've also confirmed your account, so you shouldn't have to deal with any more captchas! Thank you very much for getting involved. Keith (talk) 13:34, 3 June 2026 (UTC)Reply
@Keith Sorry for the very late reply: I completely missed your answer (I never got a notification for it) and only saw it today. Thank you for the welcome and for confirming my account.
I have now rewritten the article with sources: the exact dates (announcement on 28 May 2026, launch on 28 October 2026), what stays free and what needs the subscription (remote viewing stays free, remote control does not), the Home Assistant 402 errors and the local API question, and a sourced consumer response section. I removed the claims I could not source: the FACUA/OCU lawsuit (OCU only hosts user complaints, and I found no lawsuit or official position) and the HomeKit integration. I left the Incomplete and SloppyAI notices for a moderator to judge. Feedback welcome. Matthias (talk) 10:39, 15 November 2026 (UTC)Reply

Open-source local alternative for Airzone Cloud Webserver owners (COI disclosure)

[edit source]

Conflict of interest: I am the author of the project mentioned below, so I am proposing it here instead of editing the article myself. Other editors can decide whether it belongs.

The "Airzone Cloud paywall transition" section mentions users looking for workarounds such as local Home Assistant integrations. One such workaround now exists for owners of the Airzone Cloud Webserver (for example AZX6WSC5GER), who cannot use Airzone's own Local API from that device (its port 3000 is closed in our tests):

  • Open Airzone Gateway (MIT licence, not affiliated with Airzone) replaces the Cloud Webserver with an ESP32 board (about €30-40 of hardware) on the installation's RS-485 bus, and gives local control of every zone in Home Assistant, with no account and no subscription.
  • It shows that the functions moved behind the subscription (remote on/off and setpoints through Home Assistant, history, automations) do not technically need Airzone's cloud.
  • Limits, to be fair: it is a community project, verified on one installation so far, and support is best effort.

Possible addition to the "Consumer response" section, if editors agree: "Some users replaced the Cloud Webserver with an open-source local gateway, Open Airzone Gateway, which controls the installation from Home Assistant without the Airzone cloud."

Matthias (talk) 10:38, 15 November 2026 (UTC)Reply