@Mr.Meeseeks Its installed by default, but not neccesarily in the config and on the mirror. :)
That is something I also wanted, but I was not clear on the specification of it. My first draft.
The actions must definitely be offered by the modules themselves.
I myself use a switch originally designed for being operated by foot, however my whole setup is not the usual one (see my “interactive” prezi - almost at the end there is picture of what the product looks like). The switch is hidden underneath the boards between shoes and magic mirror. It it probably not worth for saving money, but I like to be able to switch things off completely.
Best regards,
Joseph
@Mr.Meeseeks What do you mean? Like offer alert sending in the menu only if an alert module is running? Are there any other things which depend on installed modules?
@LukeCodewalker Very interesting module, will you add this to the wiki as well?
Also why did you make a custom header? Wouldn’t it be better to use the default header functionality?
@done Ok, in this case I have no idea. But if it is about the heat, I would probably prefer a hot thing over an electrocuting thing around my walls and the mirror.
Hi,
doesn’t every monitor have the power supply inside somewhere? I think, all the ones I have, do. Did you check, whether the bare metal that you could touch is grounded? You can do this for example, with a multimeter, by checking if current flows through it, after connecting the outer metal case and the ground of your plug (number 2 on the left side of this wikipedia image. If so, you should be pretty safe, however of course I am not a qualified electrician and all information is supplied without liability.
This is how mine looks and it is definitely safe to touch the outer case.
Best regards!
@rvdgeer Would be great to find out what causes this and hopefully fix it, however it is still not clear to me, what the reason is. I will investigate a little bit more on the weekend. Maybe I am able to reproduce the issues, could you post your node --version?
In the meantime you could compare your config.js and the config.js.backupX and see if you find possible differences?
Same here, good luck with the topic. If I were you, I would maybe include my Remote Control in the related work section of your thesis (unfortunately no scientific articles to cite there).
Also will you publish the results of the poll?
@rvdgeer The quotes wrapping should be ok, since whether the key of an object is wrapped in quotes or not, does not make a difference as far as I know. However something is still wrong. Are these console messages coming from your browser?
And did the saving of hidden/shown modules work before you changed to the development branch? Did you change permissions on any folder, and do you have a dedicated user which runs you MagicMirror?
@done Yes the fixed area there takes up way to much space.
Does it still do the restart thing? If yes, can you check the output of pm2 show mm and see if Watch & Reload is enabled? I am currently trying to figure out a way to stop pm2 from restarting on changes of files.
@done Thank you very much!
I am still on the hunt of the restart thing. This is actually a bug, but I am not sure what causes it (if any file in the MagicMirror directory changes, the process restarts). Only happens on the raspberry pi though, and thus harder to debug. If anyone has an idea…
I will see if I can find out what causes the errors on download, since that is the part that actually should work.
It does not show the installed modules list on smartphone in landscape?
If anyone is interested in helping to test the next major (and future) versions of the module, I am searching for beta testers. Please note that the version may still contain bugs, and thus involves an (unlikely) risk of your Raspberry Pi explo… I mean you having to fix some stuff from the command line and your config.js by yourself.
Currently the biggest changes to test are:
config.jsI am looking for feedback on these steps, as well as:
I developed the Remote Control Module (Link to Showcase Thread), and am currently making some major changes, to allow editing the config.js in a UI.
Judging from the traffic of the repository, this module is now being used by more people than just me, so I would like to make sure to gather feedback and fix possible bugs before releasing changes to everyone.
If you are using my module and are interested in helping me by testing the version on my develop branch, I would greatly appreciate it. Note that this version also might not work as intended all the time and can contain bugs. If you are afraid of messing up your config.js you should probably stay on the master branch. Even though backups should be created, these currently need to be restored manually.
If you want to help, please change to the develop branch (I assume you already installed it):
cd ~/MagicMirror/modules/MMM-Remote-Control
git fetch origin
git checkout develop
npm install # install new dependencies
I will post here when new changes are ready for testing, if you want to be updated about new changes, you can watch this thread.
Also I will try to keep my trello board up to date.
Please post ideas, feedback and bugs concerning the develop branch in this thread (or make comments on the trello board).
@bez252 Actually what they describe might also work for you, based on a quick glance through the setup code.
To shutdown from the node_helper you need to change some code in the file(will be in MMM-Button/node_helper.js in your file system).
Here is an example from my module to shut down the RPi, you can replace the self.sendSocketNotification(...) in the node_helper with a similar command:
exec('sudo shutdown -h now', null);
Also, at the beginning of the file you need to include the exec function, like here:
const exec = require('child_process').exec;
@bez252 I made a module (acutally two) for this, however they are not (very well) documented and I just made them for myself. But if you want, I could upload them.
I have four buttons conncted to the RPi, and one of them shuts down the system on a long press (>3 seconds).
There is also this module, which you can adapt by adding a shutdown command.
@Mr.Meeseeks Even though I did not make that properly clear, but that was my intention, behind asking you to make the pull request early, sorry about that. :/ I can help with the merging, though, let me know.
@Jopyth said in MMM-Remote-Control:
@Mr.Meeseeks Also if you think you are at a stage where we can work together, feel free to make the pull request early, and I will have a look and see if I can help.
Otherwise I will concentrate on other stuff, which you have not already implemented.
@Mitchfarino This could be an option, however it only visually looks the same.
If for example a module temporarily does not work for some reason (blocks the start of the mirror), hiding it with the Remote-Control would not help.
What you probably wanted to say is: This should also be added to the Remote Control module. ;) And I would like to include this option in the GUI for the config there. And there is a big advantage in a config option to disable a module (versus commenting out), since this leaves the values readable from other JS code, i.e. the Remote Control module.
@done said in Introduce yourself!:
You know: “If a man says that he will do it, he will! You don’t have to remind him every 6 months.” :D
Exactly.
I wanted a mirror since January, and finished around June. :D
@done Thank you.
Yes this is certainly possible. Would it make sense to also make an option, which automatically switches off the screen at the start up then? So the “default” would be, that the screen is off, but you can switch it on for x Minutes?