Hub Recommendations

Welcome to Hubitat :wink:

I wish I had a solution, but mysterious slow downs like this are a major part of why the Hubitat integration thread on the Home Assistant forums has over 1k posts in it. What I, and many others, have found is that by offloading the automations from the Hubitat Hub into something such as Home Assistant, Node Red, or literally any other platform and using Hubitat for it’s radios will drastically speed things up and almost eliminate these issues. It’s also part of why if you spend any time on the Hubitat boards you’ll see people buying 2, 3 or even more hubs. The devs are adamant that it’s powerful enough, and I believe in theory they are right. But in the real world I personally feel the hub to be underpowered.

My advice, if you’ve got some hardware that’s on 24/7, look into node red as a jumping off point. Leave all your devices on Hubitat, but move this particular automation onto node red. If the slow downs go away, you can rule out an issue with the zwave network/radios.

1 Like

My Hubitat hub was brought to its knees by a jabbering sensor connected to my alarm system panel. I’m pretty sure that the sensors connect via a serial bus, with a baud rate less than 19,200. Calling the Hubitat underpowered is an understatement.

FWIW, I made the jump to HA over the winter holiday, and am not looking back…

So 2 of my troublesome switches simply set the lights they are connected to, to a low level when I push the Config/Favorite button. Could you show me a simple flow doing that? (I’ve seen the threads with some posted flows, but, understandably, they are all more complex than this, such as turning on lights if motion is detected, but only during certain times, etc.).

In thinking about this I often use the Config button late at night, and just before this I’ve typically told Alexa “Good night” which sets off an Alexa routine to tell my Harmony to turn off my entertainment system, turn off a few lights and to turn on 2 lights to a low level for 2 minutes. This “good night” routine doesn’t always work entirely, and I suspect that the commands might be coming too fast for Hubitat, even though I tried to build in some delays. I’m wondering if this might be the real culprit in that somehow Hubitat is getting hung up on it, so it takes forever to process something else, like a simple Config button push.

I haven’t kept track of it enough to really know if this only happens after that Good Night routine is fired. (And since it is late at night and I’m going to bed, I’m not firing up my computer to look at the logs).

But beyond that, I have another Red Dimmer that is only connected to the line, neutral and ground. When it is pushed once it is to turn on the light of an Inovelli Fan+Light. A double push is to turn on that light and a light plugged into an Aeotec Series 7 plug. A triple click is to turn them both on. This works great the majority of the time, but every now and then it doesn’t, or it works very slowly - even just turning on the fan light (i.e. just pushing the on switch once). The same thing can happen when we try to turn off those lights (with the corresponding 1 off push (1 “Held” in Hubitat parlance) turning off just the light of the Fan+Light, a double off click (2 “Held”) turning off just the table lamp (i.e. turning off the Aeotec plug) and a triple off push (3 “Held”) turning them both off. So there isn’t anything else running before it that should/could hang up they system like my Good Night Alexa routine.

BTW, that Fan+Light and the Aeotec 7 plug are in the same room as the hub, and the switch I’m referring to is just on the other side of the wall from the Fan+Light plug. For some funny reason the Fan+Light switch is running at 40 KBs while the switch on the other side of the wall is running at 100 KBs as is the Aeotec plug. Plus all 3 are connecting directly with the hub, so there shouldn’t be any issues of too much traffic going through other devices.

Do you think moving these automations to Node-Red would help?

It’s just so hard to figure out what is causing it, because these inordinate delays happen so randomly and I cannot do anything to cause them to happen for debugging.

I know this is sort of turning into a, “how do I optimize my network” thread but I’ll chime in briefly (I may separate the thread if it goes too crazy).

Anecdotally, I will say that when I moved everything off S2 encryption with Hubitat, that solved literally all of my issues. Before that, I experienced the same thing as you and it was so frustrating. I have a button next to my bed that I press that shuts down the house and it worked 50% of the time. Half the automations would work, but they’d work randomly. I’d press it multiple times but sometimes it helped, sometimes it didn’t.

As soon as I removed the devices and paired them without security, the automations worked every time, scene control was back to instant, and all was well.

I haven’t tried @BertABCD1234’s recommendation in updating the firmware but he’s on top of his game, so I’d give that a shot first before blowing everything up and starting from scratch as you’ll have to remove and re-add everything if you decide to pair without security.

I wish I could help you with an example flow, but it’s been forever since I’ve used any of the Hubitat specific nodes. After I used the custom component to bring my Hubitat devices into Home Assistant, I was hooked and ended up going full Home Assistant. And the Home Assistant node set is completely different than the Hubitat set, plus there’s a specific set of Inovelli nodes designed to work with Home Assistant that makes it even easier.

I’d suggest making a post on the Hubitat board for help with a specific flow. I just quickly browsed the mega-thread they’ve got on there and there seems to be an example HERE that may get you started. Somebody was looking for an example flow with an Inovelli red when button X is pushed, lights go to 25% and when button Y is pushed it goes to 100%. You’ll just have to change the button for your config button.

My Hubitat hub would almost grind to a full stop anytime I ran my goodnight routine. It was a pain but what I ended up doing was a series of checks to reduce the amount of commands being issued on the network. Is light A on? Yes - turn off, no do nothing. Is light B on? Yes - turn off, no - do nothing. etc… etc… etc… This was a million times easier in node red than it was with Rule Machine I can say that. So if this is where you find it’s struggling, then yes it will 100% make things faster.

I have had no security on anything except my front door lock for months - so that hasn’t helped me at all. In fact, tonight my daughter told me the outer switch to turn off the Fan + Light light didn’t work. I checked the logs right away but didn’t see it in the past or current logs. I then pressed the switch and it turn the light off. So who knows why?

So Monday night (actually Tuesday as it was after midnight), I went to turn on my master bathroom shower/tub lights using the Config button. Nothing happened. I then went back and checked the logs. As you’ll see from the screen shot the switch did report in at 12:09:28. I’m not sure if I pushed it then or it was just doing a periodic check-in. The last action for this device on the logs occurred 20 seconds later. I’m not sure if there was a 20 second delay in implementing the 7 push or for some mysterious reason it just took forever to turn on. I can’t tell as I don’t know how to read the logs. When I went back to the bathroom the lights were on.

So what would cause the delay from the time I pushed a button to it reacting?

Here are all the events that happened between those 2:

Should I be turning off the metering reports for all my devices? If so, how do I do that? In Hubitat is that Param 19? 19. Periodic Power & Energy Reports Time period between consecutive power & energy reports being sent (in seconds). The timer is reset after each report is sent. Range: 0…32767 Default: 3600.

If so, would setting it to zero mean to turn it off or is that continuous?

BTW, I did update the Hubitat Z-Wave firmware a couple of days ago. Per their instructions to check the version it says I am running:

VersionReport(zWaveLibraryType:7, zWaveProtocolVersion:7, zWaveProtocolSubVersion:17, firmware0Version:7, firmware0SubVersion:17, hardwareVersion:1, firmwareTargets:1, targetVersions:[[target:1, version:7, subVersion:15]])

it is interesting that I got an email from Inovelli telling me “There have been many problems with the 700 series controller chips that are in several Z-Wave products, but Silicon Labs may have figured it out” and suggested I was sure to have updated the Z-Wave Firmware for the Hub. As you see above, I did that. However, the update had the opposite result as many of my Inovelli Red Dimmers got faster, and some much faster, from 9.6 to 100, but 2 of my Fan + Lights, which have 700 chips vs the 500 chips in the Red Dimmers, got much slower going from 100 to 9.6. This seems particularly disturbing to me as one is in the same room as the Hub so I have no idea why it not only slowed down, but also no longer is connecting directly. Here are before and after screen shots:

This is the one in the same room as the hub:
Before:

After:

Before:

After:

This is a Fan + Light that was, and still is, slow:
Before:

After:

This is not a 700 chip, but is an Inovelli Black with scene control.

Before:

After:

1 Like

I’m not sure what email you’re referencing… I don’t recall sending out any emails. Did you mean Hubitat?

Here is the email I was referring to from Inovelli Support:

Header:
Re:[## 23578 ##] Article feedback - Troubleshooting: Dimmer or Switch is Sometimes Slow to Respond In Home Assistant

Body:
Hi there, can you make sure that you have updated the Z-Wave firmware on the Hubitat hub? There have been many problems with the 700 series controller chips that are in several Z-Wave products, but Silicon Labs may have figured it out.

Settings > Z-Wave Details > Update Z-Wave Firmware

Here is some info on the bug:

Eric Maycock
CTO | Inovelli

Ah got it - a support email. I thought you were referencing a mass marketing email or something.

1 Like

A properly laid out zwave mesh network will function perfectly fine at 9.6kbps.

It’s been a few years since I’ve really looked at Hubitat logs, so one of the HE guys may be better suited for this.
But what I’m seeing from your first screenshot is that the scene command (config button) was received by the hub at 12:09:28 and the command sent to the light which turned on at 40% at 12:09:49. Which to me says the processing of the automation in between took 21 seconds.

1 Like

I know I’m asking the obvious, but did you heal your network after the firmware update?

Agreed that it seems hub-automation based delay, not device-based delay.

. . .

No as @bcopeland said it should not be necessary.

:eyes:

1 Like