Just last night one fuse died because several deviced maxed out at the same time.
If I have high peaks it could drastically affect how I should make the design. I am re-designing the internal energy grid and need to know how much power is used for each and every device in different scenarios. It’s great that I can export the statistics and see it in Excel, but I miss the power peak info. It works very well, but I sorely lack the information about peak power used. I have a VOLTCRAFT SEM8500 Energy consumption meter.
#Peakhour 4 per device how to#
PeakHour will remain accurate as long as large amounts of data aren't transferred while it is stopped.New to Home Assistant and I am trying to figure out how it works.Īt the moment I haven’t installed a HA-system yet, but I am planning on how to do it. If that is not possible, you will get most accurate results if there aren't a lot of devices using your Internet connection whilst PeakHour isn't running.
#Peakhour 4 per device install#
Install PeakHour on a machine that is always on.Simply put: the best way to ensure accurate usage is to choose a router that supports High Capacity Counters. If a device supports High Capacity Counters, PeakHour will detect and use them automatically. Most enterprise-grade routers, servers running net-snmpd, open-source firewalls (such as pfSense). High Capacity counters are supported by some (usually higher-end) SNMP devices. PeakHour can be stopped for a very long time before any usage inaccuracy would be noticed. Due to their increased size, High Capacity counters roll a lot less frequently. The solution to counters rolling over is High Capacity Counters. If you wish, you can disable Usage Estimation in Advanced options. This is not as accurate as measuring directly but it will get close in many instances. In Usage Estimation mode, PeakHour will attempt to estimate the usage while it was stopped by using other counters available to it. If the counters do roll, the next time PeakHour is started it will drop into Usage Estimation mode. If the counters DO roll over while PeakHour is stopped, it's becomes impossible for PeakHour to know how much data was transferred during that time the counters could have rolled multiple times but we have no way of knowing how many times exactly.Usage will be calculated accurately as if PeakHour had been running the entire time. If the counters DON'T roll over while PeakHour is stopped, there is no problem.
If it's stopped for a period of time and data is still being transferred, things can happen that are beyond yours and our control: While PeakHour is running, it does not matter if the counter rolls over PeakHour is only concerned about the change in the counter's value, not the absolute value. The question is: how does this affect usage monitoring? In practise, it means each counter can only go up to 4,294,967,295 bytes or (~4GB) before it resets or 'rolls over' to zero and starts again. On most SNMP routers and all UPnP routers, these counters are only 32bits long.
Every router that is capable of being monitored by PeakHour keeps a running count of the total number of bytes uploaded and downloaded. PeakHour queries these counters regularly and uses them to calculate how much data is being currently being transferred (the transfer rate) as well as the total data transferred (usage).
0 kommentar(er)
