With this last update, my hub has started randomly locking up and I'm scratching my head as to why. My Hubitat hub is directly connected to my core switch (Ubiquiti US-48-500W) and I'm not showing any network issue. Attached is a screen shot of my logs just before the lockup all the way to the point where I physically reboot the hub. Any thoughts?
I thought it was just me. Tracking.
1 Like
What is device 996 and app 738? Those don't happen to be Hub Connect do they? Also, is app 1 the native Ecobbee app or the Ecobee suite?
App 996 is the Lutron Integrator and App 738 is Hub Connect. I've since disabled the Hub Connect app and no change. 
The Ecobee (now disabled) is the native app.
Thanks!!
Did your router go on the fritz around this time? I've never seen the Lutron telnet app lose connection except when I accidentally unplugged my hub from my router. It is probably the most stable app on my hub.
Same here! I'm running an enterprise network (mix of Cisco and Ubiquiti) and the Lutron Hub is directly connected to my core switch literally one swithport over from the Hubitat Hub. Review my network logs from last nights and no drops. My switch has been up for 162 days rock solid.
Huh...that is odd then. What I suspect is that something else was going on that isn't captured in the logs that caused the NIC on the hub to stop and that's why the lutron telnet got disconnected. This would also be the reason that the Ecobee app crashed...that's on the network connection as well. So, what you're seeing here in the logs is probably more a symptom than a cause. But again, that's just an educated guess. I would reach out to support at support@hubitat.com They have tools that will dive deeper into the hub's performance and might reveal something else that happened.
Also, tagging @bobbyD, in case that route is quicker.
Can you see in the switch logs if the port for your Hubitat went down? Maybe the ethernet port on the hub had a problem
Or.... Do you have logs of your DHCP server? Maybe there was an IP conflict.
Will do!
My Hubitat Hub has an IP reservation, so essentially a static IP address. I checked the logs and the port didn't go down until I unplugged the Hubitat Hub.
Still having issues, so I've opened a ticket with support. I will update this post once I have a resolution.
@seeharrison every get resolution on this?
Nope. It finally (magically) fixed itself. My guess is some update initially broken it and then another update fixed it. Needless to say Iām more cautious about updates now.
