# IntesisHome 1.1.3: incorrect status across five AC units and temporary server restriction

**URL:** <https://community.homey.app/t/intesishome-1-1-3-incorrect-status-across-five-ac-units-and-temporary-server-restriction/162382>\
**Category:** Questions & Help\
**Tags:** homey-pro-2023\
**Created:** [November 17, 2026, 8:54pm UTC](https://community.homey.app/t/intesishome-1-1-3-incorrect-status-across-five-ac-units-and-temporary-server-restriction/162382 "2026-11-17T20:54:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cornell\_Jaspers](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cornell_jaspers/32/183757_2.png) [@Cornell\_Jaspers](https://community.homey.app/u/Cornell_Jaspers)\
**Post date:** [November 17, 2026, 8:54pm UTC](https://community.homey.app/t/intesishome-1-1-3-incorrect-status-across-five-ac-units-and-temporary-server-restriction/162382/1 "2026-11-17T20:54:49Z")

</div>

Hi all,

I would like to report two issues observed while using **IntesisHome test version 1.1.3** with five air conditioners.

**Setup**

- Homey Pro (Early 2023).
- IntesisHome by Mattias Holm, app ID: com.mattiasholm.intesishome.
- Five separate air conditioners under one AC Cloud Control account, added as five separate devices in Homey.
- Exact Intesis adapter/module model: still to be confirmed.

**1. Adding devices and incorrect status updates**

With version 1.1.2, I could add only one air conditioner. Adding a second produced “Duplicate Device Data”.

After installing test version 1.1.3 on Saturday, 14 November, I could add all five. However, their individual statuses were incorrect.

For example, the living room unit was already running. When I switched on only the master bedroom unit, Homey eventually displayed all five units as on, although only the living room and master bedroom were actually running.

When I switched off the master bedroom, its Homey tile changed first. A few seconds later, the other four tiles also changed to off—even though the living room unit remained running.

The official AC Cloud Control app showed the correct individual states. I have not performed a controlled test with fewer devices on version 1.1.3.

**2. Temporary restriction affecting app control over home internet**

Later that Saturday, control through both Homey and the official AC Cloud Control app stopped working. It briefly recovered the following morning after restarting Homey, but I cannot establish whether that restart caused the recovery.

During the subsequent failure:

- The official app could log in and retrieve correct device states and settings over home Wi-Fi.
- Commands from the app did not operate the units over home Wi-Fi.
- The web portal could control the units through the same home internet connection.
- The same iPhone app worked immediately over 5G or through a separate mobile router.
- An iPad showed the same problem over home Wi-Fi.
- The guest Wi-Fi network, using the same fixed internet connection, also failed.

Restarting the phone and network, signing out and back in, changing DNS and temporarily disabling the tested UniFi security features did not resolve it. Disabling the Homey IntesisHome app did not immediately restore operation either.

A packet capture identified traffic from my iPhone to 212.92.41.143:5210. The server returned:

{“command”:“wait”,“data”:{“time\_seconds”:101762}}

Approximately 40 minutes later, another capture showed:

{“command”:“wait”,“data”:{“time\_seconds”:99331}}

The decrease matched the elapsed time, demonstrating that the waiting period was counting down. After the restriction expired on 17 November, the official app worked again over home Wi-Fi.

This establishes a timed server response, but not its trigger or whether the restriction was specifically tied to my public IP.

**Source-code findings**

Reviewing the public source for version 1.1.3 revealed:

- One shared STATUS object, without separating status by air conditioner. This appears consistent with the shared tile behavior.
- A TCP connection opened during each device’s initialization, while the shared gclient reference is overwritten without explicitly closing the previous connection.
- No specific handling of a server wait response.
- The default 10-second timer updates Homey from the shared in-memory status; it does not itself make a cloud request.

I pressed the controls repeatedly during testing because the displayed states were not updating correctly. I cannot determine whether those commands, multiple connections, or something else triggered the server restriction. The status issue and restriction should therefore be treated as separate observations.

**Request**

Could a maintainer or community developer investigate the per-device status handling, connection management and handling of server-imposed waiting periods?

Is there a maintained version or proposed fix available? I would be happy to help test a corrected build with my five units.

For now, I have disabled IntesisHome in Homey and restored the direct AC Cloud Control integration with Google Home.

Test version:

> **[IntesisHome | Homey](https://homey.app/en-us/app/com.mattiasholm.intesishome/test/)**
>
> Take control of Intesis AC Cloud Control

Source:

> **[GitHub - mattias-holm/com.mattiasholm.intesishome: Homey app for controlling AC Cloud Control...](https://github.com/mattias-holm/com.mattiasholm.intesishome)**
>
> Homey app for controlling AC Cloud Control (previously IntesisHome) devices

Existing discussion:

> [@\[APP\]\[PRO\] IntesisHome](https://community.homey.app/t/app-pro-intesishome/105508):
>
> Thread for the IntesisHome app, [IntesisHome App for Homey | Homey](https://homey.app/en-us/app/com.mattiasholm.intesishome/IntesisHome/)

Kind regards,  
Cornell Jaspers
