Description:

This module will display the inside and outside temperature from your British Gas Hive heating. It is fairly configurable, with some of the text and the inside icon able to be changed. The thermometer is dynamic based on the current outside temperature, and the inside icon will go red when the heating is on. The Target Temperature row will also change if the target temperature of the Hive system is 1°C or lower (I couldn’t find a specific flag for frost protect enabled, so this was the best way I could find to achieve this).

I’ve never written code before, and this took far longer than it probably should have, but the internet is a great place and there are some great resources and assistance out there, so a massive thanks to anyone that has helped me (directly or indirectly).

Screenshots:

Default:

Outside temp exceeding highestTemp value, and heating on

Target temperature 1°C or lower

Text and icon changed in config.js to alternate values

Download:

Version 1

• Initial Release

No code uploaded yet, but I have started on the readme!
MMM-Hive

Got this sorted - found there is another url that holds the information so added another request. The request I was having issues with was a post request, whereas the one I am using is a get.

@jinjirosan Hi, have you made the changes available to download? Would like to give it a go as currently using a combination of the default weather and forecast-io.

Hi Damian,

I’d love to help, but unfortunately I moved house 2 weeks ago and didn’t bring the Hive with me so there is currently no way for me to test this.

From what I do remember the way that Hive works is that you have to authenticate initially and then you can request the info from the hub:

So first call is made to https://api-prod.bgchprod.info:443/omnia/auth/sessions which pulls back the session ID

Then the session ID is used in the header for the request to https://api-prod.bgchprod.info:443/omnia/nodes

For testing I used Postman in Chrome to make the requests etc so that way I could at least see if data was being pulled back.

Have you enabled debug? Might be worth a go and then view the console under the browsers developer tools to check whether data is being pulled from the above urls.

Thanks

I’ve spent some time on this (well all of my spare time really since I posted my request!) seeing if I could bodge something together, and have come up with the following:

I would imagine it’s totally unoptimised, but it pulls the temperature back from the hive server, which is the main thing! The thermometer also changes depending on the temperature, and the flame changes to white when the heating is on. Need to spend some more time tidying it up and will then probably submit it here.

I was just about to post about the nodeName setting as remembered that can cause issues if you have multiple Hive bits - I only ever had the hub and thermostat… Cheers randomnoise

@Eunanibus I’m probably more worried about people reviewing my crappy code I will definitely put it up though.

Hi,

The last screenshot shows Frost Protect Enabled. Is this actually active on your hive?

I’ve only gone and bloody done it!!

https://forum.magicmirror.builders/topic/4576/mmm-hive

Please be gentle with the critique!

@rick Cheers for the details. I’ve updated and added some config options in case this changes again, so you only then need to update the config.

I’ve created a module, MMM-qnapDownloadStation, that will show the current downloads from Download Station running under a QNAP NAS.

Thanks for the replies

I’ve got the bytes string converting to a number, so that’s all good. Now the next question, @Bugsounet how do I use your function within the JSON.parse function?

                var payload = JSON.parse(payload, function (key, value) {
                    if ( key === 'down_rate' ) {
                    var num = Number(value);
                    return (num/(1024*1024)).toFixed(2);
                    }

Just to add, I had tried the following and receive a this.convert is not a function

                    var downrate = this.convert(value,0);
                    return downrate;

I figured this out in the end, with the help of google I used the JSON.parse() reviver function to take the down_rate and up_rate from the payload and divide it by 1024 (and again by 1024) to convert the bytes to megabytes. What confused me at first was I was trying to do this in the node_helper.js, which didn’t work. It needed to be in the socketNotificationReceived of the .js file.

                var payload = JSON.parse(payload, function (key, value) {
                    if ( key === 'down_rate' ) {
                    return (value / 1024 / 1024).toFixed(2);
                    }
                    else if ( key === 'up_rate' ) {
                    return (value / 1024 / 1024).toFixed(2);
                    }
                    else {
                    return value;
                    }
                });

I’m sure there is a proper way of doing this, but for my needs this is now working as needed.

@sdetweil Thanks for the reply.

basically t.data[i].down_rate / 1024 for kilobytes

I’m creating a module that connects to my QNAP NAS and shows the current downloads (DownloadStation). It’s mostly working, but the download rate is in bytes and I’d like to display it in megabytes (or possibly kilobytes).

The download list is in JSON format and I currently display the download name and download rate in a table as follows ( t being the JSON data):

            for (var i = 0; i < t.data.length; i++)
        {
            var row = document.createElement("tr");
            var name = document.createElement("td");
            name.innerHTML = t.data[i].source;
            var downrate = document.createElement("td");
            downrate.innerHTML = t.data[i].down_rate;
            row.appendChild(name);
            row.appendChild(downrate);
            table.appendChild(row);
        }
        wrapper.appendChild(table);

		return wrapper;

@Damian Hi, glad that it’s now working. I’m still going to work on it when I can, but at least no urgency now

For the outside temperature thermometer, check the readme on the github page (https://github.com/flick116/MMM-Hive), specifically the following settings:

highestTemp - Set the highest temperature value, which when reached will use the ‘full thermometer’ icon, plus turn the icon red

highTemp - Set the high temperature value, which when reached will use the ‘three quarters full thermometer’ icon

lowTemp - Set the low temperature value, which when reached will use the ‘half full thermometer’ icon

lowestTemp - Set the lowest temperature value, which when reached will use the ‘quarter full thermometer’ icon
(anything below this temperature will use the ‘empty thermometer’ icon)

Only when the temperature equals or is greater than the highestTemp value will the icon turn red.

The config I have just tested with:

		{
			module: "MMM-Hive",
			position: "top_right",
			header: "Hive",
			config: {
				username: '',
				password: '',
				postcode: '',
				updateInterval: 10 * 60000,
				outsideUrl: 'http://weather-prod.bgchprod.info/weather?postcode=',
				temperatureSuffix: ' °C',
				showNext: true,
				highestTemp: '30',
				highTemp: '25',
				lowTemp: '20',
				lowestTemp: '15',
				animatedLoading: true,
				debug: true,
					},

@Damian I didn’t make any changes to the config really, apart from adding some other settings, but these default to false if not defined.

Could you enable debug in the config for MMM-Hive (debug: true,) and then load the magic mirror in a browser and enable developer tools (F12). In this window, ensure Console is the selected tab and then refresh the page (it’s easier to remove all other modules). When refreshed, you should then see a load of text when the hive module loads, something like the following:

Tue, 10 Apr 2018 14:45:16 GMT MMM-Hive received notification: INSIDE - Payload: [{“id”:“xxx”,“type”:“heating”,“sortOrder”:1,“created”:1521812393853,“parent”:“xxx”,“props”:

If you could copy / paste the text into notepad and then search for “type”

The bit I am interested in, is the text straight after “type” - so in the above example it’s “heating”

I am using the “type” to determine whether to pull back data for heating or hot water so if yours is named differently that is probably the issue. There might be more than one instance of “type”, so if you could let me know all.

Hopefully it’s just that and I can then add a new setting so you can choose the name.

Thanks

I was just testing and realised that when I was seeing the target temperature, it was when the system was in boost mode. So when not in boost mode, but the heating on, it’s not the same as previously, so it won’t show it’s heating. I need to look at how this is now working and update. You should see current temperature correctly using he updated code, but not target unless boost is on.