[Remote-Control] Shutdown, Configure and Update your MagicMirror

[Jopyth]

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

[fox]

@Jopyth said in [Remote-Control] Shutdown, Configure and Update your MagicMirror:

@AAPS (and everyone else): You can try the new version, but you can also go back to a previous version afterwards with the commands:

cd MagicMirror/modules/MMM-Remote-Control # or wherever you installed the Mirror and the module
git checkout v1.0.0 # or the version you want

Currently, there is v1.0.0 (which is probably the one you are on) and v1.1.0 as older versions. To check out the most recent version use git checkout master again.

I want to update. But git checkout master does not work. There stands i shall use git pull but then there comes:
*Please, commit your changes or stash them before you can merge.
Aborting
*

[Jopyth]

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

[fox]

@Jopyth said in [Remote-Control] Shutdown, Configure and Update your MagicMirror:

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

Thank you!

What for a fantastic update! I tested nearly every module and everythink worked fine.
You refactored also the config file during saving. Awesome! Nice job.

[Patex]

@Jopyth I forked your project and am looking into adding the functionality to toggle back and forth between different configurations with one click using the remote page (like having a set of different config files). Is this proposed change on your to do list as well?

[AAPS]

Is there anything I need to do to update instead of just putting “git pull” in ~/MagicMirror/modules/MMM-Remote-Control ?

[Jopyth]

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

[Jopyth]

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

@Jopyth What is the difference between develop and master version? Also, I probably sound dumb, but how do I change my ipWhitelist? Currently I have “::ffff:192.168.1.1/24” added. Do I need anything else? ( I would rather be able to access the mirror from any device )

[yawns]

Master branch is the official stable release
Developer branch is in development, so it contains new features but could contain bugs. Once the development team is happy they move the current development version over as the new stable release