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 automations created through the Tapo H110 Hub show inconsistent logging behaviour when they fail.

Sometimes a failed IR schedule appears in the global history as “Failed,” and other times the failure is not logged at all, even though the IR action did not run.

This inconsistency makes it impossible for users to trust automation history for heating/cooling devices.

 

Steps to reproduce

1. Create an IR automation (e.g., “Turn On Air Conditioner at 12:50”).
2. Confirm it 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 and check:
   • global history
   • automation history
   • device history

Repeat the test, but this time open the Tapo app before the schedule fires, so the app detects “Local Only” mode in advance.

 

Observed behaviour

Case A — Failure is logged

• The global history shows a clear entry: “Failed: Turn On Air.”
• This happens when the hub has not yet detected that it is offline.
• The automation engine attempts to run the IR command via the cloud → fails → logs the failure.

Case B — Failure is not logged

• No entry appears in global history.
• No entry appears in automation history.
• No entry appears in device history.
• The IR device still shows “Local Only” when opened on iPad.
• The Android app shows no offline indication at all.
• The IR action did not run, but the system remains silent.

 

This happens when the hub already knows it is offline before the schedule fires.

In this state, the automation engine does not attempt to run the IR action → therefore no failure is logged.

 

Expected behaviour

• All failed IR schedules should be logged consistently, regardless of whether the hub detected offline mode before or after the scheduled time.
• Users should always be able to see when a schedule did not run.
• The logging behaviour should be identical across iOS and Android.
• Silent failures should never occur for heating/cooling devices.

 

Impact

This inconsistency creates several problems:

• Users cannot rely on automation history to diagnose issues.
• Heating/cooling schedules may fail without any record.
• The system gives the impression that everything is working when it is not.
• Troubleshooting becomes extremely difficult because failures are invisible.
• The behaviour differs depending on whether the app was opened before the schedule fired.

This is especially concerning for climate‑control use cases where reliability is essential.

 

Additional notes

• The behaviour is reproducible across iPadOS, Android, and Bluestacks.
• iPad shows “Local Only” when offline; Android does not.
• Smart plug schedules always log correctly, even when offline.
• The inconsistent logging affects only IR automations.

 

Request

Please confirm whether this inconsistent logging behaviour is expected.

If IR schedules cannot run offline, the system should still log every failed attempt, regardless of when offline mode was detected.

Consistent logging is essential for reliability, safety, and user trust.

 

Thank you for your attention.

 

Best regards,

 

John