Dedicated drivers change configuration parameters specific to the device they were written for so if you use them with other devices make sure you don't save the preferences or click configure because the device could stop working and then you'd have to factory reset it.
I've left it using the ported Fibaro driver for that reason.
Locked up again last night.
This now getting beyond a joke.
I go on holiday tomorrow and I have 2 choices now.
Quickly re-pair all my devices on to my ST hub or check everything twice a day to make sure everything is working.
This DID all start with 2.0.9 and RM3.
I'm not saying they are at fault but it is the only conclusion I can draw.
Is there going to be an 'In House' driver for the Fibaro Double Switches? FGS222 and FGS223.
Another option might be using the HubConnect app from @srwhite. You could connect your ST hub to Hubitat as a slave and share devices. You could then put the Fibaro devices on the ST hub and share them to Hubitat, then they work like they are connected to Hubitat, This might be fix for now until a better driver is out, and prevent you from having to switch every device back over. I had this problem with some devices, and have been using HubConnect and all works great.
Put a tp link wifi plug to reset remotely the hub.
I'm using a WeMo outlet to do this.
Thanks for the response.
Hub dead AGAIN. This really isn't funny anymore.
On my original ticket I was advised it could be 2 custom drivers causing it.
One device I have removed so it definitely wasn't that.
The second one I have asked questions about to @mike.maxwell but haven't had any response.
Glad I plugged my hub into a wemo outlet so that I can control it remotely.
I'm on holiday. I shouldn't have to check 4 times a day to make sure everything is working.
We are talking home automation. Not home automation that needs babysitting.
I figured out my issue I think. One night I noticed in the log that Alexa App was going NUTS (Builtin not the TTS). There were tons of throttling mesages from Amazon and my hub voice announcements were getting slow. I think I had Alexa Echo App not Alexa Echo Skill. I had always wanted to upgrade, but hadn't ever seen the option to install Alexa Echo Skill. Well I deleted the Alexa Echo App, and when I went to reinstall I saw the Alexa Echo Skill and instead installed it. I also pruned the list of allowed devices down to 20ish. Ever since then I've been a OK. My Alexa view of my house via the app is also more responsive.
That's interesting information.
I have disabled the Chrome cast integration (under guidance from support) and my hub has been ok ever since. Still early days but fingers crossed.
Just an anecdotal piece of info.... The other day when my hub slowed down to the point automation stopped, the only error in the logs was from the chromecast integration. There was just a single error in the log, so I didn't think much of it, but it was there...
Not saying that is what caused my hub to bog down, but based on the discussion above I thought I would mention it.
I have been thinking of moving all "LAN" style connections to my 2nd hub anyway, maybe I'll move Chromecast 1st when I have time next week.
I will say that I'm going to laugh my **** off if a native Hubitat created piece of code ends up being the issue - and not all the "evil user code".
Yes, I know that's immature and petty - what can I say? I'm flawed.
When my production hub was experiencing lockups about every 2 weeks, I went through the list and disabled/removed what I considered 'suspect applications'. Two of those were the Hubitat's Chromecast Integration (Beta) and the amazing Echo Speaks by @tonesto7 .
It is hard to say if either one of them was the cause, however my hub issues seem to be reduced. I am now running both of these integrations on my development up as I wanted to see if I could 'move the problem' as part of my troubleshooting. The development hub has not locked up ever. Of course, I really don't use it for much other than development, and it gets routine firmware updates/restarts as it is part of the beta program. So if the problem is a gradual resource exhaustion issue, it might take months on my development hub versus weeks on my production hub.
Recently, I enabled a feature on my Asus Router that collects WAN usage data by device. My production HE hub did not show anything unusual (i.e. very little data per day going to the WAN.) My development hub, on the other hand, showed a significant amount of data usage every day going to Amazon. I suspected Echo Speaks as the large data consumer and so I disabled it yesterday. You can see in the chart below the dramatic change in traffic as a result. This hub does not even utilize Echo Speaks (i.e. no TTS whatsoever) so I am not sure why there is so much traffic. Maybe it is trying to auto-discover new devices as they added to your Amazon account? Over the course of a full 24 hours, Echo Speaks on this one hub consumes ~500MB of total bandwidth for my 4 echo devices. Not a massive amount of data, but for folks with a monthly bandwidth cap it is something to be aware of. This could also consume a cellular backup WAN solution's data cap fairly quickly.
I am not pointing the finger at either the Chromecast Integration or Echo Speaks. I just wanted to add some more data to the discussion.
Not really fair Jason. They do label Chromecast Integration as Beta, and @chuck.schwer has said it probably should actually have the label “Alpha”. Really none of these guys have used evil to describe user created code, and have often gone out of their way to help with issues in user created code. They’ve also never said any of their code is perfect. They’re not putting themselves on a pedestal, so let’s not accuse them of looking down at anyone from a pedestal.
@ogiewon Thank you for the insight to your tests. I’ve been wondering about the Chromecast Integration Beta, but have not tried disabling it. I will do that now to see if things improve over the next week.
I must say I have suspected echo speaks of causing slow downs as well. I however like it so much I have been hoping it wasn't so. I plan on switching my chromecast stuff back to cast web api and likely going back to my telnet driver for Alexa tts and routine triggering.
My anecdote - I had some unexplained lock-ups. I had the original Hubitat Nest app. It was throwing some errors. I deleted it and installed the community app. No lock-ups since. It's hard to say if that was the issue as there have been regular reboots due to platform upgrades. I also have Echo Speaks and Chromecast installed.
My hub became extremely slow last night and motion lighting seems to have been the culprit. I hit a button to turn off the lights and they went into some kind of on/off loop for about 5 minutes until I disabled the motion lighting app which immediately fixed the lights. The web interface regained its responsiveness, but automations still had some lag, so I ended up rebooting it. It only made it a day and a half since the last lockup. The thing is, everything works great, (when it’s working) but I always see more delay with motion lighting on Hubitat than I did on SmartThings. I don’t understand why it’s not faster. Same motion sensors and lights.
EDIT: You know... You're right, probably not "fair". I thought it was "funny" though.
We appreciate the passion everyone has for trying to solve sources of Hub Lockups.
What we know is this:
- If we can reproduce it, we can probably fix it.
- We need to isolate apps and drivers users are using to determine where or what is the cause
- Bad code is bad code... No software is perfect, but we continually improve the hub core code to make sure we fix what we know are issues and what we can reproduce or observe as issues.
We have identified one significant bug in how network connections, under specific circumstances, caused the hub to stop working. We could not have found this cause without the help of the community. This fix will be available in the next release.
We continue to try to find root causes of lockups, freezes, slow downs, etc in our never ending quest to build the best hub out there.
It is basic troubleshooting to baseline and isolate potential sources of problems and determine what the cause is, what the steps to reproduce are and ultimately what the fix might entail and then make sure that fix doesn't break anything else.
When we ask you to disable (not remove) user drivers and apps, it's simply to get a baseline of the hubs operation. If the problem still exists, then we know it's not related to user drivers and / or apps.
We added the option to disable devices and apps very easily in the Web Interface to make this process much easier.
One simple process of troubleshooting is then cutting things in halves. Enable half of your disabled apps and /or devices and see if the problem returns. Continue cutting that half in half until you isolate and identify the potential root cause.
With lockups that are potentially due to time (typically memory leaks or resource issues, random events like 3rd party endpoints that don't respond, etc.) it's important to try to track down those causes. Some problems like a random lockups could simply be due to a power surge, or a rouge device flooding the network, etc. These are the hardest to track down, let alone reproduce or eventually fix.
When we have enough information to identify a cause, be able to reproduce it, we can then fix it. We have fixed many causes over the last 14 months and will continue to knock them out as we find them.
We are a dedicated team that actually uses Hubitat in our own homes, we use the hub's code editor to write our apps and drivers just like any community developer does. There isn't any magic answer to what users or user installed code can do to create issues, random lockups, unhandled exceptions, excessive logging or even loops that can drag the hub down.
We can not solve these issues without your help. Anything you can do to isolate, identify and reproduce the issues, helps us out tremendously.
Thanks for your patience and willingness to help out!
Thanks for spending the time on this it's appreciated.
The higher consumption for Echo Speaks makes sense as each device makes calls to amazon for device status and other data.
I really hope that they can track down the network connection bug because I feel very strongly that the random failures from Amazon requests are causing issues on the hub which are causing the slows.
I’m not offended or otherwise wounded in any way. But, Hubitat team finds that code they labelled beta has a problem. Where is the punch line?
Eh, funny is subjective.