P110/P110M Error Messages Flood Logfile When Unplugged

by ADMIN 55 views

The Problem

If you remove one of these plugs from power, about 4 or 5 error messages are generated per minute. The only TP-Link devices I have are P110 and P110M. It happens with both types, not just one specific device. This issue is particularly frustrating when you have seasonal use for these plugs and store them when not in use. Additionally, turning off most devices at the power point if going away can also trigger this problem.

What Version of Home Assistant Core Has the Issue?

The issue is present in version 2025.4.3 of Home Assistant Core.

What Was the Last Working Version of Home Assistant Core?

The last working version of Home Assistant Core is 2025.3.3, at least I don't think the error was present then.

What Type of Installation Are You Running?

You are running Home Assistant OS.

Integration Causing the Issue

The TP-Link Smart Home integration is causing the issue.

Link to Integration Documentation on Our Website

You can find the documentation for the TP-Link integration on our website at https://www.home-assistant.io/integrations/tplink.

Diagnostics Information

The diagnostics information is available in the following JSON file: config_entry-tplink-01JPEDKT0MKBFJWFAX07KQKVMY.json.

Example YAML Snippet

There is no YAML snippet provided.

Anything in the Logs That Might Be Useful for Us?

Yes, there are several error messages in the logs that might be useful for us. Here are a few examples:

2025-04-25 23:21:22.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 for modules 'Time, AutoOff, DeviceModule, Energy, PowerProtection' after first update: ('Unable to query the device: 192.168.168.1.95: ', TimeoutError())
2025-04-25 23:21:28.713 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_device_time' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:34.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_auto_off_config' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:40.713 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_device_info' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_device_usage' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:52.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_energy_usage' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:58.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_current_power' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:22:09.877 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_emeter_data' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:23.189 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_emeter_vgain_igain' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:36.501 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_protection_power' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:49.813 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_max_power' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:49.813 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.1.95 data: Unable to communicate with the device update: get_device_info not found in {'get_device_time': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_auto_off_config': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_info': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_usage': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_energy_usage': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_current_power': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_emeter_data': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_emeter_vgain_igain': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_protection_power': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_max_power': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>} for device 192.168.1.95

Additional Information

Q: What is the issue with the P110/P110M plugs?

A: The issue is that when you remove one of these plugs from power, about 4 or 5 error messages are generated per minute. This can be frustrating, especially if you have seasonal use for these plugs and store them when not in use.

Q: Which versions of Home Assistant Core are affected?

A: The issue is present in version 2025.4.3 of Home Assistant Core. The last working version of Home Assistant Core is 2025.3.3.

Q: What type of installation are you running?

A: You are running Home Assistant OS.

Q: Which integration is causing the issue?

A: The TP-Link Smart Home integration is causing the issue.

Q: What is the error message in the logs?

A: The error message in the logs is:

2025-04-25 23:21:22.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 for modules 'Time, AutoOff, DeviceModule, Energy, PowerProtection' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:28.713 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_device_time' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:34.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_auto_off_config' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:40.713 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_device_info' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_device_usage' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:52.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_energy_usage' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:21:58.712 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_current_power' after first update: ('Unable to query the device: 192.168.1.95: ', TimeoutError())
2025-04-25 23:22:09.877 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_emeter_data' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:23.189 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_emeter_vgain_igain' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:36.501 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_protection_power' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:49.813 ERROR (MainThread) [kasa.smart.smartdevice] Error querying 192.168.1.95 individually for module query 'get_max_power' after first update: ("Device connection error: 192.168.1.95: Cannot connect to host 192.168.1.95:80 ssl:<ssl.SSLContext object at 0x7f46a9c15a30> [Connect call failed ('192.168.1.95', 80)]", ClientConnectorError(ConnectionKey(host='192.168.1.95', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f46a9c15a30>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(, "Connect call failed ('192.168.1.95', 80)")))
2025-04-25 23:22:49.813 ERROR (MainThread) [homeassistant.components.tplink.coordinator] Error fetching 192.168.1.95 data: Unable to communicate with the device update: get_device_info not found in {'get_device_time': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_auto_off_config': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_info': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_usage': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_energy_usage': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_current_power': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_emeter_data': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_emeter_vgain_igain': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_protection_power': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_max_power': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>} for device 192.168.1.95

Q: How can I fix this issue?

A: Unfortunately, there is no clear solution to this issue yet. However, you can try the following:

  • Check your network connection to ensure that it is stable and not causing any issues.
  • Try restarting your Home Assistant instance to see if it resolves the issue.
  • Check the TP-Link Smart Home integration settings to ensure that they are correct and not causing any conflicts.
  • Consider reaching out to the Home Assistant community or the TP-Link support team for further assistance.

Q: Is this issue specific to the P110/P110M plugs?

A: Yes, this issue is specific to the P110/P110M plugs. However, it is possible that other TP-Link devices may also experience similar issues.

Q: Can I prevent this issue from occurring?

A: Unfortunately, there is no clear way to prevent this issue from occurring. However, you can try the following:

  • Regularly check your network connection to ensure that it is stable and not causing any issues.
  • Regularly restart your Home Assistant instance to ensure that it is running smoothly.
  • Regularly check the TP-Link Smart Home integration settings to ensure that they are correct and not causing any conflicts.

Q: What is the next step in resolving this issue?

A: The next step in resolving this issue is to gather more information and try to reproduce the problem. You can try the following:

  • Collect more logs and error messages to help identify the root cause of the issue.
  • Try to reproduce the problem by simulating