@gismo2006 Good point. We might even want something like this option in the core.

I had some plans into that direction, too, but as I experienced for myself something like this is a long term project indeed.

In my imagination, the remote control module could some day be used to download new modules (often a simple git pull plus npm install) create/change the config.js file, to add these new modules, with the parameters being editable in the UI.

If you want, I invite you (and everyone else who wants) to go on this journey, and see where we end up. ;)

I am using pm2 but watch & reload was disabled.

I did a complete update, which apparently helped people before with #150, that seems to have fixed it:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt-get clean
sudo rpi-update

I am a little bit in the dark on the restart issue. It happens every time I change any file in my source code directory, i.e. config/config.js or even package.json.

All I have so far, is this appeared after I updated to development branch (hence updated all npm dependencies), plus I had to update my PIR-Sensor module (got a version XX expected, got XX error), and rebuild dependencies there also.

Does anyone have any idea on this? And is anyone else even seeing this behavior also? If I have time, I will try a complete reinstall and see if that fixes it.

My mirror is now also running the development version, and I am experiencing restarts more often than before. I guess it is related to # 150 since there is no error in the log. Anyway I saw this twice yesterday, but this might just be something with a newer electron version, so maybe nothing we can fix. It is still a little bit annoying.

@MichMich By the way, do you have any particular date in mind for the release?

@gismo2006 Good idea. Originally I thought the IP address filtering coming in version 2.1.0 could serve that purpose. Do you think that would work? I.e. you can assign fixed IP addresses to your devices, and enter these addresses in the config.js, and only these IP’s are allowed to access the mirror (and also the Remote Control).

@MichMich Yes. Since the mirror is integrated into our wardrobe, with our shoes beneath it, I get ready for my morning run in front of it. So there I would notice the update notification (that was my original thought at least). But this is really not a big issue, the fixed message probably works fine as well.

@Bangee Just me being confused: this needs sudo rights, doesn’t it? You just do not want to start the mirror with sudo?

@MichMich Well, I start my mirror in the morning, and shut it down before going to sleep, so a notification at start up would be perfect for me. I even installed a “light” switch under my mirror to do that. But maybe this is really just me, I can implement this on my fork.

Oh, I see. My this.identifier would have been the identifier of the module to be hidden.

I like the idea, but as @strawberry-3-141 says, maybe a notification at start up would be good alternative? Or as an additional option, so if you do not set a position, you see the notification, and if you have a fixed position it does not show a notification.

If it pushes other modules down, the module could just hide itself instead?

@strawberry-3-141 Added some feedback on the translation.

@MichMich Did you have any concerns about making this an opt-out instead of an opt-in? I.e. make the default options {this.identifier} instead of {}. Or is there a specific reason against it? The overall concept seems reasonable, if we assume the meaning of the hide() method always was to “keep this module hidden until I want it to reappear”.

I do not think anyone does something like hiding module A from module B and then purposely showing module A again from module C. This is the only way I think of, which would make the default option using the modules identifier weird.

@Tuxdiver What kind of sensors are you using for this internally (your openHAB)?

@yo-less Thanks! And the cluttering is an important aspect, indeed. Should definitely be optional and that is why I would think a symbol is nice, for less space usage.

@yo-less Nice module you have here, it would be a shame if someone … would steal it. :)

I am currently working on a departure time module for Berlin/Brandenburg, I like the layout of your module and would like to use a similar layout, and I guess the MIT license says yes, but I would still like to ask.

Also I have a few suggestions, which I either implemented already, or are going to implement for my module. Maybe you want some of these options, too.

You could allow users to use a custom header, maybe they want a custom name instead of the station name? E.g. check if this.data.header is set, and if yes, do not create your own one.
Also when version 2.1.0 of the MagicMirror is released, you can use the https://github.com/MichMich/MagicMirror/tree/develop/modules#getheader function.
And no matter which of these methods you use in the future, it might be nice to have an optional small appendix (last updated: 12:30) to the header with the time the data was last updated at, e.g. something like a font awesome refresh symbol + the time in case of connection issues.

Sorry for your loss. Hope you and your family will find your way through it.

The gallery is looking good though.

You can also take a look at this. It explains also how to debug from your machine, instead of doing everything via SSH.

@KirAsh4 Can we find out, which version is compatible, and set that? I am experiencing a similar error after chaging to the development branch, but maybe it is unrelated to this specific problem. But I do not know which version of electron I had previously.

@ianperrin The actions available are now also documented in the readme, so noone has to dig through all the code neccessarily. See this section, a table is down below.