Need help with refactoring charting for a fork of a module.

[jwilson5607]

@sdetweil, thank you. I thought I had copied the right code (it was a late night). Here is what is in my code currently:

 //heat
                if (this.hist.data[i].sum_auxiliary_heat_1 > 0) {
                    heatRuntime += this.hist.data[i].sum_auxiliary_heat_1 / 3600;
                }
                if (this.hist.data[i].sum_auxiliary_heat_2 > 0) {
                    heatRuntime += this.hist.data[i].sum_auxiliary_heat_2 / 3600;
                }
                if (this.hist.data[i].sum_auxiliary_heat_3 > 0) {
                    heatRuntime += this.hist.data[i].sum_auxiliary_heat_3 / 3600;
                }
                if (this.hist.data[i].sum_compressor_heat_1 > 0) {
                    heatRuntime += this.hist.data[i].sum_compressor_heat_1 / 3600;
                }
                if (this.hist.data[i].sum_compressor_heat_2 > 0) {
                    heatRuntime += this.hist.data[i].sum_compressor_heat_2 / 3600;
                }

                //cool
                if (this.hist.data[i].sum_compressor_cool_1 > 0) {
                    coolRuntime += this.hist.data[i].sum_compressor_cool_1 / 3600;
                }
                if (this.hist.data[i].sum_compressor_cool_2 > 0) {
                    coolRuntime += this.hist.data[i].sum_compressor_cool_2 / 3600;

Since I am using the same data set as the results from postman (results via the API call), I SHOULD get something - i THINK. However, I don’t see it loading the screen at all, and nothing showing that it crashed or something similar. My fork is found here if that makes looking at it easier: https://github.com/JWilson5607/MMM-Beestat

[sdetweil]

@jwilson5607 open the developer window, ctrl-shift-i, select the sources tab and find your module and filename I the left nav.

put a stop (click line number) on the code you just posted, and Ctrl to reload the page. code will stop there and u can examine the data structures,
just mouse over the words …

[jwilson5607]

@sdetweil was able to get it tracked down to requesting:https://api.beestat.io/?api_key=0f3499eeb0f984dfdff55f8dd7c23eb4fbdee6b2&resource=runtime_thermostat_summary&method=read_id&arguments={“attributes”:{“thermostat_id”:undefined,“date”:{“value”:“-undefinedundefined”,“operator”:“>”}}}

So I am now diving into that section. This is equal parts frustrating and elating. Thank you for pointing me in the directions you have.

[sdetweil]

@jwilson5607 glad u are making progress

[jwilson5607]

@sdetweil I’m packing it in for a day or two, give my brain a moment to relax. I verified I am getting in my URL properly (via output to the logs and that I am getting in a 200 response code via the console logs as well. However, its not parsing the data into the chart, and thats the part I was hoping would work with the sum_xxx_xxxx I added to match the json results from the GET call. If you have any ideas or places to look to understand it better as to why its failing, I would certainly appreciate it, if not - I do appreciate all the suggestions thus far.

[sdetweil]

@jwilson5607 i forked the repo…

so THIS will drive you NUTS…
I don’t have a good api key yet

the api doesn’t return an error if there is an error… it returns 200 (good)
and THEN u have to check the results for the actual status…
sloppy

MMM-Beestat: request response error=null statusCode=200
[05.05.2022 08:05.20.470] [LOG]   {
  "statusCode": 200,

   // my comment   see status is 200 (good)
  // but body.success=false, and body.data .error_message="API key is invalid.",

// BUT it 'is' JSON, so the parse is successful...  just not any data u are expecting
  "body": "{\"success\":false,\"data\":{\"error_message\":\"API key is invalid.\",\"error_code\":1003}}",


  "headers": {
    "date": "Thu, 05 May 2022 13:05:20 GMT",
    "server": "Apache/2.4.29 (Ubuntu)",
    "vary": "Accept-Encoding",
    "content-length": "82",
    "connection": "close",
    "content-type": "application/json; charset=UTF-8"
  },
  "request": {
    "uri": {
      "protocol": "https:",
      "slashes": true,
      "auth": null,
      "host": "api.beestat.io",
      "port": 443,
      "hostname": "api.beestat.io",
      "hash": null,
      "search": "?api_key=12345667&resource=runtime_thermostat_summary&method=read_id&arguments=%7B%22attributes%22:%7B%22thermostat_id%22:0,%22date%22:%7B%22value%22:%22-3%20month%22,%22operator%22:%22%3E%22%7D%7D%7D",
      "query": "api_key=12345667&resource=runtime_thermostat_summary&method=read_id&arguments=%7B%22attributes%22:%7B%22thermostat_id%22:0,%22date%22:%7B%22value%22:%22-3%20month%22,%22operator%22:%22%3E%22%7D%7D%7D",
      "pathname": "/",
      "path": "/?api_key=12345667&resource=runtime_thermostat_summary&method=read_id&arguments=%7B%22attributes%22:%7B%22thermostat_id%22:0,%22date%22:%7B%22value%22:%22-3%20month%22,%22operator%22:%22%3E%22%7D%7D%7D",
      "href": "https://api.beestat.io/?api_key=12345667&resource=runtime_thermostat_summary&method=read_id&arguments=%7B%22attributes%22:%7B%22thermostat_id%22:0,%22date%22:%7B%22value%22:%22-3%20month%22,%22operator%22:%22%3E%22%7D%7D%7D"
    },
    "method": "GET",
    "headers": {}
  }
}

I changed your request like this in node_helper to get this info on the console

request({ url: url, method: 'GET' }, function (error, response, body) {
        console.log(self.name+": request response error="+JSON.parse(error)+" statusCode="+response.statusCode)
          if (!error && response.statusCode == 200) {
            console.log(JSON.stringify(response,null,2) );
            var result = JSON.parse(body);
              self.sendSocketNotification(notification, result);
          } else {
              console.log("MMM-Beestat : Could not load data. error="+JSON.stringify(error));
          }
      });

and then i looked in the dev console just to see
i

[sdetweil]

@jwilson5607 i changed the node_helper like this … I sent a pull request

accept it and this will be added to your instance, then on pi, git pull to get that update locally
restart magic mirror

  getData: function (notification, url) {
      var self = this;
      console.log('requesting:' + url);
      request({ url: url, method: 'GET' }, function (error, response, body) {
        console.log(self.name+": request response="+JSON.parse(error)+" statusCode="+response.statusCode)
          if (!error && response.statusCode == 200) {
            var result = JSON.parse(body);
            console.log(JSON.stringify(result,null,2) );
            if(result.success==='true'){
              self.sendSocketNotification(notification, result.data);
            } else {
              console.log(self.name +" api request failed =>"+ result.data.error_message)
            }
          } else {
              console.log("MMM-Beestat : Could not load data. error="+JSON.stringify(error));
          }
      });
  },

[jwilson5607]

@sdetweil I see the data flowing into the logs now (I think it would be ok to comment out the console.log portion of this later on when I start parsing longer stretches of time). Thank you so much for looking at this! However, its now changing the title of the chart to Ecobee Runtime, and just sticking on loading… in the chart area.

I don’t see any reference in the mmm-beestat.js file that should put this there for the title. I have chart_title defined in the code and called via this snippet here on 118:

title: { display: true, text: this.config.chart_title, padding: 5 }

It also never displays the data. I use PowerShell for my day to day scripting work (IAM Systems Engineer) and Javascript is a whole new beast to me (one I am having difficulty adjusting to working with), but I know order of operations can be important. My guess is that it is not in this case, but unsure.

I THINK its related to the getdata function and specifically how its treating the socketNotificationReceived potion of this.

 getData: function () {
        var url = this.config.url + this.config.api_key + '&resource=ecobee_runtime_thermostat&method=get_aggregate_runtime&arguments={"ecobee_thermostat_id":'+this.config.ecobee_thermostat_id+',"time_period":"'+this.config.time_period+'","time_count":'+this.config.time_count+',"group_by":"'+this.config.group_by+'"}';

        this.sendSocketNotification('beestat_runtime', url);
    },

    socketNotificationReceived: function(notification, payload) {
        if (notification === "beestat_runtime") {
            this.hist = payload;
            this.loaded_history = true;
        }

Is this good or should it be different here? I see the original code is referencing in the node_helper file:

self.sendSocketNotification(notification, result)

And you updated it to result.data… In the received section it references payload. Would changing this to result be whats needed here?

Let me reiterate again how much I appreciate your patience and assistance.

[sdetweil]

@jwilson5607 1st… you never showed your config.js ( without the apikey) , so I don’t see your title string

console.log()… I usually add a if(this.config.debug) in front so you can turn them on when u need it via config.js
add a debug:false, to the beestat.js to set it to false by default.

as for title… did u use the debugger in the dev console… you could stop right there to see if the values are what you think they should be

‘payload’ is just a idea name…

its the data in the notification, ie the payload

doesn’t matter what its called on either side… use whatever term works in your head

payload is just generic

in got this notification, id = 1st parm, and the data/payload of the notification is in the 2nd parm…

you have loading cause the code does this is getdom()

        if (!this.loaded_history) {   // if data not received yet
            outerWrapper.innerHTML = this.translate("LOADING");
            outerWrapper.className = "dimmed light small";
            return outerWrapper;
        }

but here is where this.loaded_history is set to true

socketNotificationReceived: function(notification, payload) {
        if (notification === "beestat_runtime") {
            this.hist = payload;  // yay!!  we got some data from helper, save it
            this.loaded_history = true; // indicate we  got data so getDom() will work
        }

that just says hey, if I get socketnotification events, call here
and if the id string is “beestat_runtime” then
save the data (payload) in the variable this.hist

on the send of result.data, you only expected the DATA on the beetstat.js,. so that is what I had sent…

using the debugger will REALLY make this a LOT easier… cause u will see the data as u process it…

[sdetweil]

@jwilson5607 I don’t have my apikey yet… so only get error