Models: Tapo P110 & H110 Smart IR & IoT Hub

Hardware Version P110 & H110: 1.0

Firmware Version P110: 1.4.0 Build 251020 Rel.161559

Firmware Version H110: 1.4.4 Build 251031 Rel.111523

App Version (Android): 3.17.109

App Version (iOS): 3.17.105

Platforms tested: iPadOS, Android, Bluestacks

Networks tested: multiple routers and Wi‑Fi environments

Summary

When the internet connection is unavailable, the Tapo app does not generate any local log entries for smart plug toggles, IR commands, button presses, or local automations. This behaviour affects both smart plugs and IR devices, indicating that the issue is not device‑specific but related to how the Tapo ecosystem handles offline events. Once the internet returns, the history shows a complete gap for the entire offline period.

Steps to Reproduce

1. Disconnect the internet (router WAN unplugged).
2. Keep the hub and smart devices powered and connected to the LAN.
3. Perform any of the following actions:
   • Toggle a smart plug
   • Send an IR command
   • Trigger a smart button
   • Run a local automation
4. Reconnect the internet.
5. Check:
   • Global history
   • Automation history
   • Device history

Observed Behaviour

• No log entries are created during the offline period.
• Smart plug toggles do not appear in any history.
• Manual IR commands do not appear in any history.
• Button presses do not appear in any history.
• Local automations do not appear in any history.
• When internet returns, the history shows a complete gap.
• Only cloud‑generated entries (e.g., failed schedules) appear after reconnection.

Expected Behaviour

• Local actions should generate local logs, even when the cloud is unreachable.
• The hub should store offline events and sync them when internet returns.
• Users should be able to review what happened during an outage.
• Logging behaviour should be consistent across device types.

Impact

• Users cannot diagnose issues during outages.
• Smart plug actions cannot be verified.
• Heating/cooling IR actions cannot be verified.
• Button presses and local automations leave no trace.
• Offline periods become completely invisible.
• Troubleshooting becomes impossible without cloud connectivity.

Request

Could the engineering team please confirm whether the absence of local logging is intentional?

If not, is offline logging planned for future updates?

Thank you for your attention,

Best Regards,

John