H100 hub losing network connection
H100 hub losing network connection
I have been finding that my sensors haven't been working all the time recently and I've been able to narrow down the issue to my H100 hub. What I've discovered is that the hub is constantly losing network connection for a few seconds then coming back online and then going down again. I determined that this is the case by pinging the hub's IP address from my computer and my router. So I thought, no problem, I'll just firmware upgrade the device and hope that this issue stops. However, the connection is dropping out so regularly that the firmware update cannot complete.
So next I decided to buy another H100 to see if the same issue happens with another identical device. Turns out it does also happen with a brand new device. However on this second device, I was able to perform a firmware update to v1.5.5 Build 240105 (HW v1.0) but found that the
device is still dropping pings constantly as regularly as the first device (see belowe screenshot).
Now I know you might be thinking, it must be an issue with my network or my router. I certainly did too. However, after thorough testing, I have confirmed that this issue is not present with any other Tapo device, TP-Link device or other wireless device. I have also checked over my router and turned off Band Steering and 5 Ghz etc. but to no avail.
Has anyone else faced a similar issue recently?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I have the same issue with an Amazon brought h100. Constant network loss then unable to update firmware yesterday. New h100 arrived today which updated firmware with no problems but once completed the hub keeps losing connection. Even with no devices connected, the issue persists evident by the light blinking blue once then turning solid orange. The network loss seems more frequent when the hub is asked to do something.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Wayne-TP Hi, I use a TP-Link router
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
The tech team was made aware of this situation, they will likely reach out to you via email to continue to troubleshoot this case. Please check your email box later and confirm.
- Copy Link
- Report Inappropriate Content
Hi. Same issue here. I have different tapo devices (cams, smart plugs) connected and working, but the tapo h100 keeps loosing the connection. I have an Eero 6 router. Both Eero and h100 firmwares updates. Issue started some weeks ago. Before it was working. Any solution?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Do you use any other third-party software/services to manage Tapo devices? For example, the Home Assistant?
Tapo H100 supports local support on the latest firmware version. Please check how many of your automation rules are adapted to the Local Smart, which can be run locally without Internet access. The local smart entries will be marked with a Kasa or Tapo logo.
E.g.
- Copy Link
- Report Inappropriate Content
@Wayne-TP no - just the tapo app, also I don't have any automation rules set at all. I'm testing connectivity by trying to change the ringtone in the app which sometimes works, often doesn't. Whether it responds or not tallies up with the device pinging - output below showing the cyclical behaviour. I've tried different wifi networks too, same result.
Pinging 192.168.1.96 with 32 bytes of data:
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.96: bytes=32 time=842ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=45ms TTL=255
Reply from 192.168.1.96: bytes=32 time=352ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=6ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=6ms TTL=255
Reply from 192.168.1.96: bytes=32 time=7ms TTL=255
Reply from 192.168.1.96: bytes=32 time=9ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=5ms TTL=255
Reply from 192.168.1.96: bytes=32 time=2ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=7ms TTL=255
Reply from 192.168.1.96: bytes=32 time=11ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=29ms TTL=255
Reply from 192.168.1.96: bytes=32 time=24ms TTL=255
Reply from 192.168.1.96: bytes=32 time=2ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.96: bytes=32 time=1935ms TTL=255
Reply from 192.168.1.96: bytes=32 time=15ms TTL=255
Reply from 192.168.1.96: bytes=32 time=5ms TTL=255
Reply from 192.168.1.96: bytes=32 time=74ms TTL=255
Reply from 192.168.1.96: bytes=32 time=2ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=17ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=6ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=8ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=7ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=12ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=8ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=5ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=14ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=2ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.230: Destination host unreachable.
Reply from 192.168.1.96: bytes=32 time=1091ms TTL=255
Reply from 192.168.1.96: bytes=32 time=31ms TTL=255
Reply from 192.168.1.96: bytes=32 time=2ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=2ms TTL=255
Reply from 192.168.1.96: bytes=32 time=9ms TTL=255
Reply from 192.168.1.96: bytes=32 time=2ms TTL=255
Reply from 192.168.1.96: bytes=32 time=7ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=4ms TTL=255
Reply from 192.168.1.96: bytes=32 time=3ms TTL=255
Reply from 192.168.1.96: bytes=32 time=5ms TTL=255
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2653
Replies: 19
Voters 0
No one has voted for it yet.