Runtime per degree day (moving)

Feature Requests
1

Really enjoying the new Degree Days view in the Thermostat Summary. Thanks for adding that!

One thing that I’d like to see is runtime per degree day over time. For example month on the X axis and runtime per degree day for that month on the Y axis. It would be great if it could be grouped up the same way as Thermostat Summary (by day/week/month/year).

I think this would be a good way to visualize how a change in settings affects runtime, normalized by degree day.

Alternately I’d take an option to export the data from Thermostat Summary, which would let me plot it myself without having to bin up the runtimes and calculate degree days.

2

I agree with this request. I think this is more useful than the current new “Degree days” graph in the Summary, though I wouldn’t mind having “runtime per degree day” in addition to it.

3

Good news is that I do have this data. Beestat generates profiles weekly, and runtime per degree day is part of that profile. All historical profiles are stored - there’s just no way to access them in the GUI today. If you’d like the info I can probably show you how to access it; it would just be up to you to parse and graph it until I make it available in beestat.

4

Sure. If you have the data I’d like to take a look.

5

Press F12 to open the console inside beestat, then paste this code and press enter. It should download a CSV of all of your historical profiles.

var rows = []

rows.push([
  'thermostat_id',
  'date',
  'profile'
]);

new beestat.api()
  .add_call('profile', 'read_id')
  .set_callback(function(data) {
    Object.values(data).forEach(function(profile) {
      rows.push([
        profile.thermostat_id,
        profile.date,
        '"' + JSON.stringify(profile.profile).replace(/"/g, '""') + '"'
      ]);
    });

    var csv = 'data:text/csv;charset=utf-8,';

    rows.forEach(function(row) {
      csv += row.join(',') + "\r\n";
    });

    var encoded = encodeURI(csv);
    window.open(encoded);
  })
  .send();
6

Thanks. That seems to be working. Since temperature profiles use the last year of data, is it correct to be thinking about this as a 1 year moving average? ie, The point labelled 2023-12-05 includes data from 2022-12-05 to 2023-12-05.

image
image796×393 12.1 KB

I was also able to use the raw data to get a little closer to what I want. This is ugly but shows runtime per DD grouped by week.

image
image782×366 6.54 KB

7

Yes, that is correct. I’m not sure I follow your second chart - can you explain that one more?

8

In the second: The X axis is weeks and the Y axis is runtime per degree-day for that week. So any given bar represents runtime per degree-day for a 7-day period. ex: One bar is 11/5-11/11, the next is 11/12-11/18, etc. Basically the same values in the current Thermostat Summary with some math (runtime divided by degree-days, instead of independent runtime and degree-days).

1 Like