Smart Home Community > Kasa Smart Thermostat > KH100 - Network connectivity problems
< Kasa Smart Thermostat

KH100 - Network connectivity problems

KH100 - Network connectivity problems

KH100 - Network connectivity problems
KH100 - Network connectivity problems
2024-01-27 16:00:35
Model: Kasa  
Hardware Version:
Firmware Version:

The KH100 hub is no longer working properly for me, as well as the connected thermostats.

 

This is due to network connectivity problems which are as follows:

- hub will be online for ca. 30 seconds (ping works, alarm works)

- hub will be offline for 30-35 seconds (no ping, alarm not executed)

- repeat

 

See attached ping log (ping.txt)

 

Besides that the status of the hub is no longer correct in the Tapo & Kasa apps, I also now have problems with the connected thermostats:

- connected thermostats no longer update their data in the Kasa & Tapo apps

- Installation of firmware updates to connected thermostats fails repeatedly

- at some point after failed firmware update, the connection between the hub and the thermostats seems to break down (connection LED slowly blinking), and thermostats will no longer correctly perform opening / shutting of the valve

 

I have tried the following (all unsuccessfully):

- delete & re-create hub & thermostats using the Tapo app

- factory reset of the hub & the thermostats, then try setup again in the Tapo app. I could setup the hub and the thermostats in the app, but I will have the same situation as before: connection LED on the thermostat is slowly blinking, values are not updated in the app and opening / shutting of the valve is not working

 

I then informed the vendor (Amazon) and received a replacement device. I have the same situation with the replacement device:

- after unpacking the Hub, plugging in and starting with original firmware, I could flawlessly connect and setup the hub in the app. I also tried ping and had stable ping for ~2 minutes.

- after performing the Hub firmware update (which was requested by the app) to version 1.5.4 Build 231121 Rel. 105224, it also shows the faulty behavior described above. So the same behavior as with the old hardware that I sent back.

 

Currently the hub & thermostats is not usable to me. I suspect this a problem introduced with a firmware update 1.5.4 Build 231121 Rel. 105224. Can you verify this and support me with fixing these devices?

  0      
 
  0      
 
#1
Options
7 Reply
Re:KH100 - Network connectivity problems
2024-01-27 16:02:23

Sorry, I could not attach the ping log file. Here is an excerpt:

 

PING 192.168.178.48 (192.168.178.48) 56(84) bytes of data.
From 192.168.178.26 icmp_seq=9 Destination Host Unreachable
From 192.168.178.26 icmp_seq=10 Destination Host Unreachable
From 192.168.178.26 icmp_seq=11 Destination Host Unreachable
From 192.168.178.26 icmp_seq=12 Destination Host Unreachable
From 192.168.178.26 icmp_seq=13 Destination Host Unreachable
From 192.168.178.26 icmp_seq=14 Destination Host Unreachable
From 192.168.178.26 icmp_seq=15 Destination Host Unreachable
From 192.168.178.26 icmp_seq=16 Destination Host Unreachable
From 192.168.178.26 icmp_seq=17 Destination Host Unreachable
From 192.168.178.26 icmp_seq=18 Destination Host Unreachable
From 192.168.178.26 icmp_seq=19 Destination Host Unreachable
From 192.168.178.26 icmp_seq=20 Destination Host Unreachable
64 bytes from 192.168.178.48: icmp_seq=23 ttl=255 time=318 ms
64 bytes from 192.168.178.48: icmp_seq=24 ttl=255 time=4.79 ms
64 bytes from 192.168.178.48: icmp_seq=25 ttl=255 time=5.14 ms
64 bytes from 192.168.178.48: icmp_seq=26 ttl=255 time=3.60 ms
64 bytes from 192.168.178.48: icmp_seq=27 ttl=255 time=3.75 ms
64 bytes from 192.168.178.48: icmp_seq=28 ttl=255 time=6.44 ms
64 bytes from 192.168.178.48: icmp_seq=29 ttl=255 time=9.01 ms
64 bytes from 192.168.178.48: icmp_seq=30 ttl=255 time=3.83 ms
64 bytes from 192.168.178.48: icmp_seq=31 ttl=255 time=4.13 ms
64 bytes from 192.168.178.48: icmp_seq=32 ttl=255 time=3.51 ms
64 bytes from 192.168.178.48: icmp_seq=33 ttl=255 time=7.69 ms
64 bytes from 192.168.178.48: icmp_seq=34 ttl=255 time=3.76 ms
64 bytes from 192.168.178.48: icmp_seq=35 ttl=255 time=4.25 ms
64 bytes from 192.168.178.48: icmp_seq=36 ttl=255 time=3.98 ms
64 bytes from 192.168.178.48: icmp_seq=37 ttl=255 time=3.52 ms
64 bytes from 192.168.178.48: icmp_seq=38 ttl=255 time=13.9 ms
64 bytes from 192.168.178.48: icmp_seq=39 ttl=255 time=3.60 ms
64 bytes from 192.168.178.48: icmp_seq=40 ttl=255 time=3.73 ms
64 bytes from 192.168.178.48: icmp_seq=41 ttl=255 time=24.3 ms
64 bytes from 192.168.178.48: icmp_seq=42 ttl=255 time=5.89 ms
64 bytes from 192.168.178.48: icmp_seq=43 ttl=255 time=5.36 ms
64 bytes from 192.168.178.48: icmp_seq=44 ttl=255 time=3.81 ms
64 bytes from 192.168.178.48: icmp_seq=45 ttl=255 time=4.07 ms
64 bytes from 192.168.178.48: icmp_seq=46 ttl=255 time=3.85 ms
64 bytes from 192.168.178.48: icmp_seq=47 ttl=255 time=4.74 ms
64 bytes from 192.168.178.48: icmp_seq=48 ttl=255 time=4.86 ms
64 bytes from 192.168.178.48: icmp_seq=49 ttl=255 time=3.70 ms
64 bytes from 192.168.178.48: icmp_seq=50 ttl=255 time=14.8 ms
64 bytes from 192.168.178.48: icmp_seq=51 ttl=255 time=3.66 ms
64 bytes from 192.168.178.48: icmp_seq=52 ttl=255 time=3.84 ms
64 bytes from 192.168.178.48: icmp_seq=53 ttl=255 time=3.79 ms
From 192.168.178.26 icmp_seq=60 Destination Host Unreachable
From 192.168.178.26 icmp_seq=61 Destination Host Unreachable
From 192.168.178.26 icmp_seq=62 Destination Host Unreachable
From 192.168.178.26 icmp_seq=63 Destination Host Unreachable
From 192.168.178.26 icmp_seq=64 Destination Host Unreachable
From 192.168.178.26 icmp_seq=65 Destination Host Unreachable
From 192.168.178.26 icmp_seq=66 Destination Host Unreachable

 

[~ snip ~]

 

From 192.168.178.26 icmp_seq=735 Destination Host Unreachable
From 192.168.178.26 icmp_seq=736 Destination Host Unreachable
From 192.168.178.26 icmp_seq=737 Destination Host Unreachable
From 192.168.178.26 icmp_seq=738 Destination Host Unreachable
From 192.168.178.26 icmp_seq=739 Destination Host Unreachable
From 192.168.178.26 icmp_seq=740 Destination Host Unreachable
From 192.168.178.26 icmp_seq=741 Destination Host Unreachable
64 bytes from 192.168.178.48: icmp_seq=744 ttl=255 time=492 ms
64 bytes from 192.168.178.48: icmp_seq=745 ttl=255 time=5.86 ms
64 bytes from 192.168.178.48: icmp_seq=746 ttl=255 time=3.70 ms
64 bytes from 192.168.178.48: icmp_seq=747 ttl=255 time=14.4 ms
64 bytes from 192.168.178.48: icmp_seq=748 ttl=255 time=4.26 ms
^C
--- 192.168.178.48 ping statistics ---
748 packets transmitted, 326 received, +197 errors, 56.4171% packet loss, time 757586ms
rtt min/avg/max/mdev = 3.295/41.000/2060.000/179.346 ms, pipe 4

 

  0  
  0  
#2
Options
Re:KH100 - Network connectivity problems
2024-01-27 16:03:50

I also noticed a similar problem by another user with a different model of Tapo hub (H100):
https://community.tp-link.com/en/smart-home/forum/topic/651756

Could this be a related problem?

  0  
  0  
#3
Options
Re:KH100 - Network connectivity problems
2024-01-31 03:16:25

  @peterh85 

 

Thank you for your feedback. At the moment, we have not yet determined whether the problem on your KH100 is caused by the same issue as the Tapo H100 discussed in this post. The phenomenon does look very similar though.

 

To assist with this case efficiently, I've forwarded your case to the TP-Link support engineering team, who will contact you with your registered email address later. Please pay attention to your email box for follow-up.

▶ Share Your Pet Story. Win Free Tapo Care! ▶ Smart Action 2.0 Explore and meet the next level home automation.
  0  
  0  
#4
Options
Re:KH100 - Network connectivity problems
2024-01-31 09:15:07

  @Wayne-TP based on the ping times these are _exactly_ the issues I am getting with the H100 as well, so they seem to be the same issue

  0  
  0  
#5
Options
Re:KH100 - Network connectivity problems
2024-01-31 21:39:39

I have same device and same problems. 

  0  
  0  
#6
Options
Re:KH100 - Network connectivity problems
2024-02-01 05:51:29

  0  
  0  
#7
Options
Re:KH100 - Network connectivity problems
2024-02-01 14:55:58

With help from the TP-Link engineering support team, I was able to install firmware updates on my KH100 and KE100 and now everything is fully functional again.

 

Please refer to this thread if you have the same problem:
https://community.tp-link.com/en/smart-home/forum/topic/653554

 

  0  
  0  
#8
Options

Information

Helpful: 0

Views: 367

Replies: 7

Related Articles
Speed & connectivity problem
122 0
Using T315 with KH100 Kit
295 0
KH100 & H100 - Both are needed?
242 0
Kasa KE100 TRVs needing a KH100 hub
252 0
I want to home net work
332 0
Network problem
195 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.