I get a 404 on ../cpuInfo (looked at it the other day). The GC will run on its own periodically, so adding an additional run may or may not free up any memory at the time of the run.
If you really want to experiment, the endpoint to change GC frequency is /hub/advanced/intervalBetweenGCs/123, with accepted value range of 30-300. Default is 100. I suppose the utility of setting it higher or lower depends on what exactly is running on the hub, but don't expect to get a lot out of it.
No. I've added a few metrics for both apps and drivers on Logs page, and will likely expand on it, though.
8 Likes
What's the interval measure, second,minutes,...?
It's seconds.
3 Likes
Perhaps not; two wrongs not making a right, etc. But...bad behavior erodes / avoids building trust. Lack of trust leads to people looking for security in other directions, among geeks often by acquiring information.
The very thin documentation here, combined with the (seemingly best option) advice to look at the previous version of a competing product, is also relevant. We need information to use this thing.
And possibly a mix of users with lots of software experience and users with none (and every gradation in between) leads to some people being pretty casual about what they'll try and rarely getting into trouble, and maybe being kind of optimistic about what we recommend 
2 Likes
I said something along those lines almost a year ago ...
Documentation: when will we get a proper one?
3 Likes
Yeah, that does seem to be the big shortfall here. Heck of a nice group of users around these forums though!
1 Like
Yes, the community saves the day.
However, we canāt ignore the availability of the staff - always ready to help. But sometimes I feel uncomfortable to ask questions that I know are trivial but I canāt find the answers by myself, even after spending hours trying. Itās frustrating.
I developed an app & drivers for the Nuki Smart Lock and I couldnāt remember the last time I took so long to get along with a platform. Itās tiresome too.
Well, thatās what we have and, to be honest, HE really is a great product. Letās hope that, someday, a good documentation joins it!
3 Likes
Haven't actually updated a page, but it does look like users who create an account on the docs.hubitat.com can update things in the wiki. I get the edit page, it would be weird to let me have that and then forbid saving the result. So far I don't feel like I understand any of the missing things well enough to try to explain them to others.
Oh! Yes, the active participation of staff is very useful, I think. Not sure which of the notations that appear by forum user names represent staff -- all of them? But clearly some of the people who have helped me are staff, from credits on other bits of code and such .
No. I have done several updates, but the updates always sit for months without getting approved, and then they just disappear without ever being approved.
They are reviewed. We do accept changes that pass review.
1 Like
Interesting. Just as one example, on the list of Compatible Devices, the driver listed for the Aeotec Recessed Door Sensor 7 lists a driver (Recessed Door Sensor 7) that has not been available for about a year. I inquired in the forum when it became āDeprecatedā, and was told by Mike Maxwell Bobby Dobrescu that the driver had been superseded by the Aeotec Door/Window Sensor 7 Series driver. I edited an appropriate change to correct the Documentation, the change was never approved, and eventually disappeared. Itās still wrong, a year later.
I no longer suggest any changes because itās not worthwhile to waste my time trying to improve the documentation. The courtesy of an explanation why the changes were rejected would have been nice.
1 Like
Changes are not approved in the sense that your edit is going to be added verbatim. They are incorporated through our own editing process. Most posted changes are not in the same style, or wording. So they are rewritten. Unfortunately, there is no feedback mechanism available to us when we do this.
As for this particular change, I will pass it on.
2 Likes
My suggested wording in this instance had the exact same wording and style in the driver column as is now (correctly) shown for the Aeotec Door/Window Sensor 7, which uses the same driver. It wasnāt a major editorial change.
Apologies for this. Looked back in the rejected list and saw there was no reason it should not have been approved as it was submitted. It was a mistake to reject the change, as it could have been added directly.
The way the wiki contributions work right now isn't great. This is how it's presented, with no option for feedback.
[Approve Approve all . . Reject Reject all] . . [Mark as spammer]
In this particular instance Approve was the correct choice and it wasn't selected. Sorry about that. Discouraging contributions to the Wiki is certainly not the intention and we will introduce some changes to help improve this.
Often users will submit, but won't list the same names they use in the forum, so attribution isn't possible in those cases. That wasn't the case this time and your correction has been made. Thanks for submitting it and helping to improve the Compatible Devices List.
11 Likes
Thanks. I wasnāt looking for attribution, just trying to help improve the documentation.
7 Likes
From another thread these will let you adjust the #of events for your devices as well as the the state history size
I just tried these commands and I get an error 404 back and the value doesn't change.
Am I missing something or does this no longer work?
I got the same error when i initially tried those endpoints, but i tried in a few browsers and eventually they took properly. Not quite sure why or how i got it to work, but it did at some point..
Depending on how many devices you have, it may take a bit to complete (when you dont get the 404 error), so make sure to keep that tab open until it completes processing and gives you an output status message.
Thanks for the advice. I get the error almost immediately. Will try different browsers and see what happens.
EDIT: I was using chrome. Tried incognito mode and Firefox. Still no joy. 
