DaveL17 wrote:I will take a look at this one as well, but I want to make sure that we're on the same page.
The duration setting will only affect CSV files that are managed by that specific CSV engine device. For example, if you want some data to be 72 hours and some data to be 96 hours, you should use separate CSV devices for that.
When you've made a change to the duration value for a specific CSV engine device, you'll need to wait for it to refresh the data on its own. In this case, you have the engine set to refresh at 15 minute intervals, so you'll need to wait for the next 15 minute refresh to take place (the plugin should not reset the clock on when this scheduled refresh is set to occur.) Forcing a refresh of the chart will not have an effect. This is intentional so that the interval is maintained between observations. A later update of the plugin is going to allow for the duration setting to also be set for each chart--regardless of how much CSV data is in the file.
If, after waiting for the next refresh, the data still aren't appearing as you'd expect, let me know. This is working for me on my development environment, but that doesn't mean that it's working on your setup.
This is not an issue - I can work around these so no priority at all.
I run three CSV engines -
Main 192 obs, 48 hrs, 900 refresh
Motion (just started it) 4320 Obs/ 72 Hr Duration, 60 Refresh
Mini 12 obs, 0 Duration, 900 refresh
I only added the Duration today - hadn't noticed it before. Normal not an issue as the obs occur and it does the job - the Duration was interesting as I thought (hoped) it would make the graphing better when a failure occurred. Not a problem within 48 hours works its way out on it is own.
The Duration setting has had a couple of hours to reflect..
Again not an issue - worst comes to worst I rebuild the graphs again from scratch - that normally fixes these kind of issues. Not an overly time consuming problem - getting pretty quick at doing them now