@Damian Hi. I will give it a read and check the code. I just had a quick look and I may just be able to update the requests etc. Might be a bugger to test, but leave this with me and I will take a look.
Thanks…

@Damian Hi, yeah the frost protect should only show when the target temperature is below a certain value. I would guess the issue here is the data being received from Hive. I won’t ask you to paste the data here (which should show up under the browser’s developer console, when debug is enabled) as it contains data related to your account (from what I remember anyway). The most likely issue is that the receiver name is incorrect or that the relevant data relating to temperature etc is not where the module is expecting it to be. Unfortunately now I no longer have access to Hive there’s not much I can do to look into this. Sorry…

Hi,

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

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 :)

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

@pyrosmiley Thanks for that. What about the wind, and sunrise / sunset settings? Or were these never merged? Thanks…

@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.

@Natacha3 I had issues with Motion Detector, so ended up installing motion alongside Magic Mirror and using that - https://github.com/Motion-Project/motion

For something like this, wouldn’t it be easier to affix a cheap android tablet to the fridge door.

@spwood100 Fantastic news :)
So what was the nodeName you have used to get this working?

@spwood100 If I look at the payload from my Hive, I’m only seeing 5 nodes:
0: Your Receiver
1: Heating (thermostat)
2: Signal Booster
3: Your Hub
4: Heating (receiver)

My system is only heating, so maybe that’s the issue. It may be that both the hot water and heating receiver have stateHeatingRelay in the JSON response. Let me know how you get on with the updated version though. Thanks

@spwood100 Thanks for the info. I’ve updated the module and added a new config setting (‘nodeName’). Can you copy the debug text from the INSIDE debug info into notepad++ again, and using the JSON viewer drill down into each of the nodes. Only one should have stateHeatingRelay under attributes. Assuming only one does, make a note of the ‘name’ of this node and then add the following to the config section of the MMM-Hive section in your config.js:

nodeName: "value from above here",

Hopefully this should then pick up the inside temperature from your thermostat. If more than one have a stateHeatingRelay, then it’s back to the drawing board! As that’s not mentioned in any of the api details on the web :)

@spwood100 It looks like it should be working. I’ve just updated the module though and added the payload when debug is true. This should now output a load of text when in the console. Which is the JSON response from the Hive server relating to your receiver. You should see something like the following:

“name”:“Your Receiver”,“nodeType”:“http://alertme.com/schema/json/node.class.thermostat.json#”

I am using the “name”:“Your Receiver” to find the correct node (as this is the one that holds the temperature info). Could be that your’s is called something else. I’d say attach the complete JSON here, but I cannot be sure there isn’t anything in there that you wouldn’t want to put on a public website! So best bet is to copy / paste the text (starting with {“meta”:{},“links”:{},“linked”:{},“nodes”:[ and ending with }}}]}) into notepad++, and use the JS Tool plugin, which has a very good JSON viewer. If you run the JSON viewer, you will then see meta, links, linked, nodes etc on the left pane. If you can expand Nodes and then go into each one (0, 1, 2, etc) and let me know the ‘name:’ for each node (with the corresponding node number).

Thanks

@spwood100 Can you add deb: true, to your config.js under the MMM-Hive configuration options, and then reload and check the developer tools console. It should show more detailed information.

@spwood100 Ok, let me know. Thanks…

@spwood100 Hi, can you connect to the magicmirror via Chrome or some other browser and enable developer tools (F12). Refresh the page and you should see information shown in the developer tools window. If you set debug: true in the config.js that will output more details. If your username / password are wrong, then it should show that on the magic mirror screen.

I came back from work and had loads of the uncaught exception errors, but the module was not showing any error on the screen. Apparently the internet had been down since 2pm, so looks like that was the cause. Hopefully the errors being seen are just down to the Hive site not being available, so the changes I have made should prevent these from generating errors. If you have debug on though you will see them. Hopefully it’s sorted now :)

@randomnoise I’ve updated github with the changes. Can you update and enable debug. I’ve added a timestamp so if you have developer tools open, you should see the errors. Let me know. I will keep it running overnight to see whether I am still experiencing the problem. Thanks

I’ve added some slight changes and I am going to leave it running today. I did see the same issue as you are having last night. Not sure why yet, but at least I am seeing the same. Once I’ve tested the changes for a day or so, I will update github and let you know.

@randomnoise Let me know how it goes and I will do some troubleshooting myself.