sparky8512
sparky8512
Assuming you're using one of the history-based data modes, which includes `usage`, sample period should not matter as long as it is less than the history buffer size, which is...
Hmmm... seems pretty suspicious that the router's reporting would be so close, but the dish-reported number is so off. My best guess is that the router (and website) is including...
I need to collect a few more days of data to confirm, but so far, it seems my router is underreporting data vs either what the dish is reporting via...
The exact command I'm using for this test run is: ``` python dish_grpc_text.py -t 60 -O usage_stats.csv usage ``` Then importing the data into a spreadsheet, converting the time from...
With a few more days of data, my dish still appears to be pretty close to the website reported usage stats. Here are the updated numbers (including days listed in...
I think it's datetime (in UTC), number of samples processed, end sample counter value, download usage, upload usage. You can output a CSV header using the `-H` command line option....
I don't think there's anything left to do on this, so I'm going to close it out. Feel free to re-open if you had any further questions on this topic.
`dish_grpc_mqtt.py` can publish the summary stats (with mode `power`), but it does not support publishing bulk history data.
This just looks like it's adding a blank file?
I'm going to assume this was just submitted in error....