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

Jopyth

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

Brice

I’m experiencing a white screen issue after updating MMM-Remote to the latest version. Anyone knows how to solve this ? I’ve disabled the module for now.

Jopyth

@Brice Check this thread.

ChrisLaurie

Notifications does not obey the length parameter. I have installed this module and it looks fantastic! I have tried both the alert and notification features. The alert works and only shows for the length of time specified, but a notification displays (at the top) for only about 3 to 4 seconds and then disappears, no matter what the seconds parameter is set to.

Jopyth

@ChrisLaurie That is because a notification has a fixed length of time. There is no way to change the time of a notification to be displayed longer or shorter (see documentation). Maybe I should make this more clear, that the duration option only works for an alert?

Jopyth

@in_a_days Could you check if my changes on the develop branch solve the problem?

elmattt

This post is deleted!

in_a_days

@Jopyth

Yes, the Save feature is now working for me. Thank you very much! :)

I still get an error when I use Power > Restart MagicMirror

The software does restart correctly. Seems like a false error.

ChrisLaurie

@Jopyth So it is a core functionality. I’m not sure hat the value is of a fixed 4 second notification is.

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

Jopyth

@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