Credentials for H200

[bhumerca]

Hello!

I have 2 Tapo H200 and when trying to discover devices I got credentials error. I entered right credentials (tested with log in tapo app). Did something changed?

I get msg that device on my IP model H200 and then Device response did not match our challenge on ip 10.145.18.189, check that your e-mail and password (both case-sensitive) are correct.

[ZeliardM]

@bhumerca Can you run the discover with the --debug flag and post the output here? Scrub your personal information, but I'm looking for the encryption information, but ai need to see the whole response.

[bhumerca]

Here is the output from a manual discovery using python-kasa with DEBUG logging enabled.

Command:

• run inside a small async script that calls Discover.discover(credentials=creds)
• kasa version: 0.10.2
• device: Tapo H200 (SMART.TAPOHUB)
• platform: Windows 11, Python 3.11

I have redacted my device_id and owner fields.

Discover.discover(credentials=creds) with DEBUG logs
2026-01-15 14:19:49,101 - kasa.discover - DEBUG - [DISCOVERY] 255.255.255.255 >> {'system': {'get_sysinfo': {}}}
2026-01-15 14:19:49,148 - kasa.discover - DEBUG - Waiting 5 seconds for responses...
2026-01-15 14:19:49,195 - kasa.discover - DEBUG - Decrypted encrypt_info for 10.145.18.189: {'connect_ssid': '',
'connect_type': 'wired',
'device_id': 'REDACTED_22910EDC1063CA6C97CBE1022AA31FD',
'http_port': 443,
'owner': 'REDACTED_3016CF14CB127A85975AD16',
'sd_status': 'offline'}
2026-01-15 14:19:49,195 - kasa.device_factory - DEBUG - Using SmartCamDevice for SMART.TAPOHUB
2026-01-15 14:19:49,210 - kasa.device_factory - DEBUG - Finding protocol for 10.145.18.189
2026-01-15 14:19:49,210 - kasa.device_factory - DEBUG - Finding protocol for DeviceFamily.SmartTapoHub
2026-01-15 14:19:49,210 - kasa.device_factory - DEBUG - Finding transport for SMART.AES.HTTPS
2026-01-15 14:19:49,210 - kasa.transports.sslaestransport - DEBUG - Created AES transport for 10.145.18.189
2026-01-15 14:19:49,210 - kasa.discover - DEBUG - [DISCOVERY] 10.145.18.189 << {'error_code': 0,
'result': {'device_id': 'REDACTED_03025D6E1D3B530D768894E',
'device_model': 'H200',
'device_name': '#MASKED_NAME#',
'device_type': 'SMART.TAPOHUB',
'encrypt_info': {'data': '', 'key': '', 'sym_schm': 'AES'},
'encrypt_type': ['3'],
'factory_default': False,
'hardware_version': '1.0',
'ip': '10.145.18.189',
'isResetWiFi': False,
'is_support_iot_cloud': True,
'mac': '20-23-51-00-00-00',
'mgt_encrypt_schm': {'is_support_https': True},
'sv': 1}}
2026-01-15 14:19:49,210 - kasa.device - DEBUG - Initializing 10.145.18.189 of type <class 'kasa.smartcam.smartcamdevice.SmartCamDevice'>
2026-01-15 14:19:54,173 - kasa.discover - DEBUG - Discovered 1 devices

Najdenih naprav: 1 # "Devices found: 1"

--- Naprava na 10.145.18.189 ---
model (iz discovery): H200
2026-01-15 14:19:54,173 - kasa.protocols.smartprotocol - DEBUG - 10.145.18.189 multi-request-batch-1-of-1 >> '{"method":"multipleRequest","request_time_milis":1768483194174,"terminal_uuid":"JwNHBfzKlyvgb4QtU3wf3w==","params":{"requests":[{"method":"getDeviceInfo","params":{"device_info":{"name":["basic_info","info"]}}},{"method":"getAppComponentList","params":{"app_component":{"name":"app_component_list"}}},{"method":"getConnectionType","params":{"network":{"get_connection_type":{}}}}]}}'
2026-01-15 14:19:54,173 - kasa.transports.sslaestransport - DEBUG - Sending handshake1...
2026-01-15 14:19:54,204 - kasa.httpclient - DEBUG - Posting to https://10.145.18.189
2026-01-15 14:19:54,564 - kasa.transports.sslaestransport - DEBUG - Device responded with status 200: {'error_code': -40401, 'result': {'data': {'code': -60502}}}
2026-01-15 14:19:54,564 - kasa.transports.sslaestransport - DEBUG - Trying default credentials to 10.145.18.189
2026-01-15 14:19:54,579 - kasa.transports.sslaestransport - DEBUG - Sending handshake1...
2026-01-15 14:19:54,579 - kasa.httpclient - DEBUG - Posting to https://10.145.18.189
2026-01-15 14:19:54,579 - kasa.httpclient - DEBUG - Device 10.145.18.189 received an os error, enabling sequential request delay: [Errno None] Can not write request body for https://10.145.18.189
2026-01-15 14:19:54,579 - kasa.protocols.smartprotocol - DEBUG - Device 10.145.18.189 got a connection error, will retry 3 times: ('Device connection error: 10.145.18.189: [Errno None] Can not write request body for https://10.145.18.189', ClientOSError(None, 'Can not write request body for https://10.145.18.189'))
2026-01-15 14:19:54,579 - kasa.protocols.smartprotocol - DEBUG - 10.145.18.189 multi-request-batch-1-of-1 >> '{"method":"multipleRequest","request_time_milis":1768483194580,"terminal_uuid":"JwNHBfzKlyvgb4QtU3wf3w==","params":{"requests":[{"method":"getDeviceInfo","params":{"device_info":{"name":["basic_info","info"]}}},{"method":"getAppComponentList","params":{"app_component":{"name":"app_component_list"}}},{"method":"getConnectionType","params":{"network":{"get_connection_type":{}}}}]}}'
2026-01-15 14:19:54,579 - kasa.transports.sslaestransport - DEBUG - Sending handshake1...
2026-01-15 14:19:54,579 - kasa.httpclient - DEBUG - Device 10.145.18.189 waiting 0.25 seconds to send request
2026-01-15 14:19:54,829 - kasa.httpclient - DEBUG - Posting to https://10.145.18.189
2026-01-15 14:19:55,189 - kasa.transports.sslaestransport - DEBUG - Device responded with status 200: {'error_code': -40401, 'result': {'data': {'code': -60502}}}
2026-01-15 14:19:55,189 - kasa.transports.sslaestransport - DEBUG - Trying default credentials to 10.145.18.189
2026-01-15 14:19:55,204 - kasa.transports.sslaestransport - DEBUG - Sending handshake1...
2026-01-15 14:19:55,204 - kasa.httpclient - DEBUG - Device 10.145.18.189 waiting 0.23500000004423782 seconds to send request
2026-01-15 14:19:55,454 - kasa.httpclient - DEBUG - Posting to https://10.145.18.189
2026-01-15 14:19:55,814 - kasa.transports.sslaestransport - DEBUG - Device responded with status 200: {'error_code': -40413, 'result': {'data': {'code': -40401, 'encrypt_type': ['3'], 'key': 'MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCoVBwJv2pBtrr9ZY9C4lgqNo5+dFI+3A6W80h+8CzpCxsgl8Dic7JYmcTfOrtYtYJ6Vma3ZWx+NK1bJk8DFipOnDewVVJ6wmucnryF3OlfcIjLZsYjh4Sq2mdZfg0lOThTvh8z4V2jO6fWh91iwOOeCokGoMw9V+QyQevtCr5pSQIDAQAB', 'nonce': 'D105551504E62920', 'device_confirm': '216BB3F7A3E97F62A3E36B8098658158EF7D08499F097584CCEF8AF0EAB64AAED105551504E62920C09377A632F9C77B'}}}
2026-01-15 14:19:55,829 - kasa.transports.sslaestransport - DEBUG - Connected to 10.145.18.189 with default username
2026-01-15 14:19:55,829 - kasa.transports.sslaestransport - DEBUG - Device response did not match our challenge on ip 10.145.18.189, check that your e-mail and password (both case-sensitive) are correct.
2026-01-15 14:19:55,829 - kasa.protocols.smartprotocol - DEBUG - Unable to authenticate with 10.145.18.189, not retrying: Device response did not match our challenge on ip 10.145.18.189, check that your e-mail and password (both case-sensitive) are correct.
Napaka pri update(): AuthenticationError()
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x000001D0991DB4D0>
Unclosed connector
connections: ['deque([(<aiohttp.client_proto.ResponseHandler object at 0x000001D0993FB8C0>, 356994.156)])']
connector: <aiohttp.connector.TCPConnector object at 0x000001D099296850>

[ZeliardM]

@bhumerca And you're importing Credentials to build the credentials correctly assigning them to creds? It looks like it connects with the default credentials but fails when trying to use your credentials.

[bhumerca]

Yes, I’m using Credentials and passing them directly into Discover.discover(credentials=creds).

Here is the minimal script I’m running:

import asyncio
from kasa import Discover, Credentials

async def main():
    creds = Credentials(
        username="user@example.com",   # redacted
        password="********",           # redacted
    )

    devices = await Discover.discover(credentials=creds)
    print(f"Devices found: {len(devices)}")  

    for addr, dev in devices.items():
        print(f"--- Naprava na {addr} ---")
        print("  model (iz discovery):", dev.model)

        try:
            await dev.update()
        except Exception as e:
            print("  Error on update():", repr(e))  
            continue

        print("  Alias:", dev.alias)
        print("  Device type:", dev.device_type)

if __name__ == "__main__":
    asyncio.run(main())

And the output is:

Devices found: 1
--- Device on 10.145.18.189 ---
  model (from discovery): H200
  Error on update(): AuthenticationError()

[ZeliardM]

@bhumerca One thing to make sure is that the username and password are case sensitive, so if the email is:
Me@Gmail.Com
In the app, then it has to be that way in the script. Sometimes, we've seen it where phones or computers were automatically capitalizing things when users typed them in and they didn't do that when trying to authenticate. You find the e-mail and its capitalization

The other piece is 3rd Party Compatibility in the Tapo App, make sure that is turned on and it may resolve the issues as well.

Let me know.

[fewbafawef]

I also have been experiencing this issue since today.
Same python script, which has been working flawlessly for weeks, today (18th Jan 2026, 2:30PM roughly IST)
Getting the same "Device response did not match our challenge".
Same error as @bhumerca

[ZeliardM]

@fewbafawef @bhumerca Can you tell me if Third Party Compatibility is turned on in the Tapo App? Has the firmware updated recently? Can you verify that the username and password match case sensitive to the username in the Tapo App under the Profile?

Looking specifically at the logs posted by @bhumerca I have never seen the os error, enabling sequential request delay. Cannot write request body. This to me sounds like there may be some issue with other requirements for python-kasa in Python, not sure. Maybe reinstall python-kasa? The logs also mention that it can connect correctly via the default credentials. Do you have any other Tapo devices that can connect?

Something has to have changed locally, either on your system, network, or devices, i.e. TPLink changed something, for it to have stopped working all of a sudden if it was working. python-kasa has not been changed for months.

[fewbafawef]

I don't think I have enabled Third Party Compatibility.
Also, my script (which polls the door sensors) works fine now. The only problem is that the error log is being spammed with this error.

pi@rpi:~ $ sudo journalctl -u tapo -f                         Jan 18 16:23:17 rpi python[4317]: 2026-01-18 16:23:17,083 - ERROR - Error querying 192.168.68.105 for modules '' after first update: coroutine raised StopIteration
Jan 18 16:23:17 rpi python[4317]: 2026-01-18 16:23:17,083 - ERROR - Hub Error: getDeviceInfo not found in {} for device 192.168.68.105
Jan 18 16:23:18 rpi python[4317]: 2026-01-18 16:23:18,085 - ERROR - Error querying 192.168.68.105 for modules '' after first update: coroutine raised StopIteration
Jan 18 16:23:18 rpi python[4317]: 2026-01-18 16:23:18,086 - ERROR - Hub Error: getDeviceInfo not found in {} for device 192.168.68.105
Jan 18 16:23:19 rpi python[4317]: 2026-01-18 16:23:19,087 - ERROR - Error querying 192.168.68.105 for modules '' after first update: coroutine raised StopIteration
Jan 18 16:23:19 rpi python[4317]: 2026-01-18 16:23:19,088 - ERROR - Hub Error: getDeviceInfo not found in {} for device 192.168.68.105

My code still, somehow, works.

[ZeliardM]

@fewbafawef It looks like something in your script is polling the hub and it's not returning something.

[bhumerca]

Third Party Compatibility is turned on in the Tapo App..
I have 2 H200 in network with 12 T315 and wifi plugs

[ZeliardM]

@bhumerca It could be some changes with the latest firmware. Did the Hubs update firmware recently? The other WiFi plugs working ok? I take it the T315 are all connected to the hubs?

[fewbafawef]

@fewbafawef It looks like something in your script is polling the hub and it's not returning something.

async def monitor_hub(hub, ntfy_url):
    actions = ActionManager()
    previous_states = {}
    
    while True:
        actions.reload_if_changed()
        try:
            await hub.update()
            for sensor in hub.children:
                if sensor.model.startswith("T"):
                    current_state = getattr(sensor, "is_open", None)
                    if current_state is None and 'is_open' in sensor.features:
                        current_state = sensor.features['is_open'].value
                    
                    if sensor.alias in previous_states:
                        if current_state != previous_states[sensor.alias]:
                            await actions.trigger({
                                "sensor": sensor.alias,
                                "is_open": current_state,
                                "ntfy_url": ntfy_url
                            })
                    
                    previous_states[sensor.alias] = current_state
        except Exception as e:
            logger.error(f"Hub Error: {e}")
        await asyncio.sleep(1)

I do poll the hub. But the funny thing is how the script works even though it keeps erroring.

[fewbafawef]

Okay i found out what was wrong on my end.
I had 2 services polling the hub, so the second one couldn't poll the hub properly, the actual working one was the first service that ran, not this script.
Sorry for the trouble 😅

[bhumerca]

firmware version is 1.6.0 Build 20250915 rel 33520

All devices that are connected to both hubs are woring normaly (T315 and P115)

Hubs are connected via LAN and can be ping

[ZeliardM]

@bhumerca @fewbafawef It's newer firmware than what has been tested with the library, but still looks like it's from last year some time so it doesn't look like a recent change. Not sure, it may have been an API change on the backend with TPLink. I need to investigate the encryption still. Would either of you be able to clone the repository and checkout my PR #1638 and see if that makes a difference?