MMM-Hive

mongo116

@randomnoise Cheers :) That’s great it’s working - you can never be too sure, when I’ve only got my own Hive to test on.
Let me know whether you find any issues with it though. And I wouldn’t worry about having any knowledge, I certainly didn’t!

randomnoise

BTW, your default values in the readme appear to be wrong.

The JS shows they are set to
highestTemp: ‘30’
highTemp: ‘25’
lowTemp: ‘20’
lowestTemp: ‘15’

But readme shows 30 for all of them

mongo116

@randomnoise Doh! That’s the curse of copy / paste! Thanks for pointing this out - fixed the settings in the readme.

randomnoise

@mongo116- Don’t know how your module is going for you, but I seem to be getting errors appearing in my PM2 logs… my mm-out log is filling up with :

Whoops! There was an uncaught exception...
MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues

my mm-error log has lots of:

TypeError: Cannot read property 'statusCode' of undefined
    at Request._callback (/home/pi/MagicMirror/modules/MMM-Hive/node_helper.js:87:21)
    at self.callback (/home/pi/MagicMirror/node_modules/request/request.js:188:22)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:188:7)
    at Request.onRequestError (/home/pi/MagicMirror/node_modules/request/request.js:884:8)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at TLSSocket.socketErrorListener (_http_client.js:309:9)
    at emitOne (events.js:96:13)
    at TLSSocket.emit (events.js:188:7)

seems to happen regularly, but cant really tell exactly what causes it. The module still appears to be working so whatever this is, it isn’t crashing the module or MM itself.

Is yours doing this as well? Let me know if I can do anything else to gather info to troubleshoot.

mongo116

@randomnoise I’m still waiting for my 2-way acrylic to arrive, so to be honest I haven’t run the module for any real length of time. Most I’ve really done is run it for a few hours. While the pi is still in bits waiting to be fitted into a frame, I will run MM and the module on my Windows desktop over night and see what’s occurring. Funnily enough, I have just started MM up and got the following error which I’ve not seen before

Whoops! There was an uncaught exception...
TypeError: Cannot read property 'name' of undefined
    at D:\MagicMirror\modules\default\updatenotification\node_helper.js:35:43
    at D:\MagicMirror\node_modules\simple-git\src\git.js:721:18
    at Git. (D:\MagicMirror\node_modules\simple-git\src\git.js:761:18)

What are the config settings you are using for the module? What’s the updateInterval set as?

Thanks…

randomnoise

Haven’t changed any of the intervals so its just using module defaults

{
			module: "MMM-Hive",
			position: "top_right",
			config: {
				temperatureSuffix: "°C",
				username: "[TOP SECRET]",
				password: "[NOPE]",
				postcode: '[WHERE I LIVE]',
				showNext: true,
				animatedLoading: false,
				highestTemp: '22',
				highTemp: '20',
				lowTemp: '16',
				lowestTemp: '14',
			},
		},

Also got it running in my windows browser ATM with debug console open, but it hasn’t thrown the error yet. I don’t think its occurring all the time, but as my mirror has been running 24/7 there are quite a few of these errors in the logs so definitely not a one off. Log files don’t seem to time stamp entries so I can only tell if I see the timestamp of the log itself change when it occurred.

mongo116

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

mongo116

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.

mongo116

@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

randomnoise

@mongo116 Cheers, have updated & will keep an eye on it.

FWIW it hadn’t thrown the error again since I restarted it yesterday either.