your new temp code broke my temp display stuff, fixed it and was able to remove a now superflous fx.
change the wording and code so the schuduling input description reflects updating the html attribute as well. Also added the call from the scheduling fx to actually update the html attribute.
had to add an additional update to force it to update the formatted uptime as well when the sched. fx runs.
You may also want to create a dedicated thread in the community for this. It would probably help it reach more users and keep the discussion focused in its own thread.
I did almost the same thing as I was playing around with this (my first attempt at groovy). I found some code that did the days/hours/minutes/seconds conversion and adapted it.
Uptime Formatted
def convertSeconds(int secondsToConvert) {
long millis = secondsToConvert * 1000;
long days = TimeUnit.MILLISECONDS.toDays(millis);
long hours = TimeUnit.MILLISECONDS.toHours(millis);
long minutes = TimeUnit.MILLISECONDS.toMinutes(millis) % TimeUnit.HOURS.toMinutes(1);
long seconds = TimeUnit.MILLISECONDS.toSeconds(millis) % TimeUnit.MINUTES.toSeconds(1);
hours = (hours - (days*24))
String format = String.format("%02d d, %02d h, %02d m, %02d s",Math.abs(days), Math.abs(hours), Math.abs(minutes), Math.abs(seconds));
return format
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.
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
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!
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.