Model: H110 Smart IR & IoT Hub

Firmware: 1.4.4 Build 251031 Rel.111523

App Version (Android): 3.17.109

App Version (iOS): 3.17.105

Summary

IR schedules created for devices controlled through the Tapo H110 Hub do not run when the internet is unavailable. This affects air conditioners, heaters, and any IR‑controlled device. The behaviour is fully reproducible and appears to be a design limitation rather than a bug.

Steps to reproduce

1. Create an IR automation (e.g., “Turn On Air Conditioner at 12:50”).
2. Confirm the automation works normally when online.
3. Disconnect the internet 5 minutes before the scheduled time.
4. Close the Tapo app on all devices.
5. Wait for the scheduled time.
6. Reopen the Tapo app after the schedule has passed.

Observed behaviour

• The IR device does not turn on at the scheduled time.
• No IR command is sent by the H110 Hub.
• The automation does not run locally.
• The failure is not logged in the global history or automation history.
• The iPad app shows “Local Only” when opening the IR device.
• The Android app shows no indication that the device is in local‑only mode.
• The “Next Event” banner on the dashboard does not show IR schedules at all (only smart plug schedules).
• Smart plugs and Sub‑GHz sensors/buttons continue to work offline, confirming the hub itself is operational.

Important note from official product documentation

The H110 marketing material explicitly states:

“Offline Control – Even if the external network disconnects, the hub remains controllable via the Tapo app as long as your smartphone and hub are on the same LAN.”

This creates a clear expectation that all hub‑managed functions, including IR schedules, should continue to operate offline. There is no disclaimer indicating that IR schedules require cloud connectivity or that offline mode limits IR automation.

This makes the current behaviour inconsistent with the product’s advertised capabilities.

Expected behaviour

• IR schedules should run locally when the internet is unavailable, just like smart plug schedules and Sub‑GHz button‑triggered actions.
• If a schedule cannot run, the failure should be logged and visible to the user.
• The app should clearly indicate offline mode on all platforms.
• The “Next Event” banner should include all upcoming automations, including IR.

Impact

This behaviour affects:

• heating
• cooling
• ventilation
• dehumidifiers
• fans
• any IR‑controlled device

If the internet drops (or the router reboots at night), scheduled climate control fails silently, which can lead to:

• rooms not heating
• rooms not cooling
• humidity issues
• safety concerns for vulnerable users
• unpredictable behaviour

This is especially problematic because:

• smart plugs run offline
• Sub‑GHz button automations run offline
• IR devices do not run offline, creating inconsistent behaviour across the ecosystem

Additional notes

• The behaviour is reproducible across iPadOS, Android, and Bluestacks.
• The iPad app shows “Local Only,” but Android does not.
• The automation engine appears to be cloud‑dependent for IR actions.
• When the hub already knows it is offline, the automation engine does not attempt to run the IR schedule, resulting in silent failures.

Request

Please confirm whether the current behaviour is intentional. If IR schedules are cloud‑dependent by design, this contradicts the product documentation and creates a major reliability gap compared to smart plugs and Sub‑GHz button automations.

Local execution of IR schedules would greatly improve safety, predictability, and user trust.

Thank you for your attention.

Best regards,

John