Delayed Telnet commands Hubitat - Lutron integration

It was on, I turned it off last night. Still getting delays today. Maybe I'll try a soft reset next? I'm out of ideas other than that.

Would love some help from @support_team - I believe I've done enough testing to show that something is up on the Hubitat side, but I don't have any additional resources to find out what. Is there anything I can do to get some support here?

Interesting....installing now

Well that didn't fix it. Still seeing delays. Tagging @support_team again. Can anyone help?

Tagging @support_team again. Is anyone there? Does anyone look at these threads? I'm willing to buy a new hub if you think the faster processor would help...

Any response at all would be appreciated.

Did you ever try this?

That was to attempt to test if there was interference by removing potential sources of interference. Instead of that I bought an RF receiver to directly check for interference, and found none.

is it possible to add another bridge integration to a development hub that has little or nothing else running on it?, see if these delays also exist on that hub...

1 Like

I have an unused C-4 hub in a drawer that I could use. Would that work, or is that going too far backwards?

should be fine, make sure it's updated to the latest platform version.
I have a C3 still in production that I keep updated without any issues.

1 Like

Ok cool, I'll get that going today and report back.

1 Like

@mike.maxwell Ok I have the Lutron connections set up on the dev hub. Shared out 10-15 devices that are controlled by motion or contact type automations to the main hub using hub mesh.

I'm still letting the automations themselves process on the main hub, then command the Lutron devices on/off through hub mesh to the dev hub. Is this sufficient for testing? Don't think I need to move the automations over to the dev hub also but wanted to double check.

To completely eliminate the production hub from the equation i would add the automations to the dev hub, then disable or pause them on the production hub.
now if you were able to duplicate the delay issue on the production hub simply by activating a given device, then there wouldn't be any reason to move any automations over, I don't know if that was the case or not.

1 Like

Haven't been home much but so far I haven't seen any delays after moving Lutron to the C-4 hub. The monitoring continues....

1 Like

Are you still running the automations on tour main hub?

Yes they are still on the main hub, haven't had a chance to move them over yet.

i also notice delays from initial connect to data flow on my telnet driver for apc smart ups.. i think it is doing some sort of dns (probably reverse) lookup as i use ip before it actually connects.

Day two down, no delays. Automations still running on main hub, only using the dev hub for the Lutron telnet commands.

1 Like

I find it really interesting that the Hub Mesh HTTP Post commands are not delayed from the main hub, but the Telnet commands appear to be. I'm sure there's a rational explanation.

Another day with no delays. @mike.maxwell should I just plan on running this way indefinitely? If so I'll move the rest of the Lutron devices over to the dev hub and remove the integration from the main hub. Also can do more testing if you'd like to dig in more.

its up to you, but sometimes its not worth arguing with something that works

2 Likes