Would it work for you guys if I implement a config parameter for the Remote Control, similar to the ones I use for my Buttons module (notification specification), and you can create custom Buttons with this specification for the remote control?

@Mar If it is doing the reverse of what you want, swap the comparison of value == 1 and value == 0 of this section in the node_helper.js.

@zichao92 First of all you are editing the remote.js file, aren’t you? This is not on the actual mirror website, so you can not directly send notifications from there. This is the js file for the raspberrypi:8080/remote.html website.

You could however send the notification through a generic notification request.

Also this in the part I think you are editing, refers to the dictionary, not the the Remote object, since it is outside of the class definition. You could move it inside to fix this, or change this to Remote.

@Mar Please change your package.json file as displayed here and execute npm install again. @paviro has not yet responded to my PR, but hopefully this will get merged in sooner or later.

@schlachtkreuzer6 How did you install the module? It sounds like you may have downloaded a zipped version? Or did you use the installer or git clone https://github.com/Jopyth/MMM-Remote-Control.git? Edit: Also please do @yawns suggestion, if the folder does not exist, something went wrong with cloning/initializing the git repository.

@AAPS If you want to allow all devices on your network, change the 24 to a 120 for IPv6: ::ffff:192.168.1.1/120

Also, new version with bugfixes is out, see below. Has anyone tried the installer yet? I made it mostly for fun, but I am still look for serious feedback. :)

[1.1.2] - 2017-02-01

Note: Since version 1.1.0 this module uses (new) dependencies, check the Updating section in the README.md.

Added

• Swedish translation

Changed

• Installation process updated in README.md
• Automatic installer/updater includes hint to restart Magic Mirror²

Fixed

• Issues with not applying shown and hidden status correctly to modules
• Issues where lockstrings were missing
• Modules sometimes did not show correctly in the UI as hidden or shown:
  • This is due to a bug in Magic Mirror²
  • PR #659 to fix this was made in the project, will be released in the next version

[Advertisement for my own module incoming]: We (ab)use the Trello module for this kind of note. My girlfriend and I use one dedicated list for MagicMirror notes, and if we put cards on it they show on the mirror. Downside is you need a Trello account, upside is, it is easy to edit from phone, PC, …

With some custom CSS styling it would look like a sticky note. :)

@Mar said in [MMM-PIR-Sensor] Install failing:

I’ve tried following the instruction above of removing and reinstalling but I keep getting the below errors. I’m not even sure what they are unfortunately, wondering if anyone is able to help.

pi@raspberrypi:~/MagicMirror/modules/MMM-PIR-Sensor $ npm install
npm WARN engine electron-rebuild@1.5.7: wanted: {"node":">=6.0.0"} (current: {"node":"4.2.1","npm":"2.14.7"})

This is an old node version. Please update your node and npm. (If you need help check the answers to this SO question.)

@Patex Do you want to do this with the config.js or with the settings.json (visibility of modules and brightness)? I had this idea once for the settings of visible modules and brightness, but did not implement it. Basically what other modules do with profiles defined in the config. I am not sure how much sense it makes to have multiple config.js. One (large) config.js (which includes all configured modules) and multiple “profiles” which only show a selection of these might be the way to go?

@AAPS The script does git pull and npm install (therefore you need to do the npm install, if you are updating from an old version). Also it offers to switch between the develop and the master version (source).

@fox Interesting. What changes did you make? I will try to give you a short git crash course for your case: You can get an overview via git status (should show changed files) and git diff (showing the changes themselves). If you do not care about these changes you should be able to use git reset --hard origin/master or if you do care about them use git stash, then do git pull, and then git stash pop to apply the changes again.

@Renfield If you would like to disable all update notifications you can do as @cowboysdude has written (remove the updatenotification module).

Alternatively (edit: if you only want to disable update notifications for the WunderGround module):
Go to ~/MagicMirror/module/MMM-WunderGround and remove the git remote with the command git remote remove origin. If at any point you want to enable updates, or git pull command again, you can add the remote back with git remote add origin https://github.com/RedNax67/MMM-WunderGround.git.

Source for the module: https://github.com/MichMich/MagicMirror/tree/master/modules/default/updatenotification

I am going to quote my previous post:

Maybe you can post an anonymous copy of your ics file?

Without more information this is going to be difficult to resolve.

Edit: Somehow the dates in the parsing are being ported back to a date before 1970, probably because a year is not passed or interpreted correctly. Additionally it might be useful to know when you last updated (when it was still working) and at what point in time it stopped working, this would limit the changes we have to look at a little bit.

@dz I suggest you start with copying the helloworld module. For example, if you are in the MagicMirror modules folder you copy the default/helloworld folder to myawesomemodule (out of the default folder).

Then, in that folder you rename helloworld.js to myawesomemodule.js and change the name in line 10 in the new file also to myawesomemodule. You will also need to do these renaming steps, to change your module to a different name, so it is best if you pick a great name for what you want to do before you publish the module.

Now add your new module to the config:

{
    module: "myawesomemodule",
    position: "upper_third",
    classes: "large thin",
    config: {
        text: "My awesome module says: 'Hello World MagicMirror2'!"
    }
},

I hope this gets you started. Will see if I can add some more info on the node_helper.js stuff, but you may be able to figure this out yourself, by looking at other modules.

@Makradon Sensor PIN 22 for the PIR-Sensor module is this one:

Edit: Maybe I was confused by the diagram of the DHT22 module. It looked to me like the GPIO and WiringPi numbers are different.

@dfuerst I think it is a bug in MMM-ProfileSwitcher, I was also experiencing it. There is currently no other module providing this functionality as far as I know, but it will probably be fixed soon, maybe I will look into this myself on the weekend, if @tosti007 has not fixed it by then. :)

@Makradon Nope, definitely not the same numbering.

@FlorianRD You need to be on Magic Mirror versions 2.1.0 or higher (i.e. develop branch).

Edit: What MagicMirror version are you on? 2.1.0? When you navigate from the MMM-Buttons folder to ../../node_modules you should end up in a folder with an electron folder. If there is only a electron-prebuilt folder, it should be possible to fix the issues by upgrading MagicMirror to 2.1.0.

@ChrisLaurie Correct. The value is 3500 ms by default (code). This can be changed in the config of the alert module.

@in_a_days Yes, that is a false error, I will probably implement it, so an error after trying to restart is just ignored.

What do you need? Module or command: /opt/vc/bin/vcgencmd measure_temp?