馃殤 Fixes calculation for average processing time #82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The AdGuard Home API returns the value in seconds. To correctly convert that value into milliseconds, the multiplication should be 1000.
API result
I noticed this in Home Assistant. The AdGuard Home page showed my average processing time as 8ms, while the Home Assistant sensor (incorrectly) had 0.8ms for this value.
AdGuard Home
![image](https://user-images.githubusercontent.com/5155694/78284096-25647d00-751f-11ea-9777-1461a8e11f53.png)
Home Assistant sensor
![image](https://user-images.githubusercontent.com/5155694/78284124-31e8d580-751f-11ea-80c4-01732238a4dc.png)