Hub process slowdown after several days

Sorry for the troubles. I don't recommend "removing stuff", we understand it takes a lot of effort to set up a system just the way you want it. But when things go sideways, I do recommend disabling at least the last custom code you have added to the hub, to see if that is causing the problem. If you didn't add any new apps or devices, and you are not running some of the apps and drivers that are known to cause slowdowns in some hubs (but NOT all), such as Chromecast, Lifx, Echo Speaks, etc then please reach out to We would be more than happy to take a deeper look at your hub to see what else might be causing the problems you are currently experiencing.

If you don't know how to disable an app or a driver, please see "Disable Device Drivers" and "Disable Apps" sub-headings in the following documents:

Well, I finally broke down and deleted Echo Speaks. I was really hoping this new version would solve the hub slowdowns the old one was blamed for, but it does not. I could actually look in the logs and watch the cookie validation times increase throughout the day from 330ms to 2100 ms ( then reboot) back to 330ms and creep back up to 2000ms over a day and a half, so I knew it had to go. I put it on SmartThings, where it works great, and am using HubConnect to enable automations on HE. I have disabled echo speaks in the past in my search for what was slowing down my hub, but still experienced hub lockups and slowdowns with zigbee devices and the web ui. I didn't realize that NST manager was perhaps as much to blame for the problems. I deleted NST manager a couple weeks ago and noticed an improvement, but after deleting Echo Speaks the change is night and day. The web ui is amazingly fast (I had no idea that it could just snap between pages without any real load time), and zigbee devices respond the instant I push a button. BTW, there was also the netgear issue, which helped me as well, because my hub didn't respond this fast when it was brand new.
Thank you to the developers (and shepherds) of HubConnect and Homebridge-Hubitat-HubConnect: @srwhite, @csteele, and @dan.t for making great apps that allow the hub to really shine! Also thank you to @bobbyD, @bravenel, and @mike.maxwell for your commitment to being involved and responsive to the needs of the community and making a great product. Now that this problem is fixed, maybe I can figure out how to get mode changes to sync with Homekit.


Both Echo Speaks and NST manager are from the same author.

We're glad to hear that removing these two apps has resolved your hub slowdown problem.

1 Like

No offense to @tonesto7 and all of the work he has done on this, as his apps always worked well for me on SmartThings, and now continue to with HubConnect. I should have uploaded a screenshot of the logs to him, but the issue wasn't errors that were happening, it was just logging that showed the 20-minute check-ins to validate the cookie that tipped me off. I brought up a page of these logs by themselves and saw that as the validation times got longer, the hub got slower and slower until it was almost to slow to navigate to the reboot page.

1 Like

I don’t see a need for echo speaks anymore. Since you can create virtual contact sensors and expose that to Alexa. Then within Alexa create a routine to say whatever you want.

I’ve also got rid of MyQ and rely on HomeKit which I use all the time to trigger a vs on or off. That’s how I get two way communication not needing another app.

The only apps that remain is a virtual precense switch done by cobra (which I could remove too and make some rule machine rules to do the same thing) and watchdog.

That’s it. I haven’t had any slow downs in almost a week so far....

Don't want to thread-jack here, but I want to be sure that those who need to use Alexa devices for TTS are aware there's an alternative to Echo Speaks, namely @ogiewon's Amazon Alexa Text To Speech (TTS). I have used it pretty much continuously since switching to Hubitat (~6 months ago), and have never experienced any hub slowdowns that I can ascribe to it.

This has been mentioned before. I should point out that while it is clearly an option to consider (any may be sufficient for most needs), it lacks the flexibility offered by apps such as @ogiewon's Amazon Alexa TTS, including the capacity to use variables, repeat a certain number of times or indefinitely.


The variables are the reason I use it. Much simpler to set up, and can then hear the data points such as temperature, etc. I did it this way because I didn’t want to install another app on the HE (already using HubConnect for Homebridge), and I had a SmartThings hub laying around collecting dust when not updating zigbee devices.

1 Like

For me it's the repeats.

Being told once that the dryer is done and clothes need to be folded merely elicits a sigh from me. Repeating that message five times at 2 minute intervals is sufficient to rouse my lazy arse into action ..... :joy:


I am an amateur enthusiast who migrated to Hubitat from Wink around 6 months ago. I have really enjoyed puttering around with my Hubitat and I have amazed myself with how I have developed such an affinity for implementing various smart home devices.

Alas, as a 70 year old retired guy with too much time on his hands, I enjoy the darn Hubitat so much that I have developed this nasty habit of fixing things that are not broken. For instance, I too have noticed a response time slow down on many of my devices and have followed this thread with interest. I was especially interested in the comment about using a soft reset and immediate data base restore to perhaps speed up all processes. As I always do, I researched how to accomplish this and did so. Well, all hell broke loose - my Echos no longer responded to voice commands and when I finally got it to work, my TV came on instead of a lamp with an Echo voice command, lol. Being persistent, I rebooted , unplugged my Hubitat and I almost gave it mouth to mouth, for crying out loud. You know what? The system is working better than ever!

My two cents - keep going with the same business model and product development. It is nirvana for old guys like me and the sense of accomplishment when something works is wonderful and I don't have to think about my aging prostate at last!


You can do repeats. Just do it in rule machine to open the contact sensor over and over again.

1 Like

I discovered that a reboot is necessary after doing a soft reset and restore from a backup. The first time I did a soft reset and restore, I almost had a heart attack when I saw that all of my information was missing. Luckily I realized that the restore info hadn’t been loaded since the hub didn’t reboot afterwards.

This is a bug that we are aware of, and will get resolved.


Is the virtual contact working for you? I see the sensor change in the Alexa app, but it never says the message.

You setup a routine to say something on the state change

1 Like

I did that and the echo says nothing, I do get it when I run the routine from the echo app.

I’m going to get to the bottom of this but I might need some other devs to help.
I’m just not seeing any flaws and some fresh eyes on the code since I don’t see the issue on my hub. It’s much more complex to debug.
If anyone is willing just reach out to me on here and we can chat on the Echo Speaks slack.


Now are people referring to the old ES or the V3 echo speaks ?


For me, performance hit when on ES, removed and performance went back to normal. I installed V3 and all is well... as it relates to performance



Ok.. Well that is definitely useful info. So V3 is not exhibiting the same performance issues as v2.

I just had some ideas to make things better for v3.1. It's annoying when it takes stuff like this to rethink an idea :wink:

I will push off some of the new zones app to v3.2 and release v3.1 this week.

1 Like

see i've had V3 installed since the 10/9/19 and have not noticed my automations / system slowing down. I have had no experience with V2 as it looked too big to tackle for me.
I get the usual/random motion lighting issues - but 99% of the time the fire rates have been acceptable for the last 2 weeks (I can only really measure slowness by the automations/browser response times).