Performance issues with hub and automation

I have nearly fully migrated from ST (101 of 130 devices across) and I've started noticing degraded performance in two places:

  1. Navigating the portal: Can take (for example) 5-6 seconds to load the apps page or devices page, also, creating rules is just a waiting game

  2. Delays in automation occurring: Press a button, wait 3-4 seconds for hue light to turn on, also, motion sensor activates, wait 3-4 seconds for the light to turn on.

Where should I start investigating?

How many of those devices use custom drivers?
What custom apps are you using?



Hubitat TP-Link/Kasa Manager davegut 2018-12-21 19:22:26 AEST
hubitat-VLD eyrich 2018-12-26 09:29:52 AEST
Send IP2IR BPTWorld 2018-12-23 12:16:18 AEST
Send IP2IR Child BPTWorld 2018-12-23 12:16:41 AEST


IP2IR Telnet BPTWorld SpeechSynthesis, Notification, Telnet, Initialize
TP-Link/Kasa Color Bulb davegut Switch, SwitchLevel, Refresh, ColorControl, Actuator, ColorTemperature, Light, ColorMode
TP-Link/Kasa Dimming Switch davegut Switch, SwitchLevel, Refresh, Actuator
TP-Link/Kasa Multi-Plug davegut Switch, Refresh, Actuator
TP-Link/Kasa Plug-Switch davegut Switch, Refresh, Actuator
TP-Link/Kasa Soft White Bulb davegut Switch, SwitchLevel, Refresh, Actuator, Light
TP-Link/Kasa Tunable White Bulb davegut Switch, SwitchLevel, Refresh, Actuator, ColorTemperature, Light

As you are using only one custom app, I would personally remove it, reboot and see how things run then.
Telnet programs can often cause problems.

I’m not saying that this is the problem, but it’s the first thing I would do in troubleshooting.


aren't all 4 of those apps custom?

You can also look at your logs. When I've experienced lagginess in the past I would look at Past Logs and scan down the list for errors (usually highlighted in red). 9 times out of 10 there is something screaming for help. Once resolved the hub usually returns to normal.

Sorry, I meant one with telnet that I know of.
I’m not familiar with ‘kasa manager’

I had a similar issue, I suggest to contact support and @bobbyD so they can let you know what is the problem, in my case it was a driver flooding my telnet, but by the way, I had the Kasa Manager installed and I deleted it because it was flooding my logs with discoveries of nothing so probably it's flooding your telnet too.

I'm removing Kasa, the Global Cache app and Sonos. I noticed that it couldn't see a couple of sonos devices so was timing out, this is because I set the hub up initially in my office and it discovered the 3 sonos zones there, then i took it home and it found my other 10 at home.

The problem i'm facing now is that it wont let me remove the Sonos app (It just shows a spinning wheel) - potentially because it can't see the office sonos devices. Any tips on a more 'forced' removal?

At the bottom. Of the page that opens, click remove.

1 Like

Pleased to report that it's all super fast again. Will do backups as I install each thing again and will report what it is. So far, it's not looking like it was Sonos as 10 devices installed and all running well.

1 Like

I have added Sonos back in and TP-Link (Kasa) too - but with only one driver (not all the drivers for all the TP-Link devices that I don't have). All good thus far.


I feel like going from 2 TP-Link devices to 1 might have helped me now that I think of it...
Ugh maybe I'll switch that puppy to IFTTT control to speed things up... Maybe...
Or open more worm cans in the process...

I'm all good with just the switch driver

This helped with my hub performance as well. I changed routers for the purposes of using a VPN and didn't realize I needed to rebuild everything WiFi related. Which as it turns out means to remove and readd all Connect related apps for Sonos, SmartLife, Hue, Lifx because of all the changes the new DHCP did to changing IP addresses.

I also did as @stephack recommends here but didn't realize was to check All logs to watch for any errors. It turns out even though the system was operational it was so slow that I kept troubleshooting symptoms (ie Rules not functioning, devices not reporting, et) and not the real problem of bad apps due to WifI IP changes or drivers. Once I did this the system snapped back to life.

I still need to reserve IP's for devices once I know what best practices are. I think my Hue hub, all my Wifi Sonoff and H801 RGBWW controllers need reserved IP's based on their MAC addresses. I read somewhere @bravenel to not reserve the IP for my HE Hub though because it might interfere with updates notifications. I think I read that @mike.maxwell said it's a good practice to reserve an IP for Sonos devices.


Everything on my network has a reserved IP

With the exception of guest. I reserved all the devices IP at my router. This is much easier for me to manage and troubleshoot issue.