my god, you are just a beginner mate 
I need the next generation but one C11 hub for what I'm trying to do.
Or some programming lessons.
1 Like
10M Jun 10 10:03 HubitatBackup_2020-06-10-1003.lzf
9.8M Jun 10 10:04 SecondHubitat_2020-06-10-1003.lzf
23M Jun 10 10:04 ThirdHubitat_2020-06-10-1004.lzf
1 Like
Including this 'leak' 
But don't bother pursuing this, what happens in Beta stays in Beta... especially true if that something doesn't make it out of Beta.
To summarize... Beta is where new stuff gets reviewed, presumably on Hubs that can afford the downtime. If something new doesn't get announced (aka coming out of Beta) can you predict why? If there's one thing the Hub being discussed in this Topic does NOT need is another shot at downtime.
1 Like
yeah, agreed. I'd like improved uptime and stability really, not more weird stuff thank you very much 
1 Like
Anyway, it's back up now. WIll see how it goes again for a while...2 steps forward, 1 (sometimes 3) steps back. One thing I'm seriously contemplating now is moving all my zigbee lights to my Hue hub. Its a significant piece of work to do this and then rejig all the rules. I really dont have the time or energy to be honest. I was thinking to move them to another HE hub but given the current cost and availability and the fact I have a Hue sat here running very little (but always rock solid), it probably makes sense. I'd prefer another HE hub despite all my issues because that way I dont need to poll to update the dashboard. But I think i will cut my losses and move them to Hue and see if that helps the hub load and the mesh quality.
What type of bulbs are they?
Gledopto zigbee. They've been faultless themselves, but they do create some issues with the Xiaomi motion sensors. I added 3 Ikea repeaters but it didnt really help. I get some motion sensors drop off time by time (say, 1 or 2 per week on average). Its weird that the buttons never drop. The door contact sensor rarely. It's the motion sensors that play up, drop off, or respond incredibly slowly sometimes. So i'd like to get the bulbs on their own network for sure.
WOW. I thought I was bad at 42.
1 Like
Yep, if they will pair with the Hue bridge, then I'd move them.
and... in all fairness to the Hubitat hub, the user assumes full responsibility for pairing non-standard, unsupported devices to the hub. I am NOT saying that these Xiaomi/Aqara devices are causing your hub to slow down. I have no idea what is causing that, nor your database backup to be 103MB!!!
I truly wish you the best of luck in figuring it out. 
Please, let us know if you ever find the smoking gun.
3 Likes
For the past 6 months, mine seem to be hovering between 18-24MB. If II go back to September, mine were 11M or so until I added a bunch of stuff between Thanksgiving, and Christmas.
I have close to 150 things listed in devices, I have 15 dashboards, a dozen or so Motion Lighting, close to 20 RM4 rules, and another that many Simple rules. I have about a dozen community apps, and countless community drivers.
I rarely if ever see slowdowns or errors. On the odd occasion that I do have issues, I am usually able to catch the error right away and correct it.
I have a hub that works. My database is 16mb. I have 104 active rules. Something seems very wrong with your database size. Maybe those images in your dashboard?
1 Like
Possible - I might be incorrectly remembering this, but I think @dman2306 may have encountered a large backup size due to images?
there are no images hosted on the hub, or music files. They are all on a Pi. I'm not using the files capability yet. Here are the last few daily backups, with the size dropping significantly after the soft reset...
I have a total of 147 devices, I would say around 50 would be virtual devices. Quite a lot of RM going on and many community apps. Maybe 10 or so dashboards, all limited to just the relevant devices of course. Maker API with maybe 30 devices hooked up through that and a custom dashboard listening on the eventsocket. So, yeah, its quite busy I'm sure. I'm not complaining really. For a 100 buck device I'm putting it through its paces, thats for sure. I'm just trying to find a solution that does what I need/want and I'm happy to buy a few more hubs or something bigger/better in the future in the pursuit of an end solution that works. As I've said above countless times, its a hobby and no one died yet, so no big deal (although the wife stubbed her toe in the dark tonight and isnt so happy with the whole motion lighting schenanigans).
so anyway, maybe I do qualify for the "huuugest HE database everrrrr" award so I can go to bed tonight having achieved something of note 
Its strange, my z-wave locked up yesterday and today after a good week of no issues
Oh wow.
Ok something to check. Are there any devices that kick off a lot of events. Power reporting etc.
If so try to just disable that stuff as a test and see if the db size drops after the next cleanup tonight.
My DB was always around 19mb. I then added some devices that added a bunch of extra events and it jumped to 30mb, which is still manageable for me. But at least I know where the extra data was coming from.
The cleanup at night should shrink it down though so I would check the size in the morning and then the evening and see if it differs significantly too.
Just an idea.
3 Likes
Mine was because I was having events created where the event value was an image so it was a lot of data.
1 Like
None that I'm aware of. No power monitoring at all. I will work my way back through my devices one by one I think and check them. The only couple of issues I could have is a freezer temp device where the battery has now frozen up and so it doesn't send a report anymore. I need to fish it out of the depths of the freezer if I can find it and get it unstuck. That always reports zero activity on device watch app of course. The other is an Iris fob where the battery is a very poor fit so it's not been registering any activity for days now. I think to remove that device too. That's it as far as I know for any funnies.
Edit - oh, I do have 1 Hubigraph temp/humidity graph for the fridge Xiaomi device. But my understanding is the browser client does most of the processing for this.
Sorry for misremembering that!
I'm not part of the Beta group, so have nothing stopping me from repeating a "leak". 
If I was part of the Beta group I would not be talking about it, would I?
Why things don't come out of a Beta can be any number of reasons, if that is due to instability or not only the one making the decisions truly knows.
With the issues seen here I would have tried it if given a chance, but that is probably not an option anyway.
Yes, most of the work is in the browser.
@Angus_M maybe support could help you look at the DB and tell you what is actually taking up so much space and maybe even clean it up a bit for you?
1 Like
