I have never changed that, and mine is 11/30 for all devices.
I think in the beginning... there was no setting and it may have been fixed, then the per-device settings were made available so people could keep the data kept for particularly chatty devices at a reasonable level, or, on the flip-side of that, reduce the number of times the events need to be reduced (by having a larger value in the setting), thus reducing the amount of work the hub needs to do on a regular basis.
I think there may be a way to apply the same setting across all devices, but am not 100% sure on that...
(New defaults shown)
/hub/advanced/event/limit/11
/hub/advanced/deviceStateHistorySize/31
4 Likes
Does disabling the Hub Info Driver v3 on the Devices page deactivate the driver's use of hub resources? As in, it would be easy to bring back if needed, rather than removing and reinstalling.
Thanks.
You can certainly deactivate. Honestly though it really doesn't impact the hub much as it's simply reading what is already there on the hub.
1 Like
I was just wondering.
I would lengthen the refresh interval for the different attributes if you are worried about it impacting the hub’s performance. That way you can still keep tabs on certain things when you want without it being a hassle.
1 Like
Very late to the party.
Some of the things polled might actually be useful at fast (like 1/sec) polling.
Like Free Memory, CPU, Uptime, Temperature.
Does it make sense to add a feature to poll these things faster (a ms polling time vs. seconds)?
At 1/second polling rates, you can have very nice real-time looking fuel gauge type displays.
Even at 1/minute, it's still a very useful driver. Thanks for this!
EDIT: Is the value for DNS servers what you really want it to be? I'm seeing a string like (within the '...' is the string):
'[192.168.0.1]'
which you can't parse with JSON. Seems you want it to be
'["192.168.0.1"]'
Or is it my mistake?
You would beat the hub to death at that rate. Leave the default rates or lengthen them out. My poll rate on most things is 5 mins except my public ip which is once an hour.
2 Likes
@rlithgow1 is right in that you’d have negative consequences, but an additional factor is that the hub endpoint is a 5 minute average so really doesn’t make sense to poll it any more frequently than that.
DNS Servers is a list of DNS addresses not a JSON string.
2 Likes
If I click refresh, the freeMemory value changes every time.
I’m talking about 3 API calls 1/sec, not the whole bunch of them…
You’re right, it will force a recalc of the 5 minute average every time you ask for it, but it is a 5 minute average that is being reported.
That's also just the Mem that does that, the CPU only updates on the endpoint every 5 minutes.
Also if you really want a 1s poll to try, it would probably not be that hard to edit the code and modify one of the queues to be 1s.
Line 258 and 302 if you want to change poll1
Yeah but that would bang on the hub really hard wouldn't you think? I'm not sure I see the benefit of polling that much..
1 Like
I really don’t recommend polling that often, but if you want to guarantee that your memory drops rapidly that would be one way to do it.
7 Likes
2 Likes
Hi @thebearmay Im having an issue, after upgrading to 2.3.6.135 on one of my hubs, the html attribute shows null. The other hub html works fine, any ideas?
Try hitting Configure, if that doesn’t fix it check to make sure your template file is still in the File Manager.
First thing I tried. 
