# TP-Link HS100 V4.1 communication error

**URL:** <https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228>\
**Category:** Bindings\
**Tags:** openhab2, tp-link\
**Created:** [November 14, 2020, 12:45am UTC](https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228 "2020-11-14T00:45:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![aobcts](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a9a28c/32.png) [@aobcts](https://community.openhab.org/u/aobcts)\
**Post date:** [November 14, 2020, 12:45am UTC](https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228/1 "2020-11-14T00:45:50Z")

</div>

Hi All, just wondering if anyone can assist me,

I’ve got multiple tp-link HS100 and HS110 sockets (mainly version 2.1, but some below) which are working and connected fine with openhab 2.5.7

I added 4 sockets the other day (not realising they were a newer version - 4.1) and openhab found them automatically, then today i went to control the sockets and they were in a communication error state.  
I’ve since tried to add a further two sockets, but openhab cannot find them, I’ve tried to add them manually but get the same result.

Is this a known issue? Any help/guidance would be great 🙂 Thanks in advance!

---

<div class="post-metadata">

**Author:** ![hilbrand](https://community.openhab.org/user_avatar/community.openhab.org/hilbrand/32/72354_2.png) [@hilbrand](https://community.openhab.org/u/hilbrand)\
**Post date:** [November 14, 2020, 7:03am UTC](https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228/2 "2020-11-14T07:03:04Z")

</div>

> <https://github.com/softScheck/tplink-smartplug/issues/81>
>
> I was not aware that these had an automatic firmware update but it is only what …I can assume has happened. I have some HS100 devices that present at hardware version 4.1 (I have other that are 2.0 and 2.1 and all work fine).  
> 
> Suddenly they now not longer work and NMAP shows nothing on port 9999 any more. 
> 
> The units work fine in the Kassa app but that is it, I can only assume a firmware update has done this. 
> 
> \*\*Result for UDP nmap scan\*\*
> 
> blake@nash:~$ sudo nmap -p0-65535 192.168.0.154 -sU
> Starting Nmap 7.80 ( https://nmap.org ) at 2020-11-12 08:46 UTC
> Nmap scan report for BM-TVConsole.ghost7.com (192.168.0.154)
> Host is up (0.0058s latency).
> Not shown: 65535 closed ports
> PORT STATE SERVICE
> 20002/udp open|filtered commtact-http
> MAC Address: CC:32:E5:A6:E5:64 (Unknown)
> 
> Nmap done: 1 IP address (1 host up) scanned in 35.37 seconds
> blake@nash:~$
> 
> \*\*Result for TCP nmap scan\*\*
> 
> blake@nash:~$ sudo nmap -p0-65535 192.168.0.154 -sT
> Starting Nmap 7.80 ( https://nmap.org ) at 2020-11-12 08:48 UTC
> Nmap scan report for BM-TVConsole.ghost7.com (192.168.0.154)
> Host is up (0.0044s latency).
> Not shown: 65535 closed ports
> PORT STATE SERVICE
> 80/tcp open http
> MAC Address: CC:32:E5:A6:E5:64 (Unknown)
> 
> Nmap done: 1 IP address (1 host up) scanned in 30.08 seconds
> blake@nash:~$

---

<div class="post-metadata">

**Author:** ![aobcts](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a9a28c/32.png) [@aobcts](https://community.openhab.org/u/aobcts)\
**Post date:** [November 14, 2020, 12:53pm UTC](https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228/3 "2020-11-14T12:53:48Z")

</div>

Wow, think that’s coincidental that I’ve only just purchased them and all the devices seem to have stopped communicating in the last couple of days.

Thanks for pointing me in the right direction, I did various searches but didn’t manage to find anything.

Thank you so much for your help! 🙂

---

<div class="post-metadata">

**Author:** ![crystollic](https://community.openhab.org/letter_avatar_proxy/v4/letter/c/3ec8ea/32.png) [@crystollic](https://community.openhab.org/u/crystollic)\
**Post date:** [November 21, 2020, 7:39pm UTC](https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228/4 "2020-11-21T19:39:50Z")

</div>

Did you get it working again? I have four of these, the newer 4.1 hardware versions no longer connect but the old 2.1 is fine. I am assuming the firmware has updated on the newer and is not longer compatible with the binding ☹

---

<div class="post-metadata">

**Author:** ![aobcts](https://community.openhab.org/letter_avatar_proxy/v4/letter/a/a9a28c/32.png) [@aobcts](https://community.openhab.org/u/aobcts)\
**Post date:** [November 30, 2020, 11:24pm UTC](https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228/5 "2020-11-30T23:24:47Z")

</div>

Unfortunately not. I keep looking but haven’t bumped into anything yet..

---

<div class="post-metadata">

**Author:** ![hilbrand](https://community.openhab.org/user_avatar/community.openhab.org/hilbrand/32/72354_2.png) [@hilbrand](https://community.openhab.org/u/hilbrand)\
**Post date:** [December 1, 2020, 5:06am UTC](https://community.openhab.org/t/tp-link-hs100-v4-1-communication-error/108228/6 "2020-12-01T05:06:29Z")

</div>

> [@Tplink closed port 9999](https://community.openhab.org/t/tplink-closed-port-9999/108652/8):
>
> If anyone has this problem. See this post about how to get a work around from TP-link:
