search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.54k stars 30.72k forks source link

TP-Link Entities continually cycle with 'Failed setup - will retry' #95028

Closed rdperkins closed 1 year ago

rdperkins commented 1 year ago

The problem

I've had this problem for at least a couple of weeks, and would appreciate help.

What version of Home Assistant Core has the issue?

core-2023.6.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

TP-Link Kasa

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @rytilahti, @thegardenmonkey, mind taking a look at this issue as it has been labeled with an integration (tplink) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `tplink` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tplink` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)

tplink documentation tplink source (message by IssueLinks)

rytilahti commented 1 year ago

Take a look at the logs to see if there is something related to the tplink integration, it is not possible to help without any details on what is happening.

releeh commented 1 year ago

I am seeing this same issue for a couple of my tplink outlets as well.

Home Assistant 2023.6.3 Supervisor 2023.06.4 Operating System 10.3 Frontend 20230608.0 - latest

Logger: homeassistant.config_entries Source: config_entries.py:1247 First occurred: 3:28:49 PM (1 occurrences) Last logged: 3:28:49 PM

Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background

Logger: homeassistant.config_entries Source: config_entries.py:429 First occurred: 3:24:50 PM (9 occurrences) Last logged: 3:25:09 PM

Config entry 'Rear Bedroom TV Outlet KP115(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.196: [Errno 113] Connect call failed ('192.168.2.196', 9999); Retrying in background Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background Config entry 'Main Roomba' for roomba integration not ready yet; Retrying in background Config entry 'Kitchen Coffee Maker EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.27.254: ; Retrying in background Config entry 'Office Table Fan EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.25.23: ; Retrying in background

Here is one of the issue device's information: EP25(US) by TP-Link Firmware: 1.0.9 Build 230224 Rel.113305 Hardware: 1.0

All issue devices are responsive through the TP Link app (Kasa) on my android.

releeh commented 1 year ago

Disregard. Had something to do with my DHCP server. Quick reboot and up and running again.

I am seeing this same issue for a couple of my tplink outlets as well.

Home Assistant 2023.6.3 Supervisor 2023.06.4 Operating System 10.3 Frontend 20230608.0 - latest

Logger: homeassistant.config_entries Source: config_entries.py:1247 First occurred: 3:28:49 PM (1 occurrences) Last logged: 3:28:49 PM

Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background

Logger: homeassistant.config_entries Source: config_entries.py:429 First occurred: 3:24:50 PM (9 occurrences) Last logged: 3:25:09 PM

Config entry 'Rear Bedroom TV Outlet KP115(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.196: [Errno 113] Connect call failed ('192.168.2.196', 9999); Retrying in background Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background Config entry 'Main Roomba' for roomba integration not ready yet; Retrying in background Config entry 'Kitchen Coffee Maker EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.27.254: ; Retrying in background Config entry 'Office Table Fan EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.25.23: ; Retrying in background

Here is one of the issue device's information: EP25(US) by TP-Link Firmware: 1.0.9 Build 230224 Rel.113305 Hardware: 1.0

All issue devices are responsive through the TP Link app (Kasa) on my android.

rdperkins commented 1 year ago

Router problem with my TP-Link AXE5300 6e mesh. Dropping clients. Think my 130 clients are the problem. What router do you use?

Sent from my iPhone Robert Perkins

On Jul 3, 2023, at 5:13 PM, releeh @.***> wrote:



Disregard. Had something to do with my DHCP server. Quick reboot and up and running again.

I am seeing this same issue for a couple of my tplink outlets as well.

Home Assistant 2023.6.3 Supervisor 2023.06.4 Operating System 10.3 Frontend 20230608.0 - latest

Logger: homeassistant.config_entries Source: config_entries.py:1247 First occurred: 3:28:49 PM (1 occurrences) Last logged: 3:28:49 PM

Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background

Logger: homeassistant.config_entries Source: config_entries.py:429 First occurred: 3:24:50 PM (9 occurrences) Last logged: 3:25:09 PM

Config entry 'Rear Bedroom TV Outlet KP115(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.196: [Errno 113] Connect call failed ('192.168.2.196', 9999); Retrying in background Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background Config entry 'Main Roomba' for roomba integration not ready yet; Retrying in background Config entry 'Kitchen Coffee Maker EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.27.254: ; Retrying in background Config entry 'Office Table Fan EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.25.23: ; Retrying in background

Here is one of the issue device's information: EP25(US) by TP-Link Firmware: 1.0.9 Build 230224 Rel.113305 Hardware: 1.0

All issue devices are responsive through the TP Link app (Kasa) on my android.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/95028#issuecomment-1619156991, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH55NH4AZECJUMTUN2J6DMLXOMYZHANCNFSM6AAAAAAZPQEAYM. You are receiving this because you authored the thread.Message ID: @.***>

sandstormkeshav commented 1 year ago

I think there might be more to this. This is the error I see in my log: 2023-07-04 14:25:57.185 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Family Room Light HS200(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.10.48: [Errno 113] Connect call failed ('192.168.10.48', 9999); Retrying in background If I run kasa --host=192.168.10.48 on the host where the home assistant container is running I get:

No --type defined, discovering..
Got error: SmartDeviceException("Unable to connect to the device: 192.168.10.48: [Errno 113] Connect call failed 
('192.168.10.48', 9999)")

However if I run this on another host within the same subnet it is successful:

k@ksn ~ % kasa --host=192.168.10.48
No --type defined, discovering..
== Family Room Light - HS200(US) ==
    Host: 192.168.10.48
    Device state: ON

    == Generic information ==
    Time:         2000-01-04 11:26:30 (tz: {'index': 6, 'err_code': 0}
    Hardware:     5.0
    Software:     1.0.6 Build 210820 Rel.104606
    MAC (rssi):   B4:B0:24:E2:3D:09 (-44)
    Location:     {'latitude': 0.0, 'longitude': 0.0}

    == Device specific information ==
    LED state: True
    On since: 2023-07-04 14:24:18

    == Modules ==
    + <Module Schedule (schedule) for 192.168.10.48>
    + <Module Usage (schedule) for 192.168.10.48>
    + <Module Antitheft (anti_theft) for 192.168.10.48>
    + <Module Time (time) for 192.168.10.48>
    + <Module Cloud (cnCloud) for 192.168.10.48>

This doesn't seem to be a network issue, it seems like the switch is somehow ignoring commands from an IP.

releeh commented 1 year ago

I do DHCP on my server 2019 windows domain controller. WiFi is a ubiquiti mesh.

On Tue, Jul 4, 2023, 12:02 AM Robert Perkins @.***> wrote:

Router problem with my TP-Link AXE5300 6e mesh. Dropping clients. Think my 130 clients are the problem. What router do you use?

Sent from my iPhone Robert Perkins

On Jul 3, 2023, at 5:13 PM, releeh @.***> wrote:



Disregard. Had something to do with my DHCP server. Quick reboot and up and running again.

I am seeing this same issue for a couple of my tplink outlets as well.

Home Assistant 2023.6.3 Supervisor 2023.06.4 Operating System 10.3 Frontend 20230608.0 - latest

Logger: homeassistant.config_entries Source: config_entries.py:1247 First occurred: 3:28:49 PM (1 occurrences) Last logged: 3:28:49 PM

Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background

Logger: homeassistant.config_entries Source: config_entries.py:429 First occurred: 3:24:50 PM (9 occurrences) Last logged: 3:25:09 PM

Config entry 'Rear Bedroom TV Outlet KP115(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.196: [Errno 113] Connect call failed ('192.168.2.196', 9999); Retrying in background Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background Config entry 'Main Roomba' for roomba integration not ready yet; Retrying in background Config entry 'Kitchen Coffee Maker EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.27.254: ; Retrying in background Config entry 'Office Table Fan EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.25.23: ; Retrying in background

Here is one of the issue device's information: EP25(US) by TP-Link Firmware: 1.0.9 Build 230224 Rel.113305 Hardware: 1.0

All issue devices are responsive through the TP Link app (Kasa) on my android.

— Reply to this email directly, view it on GitHub< https://github.com/home-assistant/core/issues/95028#issuecomment-1619156991>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AH55NH4AZECJUMTUN2J6DMLXOMYZHANCNFSM6AAAAAAZPQEAYM>.

You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95028#issuecomment-1619491481, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3RHYRAIH3SS4C7CJPF7DG3XOOPWTANCNFSM6AAAAAAZPQEAYM . You are receiving this because you commented.Message ID: @.***>

rdperkins commented 1 year ago

Dream machine with access points or dream router?

Sent from my iPhone Robert Perkins

On Jul 4, 2023, at 7:00 PM, releeh @.***> wrote:



I do DHCP on my server 2019 windows domain controller. WiFi is a ubiquiti mesh.

On Tue, Jul 4, 2023, 12:02 AM Robert Perkins @.***> wrote:

Router problem with my TP-Link AXE5300 6e mesh. Dropping clients. Think my 130 clients are the problem. What router do you use?

Sent from my iPhone Robert Perkins

On Jul 3, 2023, at 5:13 PM, releeh @.***> wrote:



Disregard. Had something to do with my DHCP server. Quick reboot and up and running again.

I am seeing this same issue for a couple of my tplink outlets as well.

Home Assistant 2023.6.3 Supervisor 2023.06.4 Operating System 10.3 Frontend 20230608.0 - latest

Logger: homeassistant.config_entries Source: config_entries.py:1247 First occurred: 3:28:49 PM (1 occurrences) Last logged: 3:28:49 PM

Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background

Logger: homeassistant.config_entries Source: config_entries.py:429 First occurred: 3:24:50 PM (9 occurrences) Last logged: 3:25:09 PM

Config entry 'Rear Bedroom TV Outlet KP115(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.196: [Errno 113] Connect call failed ('192.168.2.196', 9999); Retrying in background Config entry 'Office Desk Light KP125(US)' for tplink integration not ready yet: Unable to connect to the device: 192.168.2.190: [Errno 113] Connect call failed ('192.168.2.190', 9999); Retrying in background Config entry 'Main Roomba' for roomba integration not ready yet; Retrying in background Config entry 'Kitchen Coffee Maker EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.27.254: ; Retrying in background Config entry 'Office Table Fan EP25(US)' for tplink integration not ready yet: Unable to connect to the device: 169.254.25.23: ; Retrying in background

Here is one of the issue device's information: EP25(US) by TP-Link Firmware: 1.0.9 Build 230224 Rel.113305 Hardware: 1.0

All issue devices are responsive through the TP Link app (Kasa) on my android.

— Reply to this email directly, view it on GitHub< https://github.com/home-assistant/core/issues/95028#issuecomment-1619156991>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AH55NH4AZECJUMTUN2J6DMLXOMYZHANCNFSM6AAAAAAZPQEAYM>.

You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/95028#issuecomment-1619491481, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3RHYRAIH3SS4C7CJPF7DG3XOOPWTANCNFSM6AAAAAAZPQEAYM . You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/95028#issuecomment-1620814580, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH55NH7YN6X27WNXERAPINDXOSOBHANCNFSM6AAAAAAZPQEAYM. You are receiving this because you authored the thread.Message ID: @.***>

SentiHassio1979 commented 1 year ago

Just guessing from solving the issue on my side. Were the entities originally created via yaml entry or did the integration create these? I had my yaml ones still in there and those were in the loop. I removed those en now it works.

rdperkins commented 1 year ago

All were created via the integration. I checked all the yaml files under the www folder. Were your yaml files located somewhere else? Were the entities in configuration.yaml?

From: SentiHassio1979 @.> Sent: Tuesday, July 4, 2023 10:10 PM To: home-assistant/core @.> Cc: Robert Perkins @.>; Author @.> Subject: Re: [home-assistant/core] TP-Link Entities continually cycle from Integration Entries to Needs Attention-Retrying Setup. (Issue #95028)

Just guessing from solving the issue on my side. Were the entities originally created via yaml entry or did the integration create these? I had my yaml ones still in there and those were in the loop. I removed those en now it works.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/95028#issuecomment-1620918464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH55NHZWTI2343X5UNFDGATXOTEIPANCNFSM6AAAAAAZPQEAYM. You are receiving this because you authored the thread.Message ID: @.**@.>>

rdperkins commented 1 year ago

This is an example of one of my 24 kasa devices showing up in the debug log: “ 2023-07-06 02:41:07.528 DEBUG (MainThread) [kasa.discover] [DISCOVERY] 192.168.144.120 << {'system': {'get_sysinfo': {'sw_ver': '1.0.9 Build 221011 Rel.195547', 'hw_ver': '5.0', 'model': 'HS200(US)', 'deviceId': '8006F3D55DCC9215052E5FFDF4FC46A220F25B88', 'oemId': '8754F01961F1BCDAEC5B68B74FFFA7E0', 'hwId': '6F710464613C9F1EA67305BD422BC2D0', 'rssi': -49, 'latitude_i': 349350, 'longitude_i': -808505, 'alias': 'Master Fan', 'status': 'new', 'obd_src': 'tplink', 'mic_type': 'IOT.SMARTPLUGSWITCH', 'feature': 'TIM', 'mac': '9C:53:22:00:9D:76', 'updating': 0, 'led_off': 0, 'relay_state': 1, 'on_time': 12064, 'icon_hash': '', 'dev_name': 'Smart Wi-Fi Light Switch', 'active_mode': 'none', 'next_action': {'type': -1}, 'err_code': 0}}} 2023-07-06 02:41:07.529 DEBUG (MainThread) [kasa.smartdevice] Initializing 192.168.144.120 of type <class 'kasa.smartplug.SmartPlug'> 2023-07-06 02:41:07.529 DEBUG (MainThread) [kasa.smartdevice] Adding module <Module Schedule (schedule) for 192.168.144.120> 2023-07-06 02:41:07.529 DEBUG (MainThread) [kasa.smartdevice] Adding module <Module Usage (schedule) for 192.168.144.120> 2023-07-06 02:41:07.529 DEBUG (MainThread) [kasa.smartdevice] Adding module <Module Antitheft (anti_theft) for 192.168.144.120> 2023-07-06 02:41:07.529 DEBUG (MainThread) [kasa.smartdevice] Adding module <Module Time (time) for 192.168.144.120> 2023-07-06 02:41:07.529 DEBUG (MainThread) [kasa.smartdevice] Adding module <Module Cloud (cnCloud) for 192.168.144.120> “

From: SentiHassio1979 @.> Sent: Tuesday, July 4, 2023 10:10 PM To: home-assistant/core @.> Cc: Robert Perkins @.>; Author @.> Subject: Re: [home-assistant/core] TP-Link Entities continually cycle from Integration Entries to Needs Attention-Retrying Setup. (Issue #95028)

Just guessing from solving the issue on my side. Were the entities originally created via yaml entry or did the integration create these? I had my yaml ones still in there and those were in the loop. I removed those en now it works.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/95028#issuecomment-1620918464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH55NHZWTI2343X5UNFDGATXOTEIPANCNFSM6AAAAAAZPQEAYM. You are receiving this because you authored the thread.Message ID: @.**@.>>

VincentClement1 commented 1 year ago

System Information

version core-2023.7.1
installation_type Home Assistant Container
dev false
hassio false
docker true
user root
virtualenv false
python_version 3.11.4
os_name Linux
os_version 6.1.21-v8+
arch aarch64

After the HA upgrade to 2023.7.1 the TP-Link integration has become wonky. I have 6 TP-Link devices (plugs and power strips) and I will randomly get the "Failed setup - will retry" error for 5 of the 6 devices. The one device that works isn't always the same device (which is weird). I can control all 6 devices with the Kasa App, via Alexa and via Hey Google.

Other than the HA upgrade, nothing has changed. No firmware updates to the TP-Link devices, my wifi setup has not changed nor been subject to any upgrades. All devices show up in the router and as device_trackers via the ASUSRouter integration.

Clicking on Reload usually does nothing with the integration showing an error and that it will retry. But, if I disable the problem devices, and then enable them after 5 minutes or so, the entities are setup with no errors. I've done the "Disable, wait, Enable" twice now and it brings all the devices 'back to life'.

In summary:

1) Devices can't be 'connected' and the TP-Link integration fails.

2) Clicking on Reload does not resolve the issue. However, disabling the device and then enabling it after a period of time, works.

joshuacole commented 1 year ago

Having the same issues as above. After HA upgrade half of the TP-Link strips will not connect, despite being available online and working in the app.

rdperkins commented 1 year ago

I wonder if TP-Link pushed out a firmware update recently.

Sent from my iPhone Robert Perkins

On Jul 13, 2023, at 11:45 PM, Joshua Cole @.***> wrote:



Having the same issues as above. After HA upgrade half of the TP-Link strips will not connect, despite being available online and working in the app.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/95028#issuecomment-1635224065, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH55NHZTRC5CPUAT3PV7HTTXQC6GPANCNFSM6AAAAAAZPQEAYM. You are receiving this because you authored the thread.Message ID: @.***>

VincentClement1 commented 1 year ago

Firmware on Kasa devices does not auto-update. You have to manually update the firmware via the Kasa app.

I report no issues with the TP-Link integration since upgrading to Release 2023.7.2 (July 13). I don't see anything in the release notes that mentions TP-Link specifically. Stay tuned.

UncleLeoTheDad commented 1 year ago

Same problem. My HS300 power strips keep going unavailable.

dennisiver commented 1 year ago

I just unpluged and then replugged the unavailable devices, and it fixed. Some of my devices with Homekit controller, Tapo controller and KASA controller have the same problem. All of them can be fixed.

sandstormkeshav commented 1 year ago

I just unpluged and then replugged the unavailable devices, and it fixed. Some of my devices with Homekit controller, Tapo controller and KASA controller have the same problem. All of them can be fixed.

Yes an unplug and replug of the device fixes it however it would be preferable not to need to do this. The Kasa app can still operate the devices when home assistant is retrying setup, so it seems like this should be fixable in software.

rdperkins commented 1 year ago

Why is Home Assistant choking when the phone app works? I have this problem with Tuya and Kasa. Strangely I have the same problem with Alexa with these two platforms. I’m getting a UniFi router in a few days. That may help. With nearly 130 devices my TP-Link router experiences frequent dropouts and their support person tells me they can’t handle more than 120. His suggestion was to disconnect some of the clients leave them unconnected. Not much help there. The Dream Router is supposed to handle 300. I’ll try that first before trying to worry about other things.

Sent from my iPhone Robert Perkins

On Jul 21, 2023, at 1:57 AM, Keshav Sreekumar @.***> wrote:



I just unpluged and then replugged the unavailable devices, and it fixed. Some of my devices with Homekit controller, Tapo controller and KASA controller have the same problem. All of them can be fixed.

Yes an unplug and replug of the device fixes it however it would be preferable not to need to do this. The Kasa app can still operate the devices when home assistant is retrying setup, so it seems like this should be fixable in software.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/95028#issuecomment-1645021974, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH55NH5H3VOTVMCWGGR7XALXRIK2ZANCNFSM6AAAAAAZPQEAYM. You are receiving this because you authored the thread.Message ID: @.***>

dennisiver commented 1 year ago

Actually I have a UniFi Dream Machine SE, but it will still happen. So the router might not be the key point.

rdperkins commented 1 year ago

Good to know. How many clients are you running with your UDM? Do you experience frequent drops besides the Kasa clients? How about Tuya?

From: dennisiver @.> Sent: Friday, July 21, 2023 3:26 AM To: home-assistant/core @.> Cc: Robert Perkins @.>; Author @.> Subject: Re: [home-assistant/core] TP-Link Entities continually cycle with 'Failed setup - will retry' (Issue #95028)

Actually I have a UniFi Dream Machine SE, but it will still happen. So the router might not be the key point.

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/95028#issuecomment-1645109788, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH55NH775WXOPK6277JRP53XRIVGXANCNFSM6AAAAAAZPQEAYM. You are receiving this because you authored the thread.Message ID: @.**@.>>

dennisiver commented 1 year ago

About 70 clients , it worked well and didn't lost any connection. You couldn't feel any delay between devices. All of my Tuya and KASA devices worked perfectly. Only the temperature of UDM SE is about 50 degree and might need some fans if you put it in the cabinet.

rdperkins commented 1 year ago

Everything working now. Changed from TP-Link Deco 5300 router to Dream Router and deleted a couple of devices I had removed, and knock-on-wood things look good. Thanks for all the comments and suggestions.