@Kimzer @Sean

Yup, can confirm it works just fine in top_left… my top left width happens to be manually set to be 480px due to another module I’m running so that’s probably why its happy now.

BTW I forgot to set to RPI, but it actually still worked just fine when set to ATB by default.

Tried this module, even with a default config it doesn’t seem to display any of the actual values, just the titles:

Running Rpi3 Raspian Jesse

No errors during startup:

Starting MagicMirror: v2.1.2
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: updatenotification
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
Initializing new module helper ...
Module helper loaded: MMM-Tools
No helper found for module: compliments.
No helper found for module: currentweather.
No helper found for module: weatherforecast.
Initializing new module helper ...
Module helper loaded: newsfeed
All module helpers loaded.
Starting server on port 8080 ... 
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: MMM-Tools
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started ...
Launching application.
Create new calendar fetcher for url: http://www.calendarlabs.com/templates/ical/US-Holidays.ics - Interval: 300000
Create new news fetcher for url: http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml - Interval: 300000
Use existing news fetcher for url: http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml

Config used:

{
		  module: 'MMM-Tools',
		  position: 'bottom_right',
		  config: {
			device : "RPI", // "RPI" is also available
			refresh_interval_ms : 10000,
			warning_interval_ms : 1000 * 60 * 5,
			enable_warning : true,
			warning : {
			  CPU_TEMPERATURE : 65,
			  GPU_TEMPERATURE : 65,
			  CPU_USAGE : 75,
			  STORAGE_USED_PERCENT : 80,
			  MEMORY_USED_PERCENT : 80
			}
		  }
		},

Edit your calendar.js

Find the bit that says-
longDateFormat
Change LT: “hh:mm”
To
LT: “HH:mm”

@ceddirr looks like you’re running npm install from the modules directory, you probably want to cd in to the wunderlist folder (which itself is in modules) then run the npm install

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

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

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

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

Good stuff, works great.

I was hoping someone would get a hive module up as I don’t have the knowledge to program one myself.

Cheers!

@paviro Cheers for making a very useful module.

I have made some modifications to node.js to make it work in my situation. I’ve never really done any javascript programming, so what I did was kind of hacked together from various forums. As you know what you’re doing it would be great if you could include any of these features for future versions (I’ve never used GIT before so not sure how to fork etc).

I had to make the following modifications-

1. Use the vcgencmd function to turn on/off screen (I couldn’t get it to wake up using tvservice despite trying many variations found online). I found this option suggested by others on the forum. Perhaps a config option to use this in place of the TV service for those who it doesn’t work for?
2. The PIR sensor I used is not the same as that used by nearly everyone else (the ones I bought are Wingoneer… they come on a smaller board & don’t have the sensitivity adjustments)… the outcome of this is that the sensor pin is high (+5V) when there is no detection & pulled low (0V) when you move in front of sensor. I therefore had to invert your motion detected logic by swapping the 1 & 0. Could an option for ‘invert pin’ be included?
3. I followed various options online for how to disable the screen saver… but my pi still goes in to screen save mode after 30 mins. This means even if motion is detected, the screen switches on but remains blank. I solved this in a bit of a hacky way by using the xdotool package to simulate pressing “space” and therefore end the screensaver.
4. One final issue which I haven’t been able to resolve yet is that after restarting my PI, assuming there is no motion detected, the screen will be ‘On’ even though there is no motion detected. As an event is not generated (i.e the state didn’t change) it will stay on until the sensor has detected someone & then moved away. Although this isn’t really a huge deal (it should only be restarted if I’m using the screen so I can trigger an event by moving in front & away again) I just wondered if there is a way to do an initial poll of the sensor after start up. I’m not sure if this is because my sensor logic is inverted or if this behaviour is seen on those using the normal PIRs.

As I understand I will lose these changes if you upgrade your module next time I do a GIT pull.

My code below if it is of interest to anyone:

switch off

exec("vcgencmd display_power 0"); //Used in favour of tvservice

switch on

exec("vcgencmd display_power 1"); //Used in favour of tvservice
exec("xdotool key space"); //simulate  spacebar to disable screensaver. Needs xdotool to be installed