@nbrenn

you are overwriting the innerhtml of the wrapper

You probably need something like this installed then : https://github.com/sidorares/node-mysql2/blob/master/README.md

But more than that I don’t know

@nbrenn the easiest solution without messing with the css around is to create a second module, which is litening on the broadcasts you will send with the data in it from your module you already have

Hi all,

The E-Monitor API specification has a listing of the supported API methods (page 3), like authenticate, deauthenticate, getCurrentData and so on.

I’m not really sure where to go from here, as far as developing a module based on the API specification. Below, I have some of the very basic structure of the module, but I feel like I am out of my league when trying to write my own module.

Module.resgister (“MMM-Emonitor.js”, {
},

getStyles: function() {
},

start: function() {
},

getDom: function() {
},

// And then the EMonitor methods below:
authenticate: function() {
}

deauthenticate: function() {
}

getCurrentData: function() {
}

//… and so on down the list of the supported API methods

Thanks for the responses, guys.

The E-Monitor API specification has a listing of the supported API methods (page 3), like authenticate, deauthenticate, getCurrentData and so on.

Aside from Module.register, getStyles, start: function(), and getDom, are these methods listed in the API specification the ones that I will use as functions in my code? For example:

Module.resgister ("MMM-Emonitor.js", { }, getStyles: function() { }, start: function() { }, getDom: function() { }, // And then the EMonitor methods below: authenticate: function() { } deauthenticate: function() { } getCurrentData: function() { } //... and so on down the list of the supported API methods

It seems there is an error in your config. Could you post the MMM-Nest part of your config, without any access codes? Also, did you follow the MMM-Nest installation guide?

What is the difference between the PIN and Access Token for the Nest module?

I am following the ReadMe here: https://github.com/mochman/MMM-Nest, and I got the PIN from the Nest developers page. Is the “token” this PIN that I received when I entered the product secret, or is the token the product secret itself?

Or, was I supposed to get a token after I ran the gettoken.sh? Once I entered the PIN, the terminal closed and nothing happened…

I’m supposed to insert the following into my config.js:

modules: [
{
module: ‘MMM-Nest’,
position: ‘bottom_right’, // This can be any of the regions.
// Best results in one of the side regions like: top_left
config: {
// See ‘Configuration options’ for more information.
token: ‘1234567890zbcdefghijkl’ //Nest Token - REQUIRED
}
}
]

Thanks for the clarification!

In addition to strawberry it looks like it is rather complicated getting access to the SiteSage API. Looking at various threads on the SiteSage support portal it requires approval from the sales guys and maybe a technical approval from your campus it department.

@bibi display port to hdmi works definitely. it’s both digital, so the adapter should be pretty simple and cheap (I use one for ~12€ from miniDP to HDMI on my laptop)