Stopped working from Homebridge `ECONNREFUSED`

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Out of nowhere, I’m now not able anymore to control my plug.

There’s this error in the log and it’s weird because the IP adress that it is showing is one of my computer (not even the one with homebridge) and not the plug…

I don’t know why.

I tried upgrading the the latest v7.1.0, but it’s the same.

Also I’m still able to control the plugs from the Kasa App, so it really is from homebdrige.

What, if anything, has recently changed?

Nothing’s changed. It just happened out of nowhere…

Version

v7.1.0-next.0 / v7.0.1

Node Version

v16.14.0

Homebridge Version

v1.4.0

Which OS/Platform?

Linux

Relevant log output

[3/23/2022, 12:56:39 AM] [TplinkSmarthome.API] TCP 192.[...]:9999 Error: connect ECONNREFUSED 192.[...]:9999
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '192.[...]',
  port: 9999
}
[3/23/2022, 12:56:39 AM] [TplinkSmarthome.API] [Lampe] device.send() Error: connect ECONNREFUSED 192.[...]:9999
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '192.[...]',
  port: 9999
}
[3/23/2022, 12:56:39 AM] [TplinkSmarthome] [Lampe] {"errno":-111,"code":"ECONNREFUSED","syscall":"connect","address":"192.[...]","port":9999}

Configuration

{
    "name": "TplinkSmarthome",
    "addCustomCharacteristics": true,
    "switchModels": [
        "HS103"
    ],
    "deviceTypes": [
        "plug",
        "bulb"
    ],
    "_bridge": {
        "username": "[...],
        "port": [...]
    },
    "platform": "TplinkSmarthome"
}

[EricSabe]

I think the magical fairies are temperamental.

[phydeauxfilms]

I think the magical fairies are temperamental.

LOL, That they are. Before I totally reorganized my network I was able to trigger it on command by checking the eufy cameras and operating some Tplink switches at the same time. Now it’s much less often and I can’t even trigger it at the moment. Last error was at 9:30 am this morning. It may just be an overloaded network combined with home bridge, a Pi-hole, and a neighborhood that has 116 Wifi networks within range of my apartment (true story, I checked wifi explorer). IDK. Just glad it’s working at the moment.