The office is very impressed with the Globe module. Thanks again for making this one.

Here’s how it looks on an actual mirror. :)

Now this is curious… It works great on my Windows 10 box (Chrome or Firefox). It works great on my Ubuntu 16.04 box at work (Chrome or Firefox). It works fantastic in Chrome or Firefox no matter the platform.

But when I run npm start it doesn’t render anything to the screen. This is on an Ubuntu 16.04 microPC. Fascinating.

@AnyKey said in MagicMirror Servermode on Synology DS:

EADDRINUSE

This usually means that you already have the MagicMirror running and you have attempted to start the server again. You’ll need to kill that process before starting it up.
Try ps ax | grep node and if you see the line 9589 pts/1 Sl+ 0:03 node serveronly or something similar, then the Mirror is already running.
sudo kill -9 9589 (or whatever the process number listed is) will stop it.

I’m sorry this has been so frustrating. You’re almost there.

@Eunanibus That it did. Thank you.

I’ll get it up on the mirror in the office today and send you a picture.

@Eunanibus Whatever change you made solved most of my problem. Now when I add locations, only the locations I add are being labeled.

I’m still seeing a bunch of nameless pins all over the globe. I’m going to have to turn those off.

This module is awesome. I have it up & running at the office and it looks fantastic.

Question: I added a bunch of custom locations, which is great. But they don’t seem to be replacing the default locations. So I’m getting my locations and the ones that came pre-loaded. Is this by design?

@AnyKey Heh. I’ve been there.
First, you’ll need to be sure that the config.js file exists. A manual installation generally does not copy the sample file into the final destination, so you’ll need to do it yourself. From the MagicMirror folder, cp config/config.js.sample config/config.js should put the file in the proper place. At that point, it’s ready for editing.

The Unix-like system that the Diskstation uses must have an editor of some form on there. If not nano, then VIM or VI. From the MagicMirror directory, you should be able to type nano config/config.js or vi config/config.js and open up the config file.

Absolute worst case scenario: you can copy & paste the config.js contents from your desktop machine to the file via PuTTY. Have the config file open on your desktop, select all, copy to clipboard. In the PuTTY window, navigate to the MagicMirror/config folder and enter cat > config.js and then press enter. At this point, everything you type will be in the file… so just right-click with your mouse to paste the clipboard into the file. When it finishes, hit enter one more time and the ctrl+d (control D). That will save the contents.

@lagoon7 Yeah, I knew I forgot a step.

After you clone the MagicMirror repository to your home folder, you need to install all of the dependencies. Type cd ~/MagicMirror followed by npm install and wait for it to install all the extra stuff for the MagicMirror framework. Once it’s done, type npm start and it should take over your screen and show you the interface.

Wow. Excellent woodworking skills there. Good idea in both concept & execution.

@AnyKey To my knowledge, warnings can be safely ignored. It sounds like you’re most of the way there.

For #4, did you adjust the ipWhitelist parameter in your config.js? I would think that by default, it would be configured to allow browser access only by the Diskstation. You’ll have to change that to include either your entire internal network or your specific machines (depending on your application).

Yeah, let’s try that again but with a proper piece of glass.

@AnyKey It looks like you can. A quick perusal of the Synology forums found that a few users have been using Nodejs on their devices. Off the top of my head, the process to manually install MagicMirror on a non-Raspberry system is:

1. install Nodejs & NPM (here’s a hint)
2. Install git and clone the repository.
3. Run npm install in the MagicMirror folder.
4. Start node and it will provide a webserver.

That should get you started. You may have to switch the port that Node uses for the web server, but that’s trivial.

@cowboysdude I don’t think that will give him the effect he wants. That method isn’t dynamic based upon his PIR sensor.

@Oliver_Tooth Somewhat. I see steps, distance and calories. Sleep is zero. There’s definitely something going on here. I haven’t run it long enough to encounter the authorization problem. I’ll investigate further tonight.

@Vendittelli - I’ll do that. I should have a PR for you in a couple days. Thanks for the great module!

@Oliver_Tooth I was able to successfully install the Fitbit module and get it to pull information from the web API. It took a little tweaking, but I did get it to work.

Problems I encountered:

• Python was not installed. I had to install it and figure out how to install “pip”.
• Fitbit doesn’t make their developer area visible off their main website. I ended up bouncing through their forums first.
• Example config file on the module GitHub page contains errors. The character after config: should be {, not [.
• The secret key and appID field values need to be surrounded by single quotes, something not explained in the readme file.

Here’s the relevant portion of my config.sys file.

{
        module: 'MMM-fitbit',
        position: 'bottom_left',
        config: {
                credentials: {
                        client_id: '000XX0',
                        client_secret: 'abbacadabba1234567890',
                        },
                resources: [
                        'steps',
                        'floors',
                        'caloriesOut',
                        'distance',
                        'activeMinutes',
                        'sleep',
                        'heart'
                        ],
                update_interval: 60
                }
},

When you run npm start the MMM-Fitbit python script will run and kick out a few lines in the console. I’m not entirely sure what it’s doing, but here’s what mine reads:

Set credential request recieved.
{ client_id: '000XX0',
  client_secret: 'abbacadabba1234567890' }
Initial run request recieved.
Running getData.py
results: [{"message":"credentials.ini exists","type":"status"},{"message":"Writing credentials to credentials.ini","type":"status"},{"message":"Writing id: 000XX0 and secret: abbacadabba1234567890","type":"status"},{"message":"Credentials write successful","type":"status"}]

When I ran the setupAccess.py script, it failed to modify the credentials.ini file. I ended up editing it manually and plugging in my application ID and my secret key. The format is simple. Spaces before & after the = and no quotes around the ID or key.

Fantastic! This is going to save me so much time…

@zdenek Did you delete all the stuff not used for a mirror? From the complete setup tutorial: sudo apt-get remove --purge idle3 java-common libreoffice* minecraft-pi scratch nuscratch penguinspuzzle python-minecraftpi python3-minecraftpi smartsim sonic-pi wolfram-engine

@Mykle1 Huh. When I checked this thread earlier today, I saw the image. Now I do not. Very curious.

@FreddyH Did you do something to your image?

Wow. Go big or go home, eh? That looks great.

@Oliver_Tooth Well, the Wife wants her FitBit stats on the mirror so I’m going to end up using this module at some point. I’ll try and catch up to you and we’ll debug this together.