Yeah, I hear you there. I’ve been trying to recreate the problems on my end but … no such luck. It runs flawlessly on my server, both as a super user as well as an unprivileged user. So something happened on his end with he switched things … maybe permissions … maybe something else. We’re trying to figure that out. You … you keep your focus on MM. :)

Does that module actually require an 'npm install' to be run? Don’t blindly run commands that you don’t know are actually necessary. You need to ask the author of that module how to properly install it, what the steps are, what’s needed, etc., etc. I know nothing of that module.

Edited to add: running an 'npm install' is generally only required if the specific module needs any additional node dependencies installed. However, the author would make this known. If it doesn’t say that anywhere, do not assume you have to do it yourself. You may end up causing more harm to your installation than good.

If you can’t log in with that default user and password, and you never changed it to begin with, I would seriously wipe that SD card and start over. There’s no telling what happened to it or why the password is different. And since it’s an internet connected device, that’s cause for alarm, or at least be concerned.

@alexyak, oh, take a picture every day … at the end of the year, put them together in a video and watch the transformation. :)

Just as an example, while I don’t necessarily know yet what I want to do with buttons, I still wanted to integrate one with my mirror. And I don’t particularly like to use a tactile toggle or momentary switch (although I still might later), so instead I opted to use a touch sensor and get that working. So what does it do right now? It started with it simply displaying random messages whenever touched:

                messages: [
                        "That tickles!",
                        "Stop that!",
                        "Was it as good for you as it was for me?",
                        "Stop touching me!",
                        "HEY!",
                        "Did that feel good?",
                        "Are you having fun yet?",
                        "Don't forget to wash your finger later ...",
                        "Must you keep touching me?",
                        "Can't a Sensor get some rest around here?",
                        "I need touch pad sanitizer.",
                        "Are you done yet?",
                ]

(yes, I realize those are kinda funny)

Then I reconfigured it so that when touched, it fades away all the modules so I end up with nothing being displayed, and when I want things back, I just touch it again.

The next step was reconfiguring it so that it triggered the HDMI output and turn it off or on, however I quickly abandoned that because my monitor, when it loses the HDMI signal, will turn to a bright blue background instead of going black. And since it doesn’t support HDMI CEC commands, I’m stuck. I reverted back to turning off the modules instead.

My point here is, that this was a slow and calculated build up of that specific part: the touch sensor:

1. Connect it and see if it responds how I expect it to
2. Get it to do something, display a random message
3. Reconfigure it to turn off all the modules
4. Reconfigure it to power down HDMI - oh, that works but produces an undesirable result, go back to #3

Now that I have that figured out, I can focus on something else that may or may not incorporate the touch sensor. I made sure the sensor works first, and it works as expected, no fuss, no errors, nothing.

@cowboysdude, I don’t know who gave you permission to take a vacation, but they need to be fired. First thing you will need to do when you return.

@flooo, you can look at the repository’s commit history (https://github.com/Bangee44/MMM-swisstransport/commits/master), and then checkout a specific revision by using the SHA1: git checkout <sha1> Note that you may need to use the full sha1 value, not the truncated one.

For example, the last commit on May 3rd is 146a6ce. If you click on that, it expands that commit and you can see the full sha1 value as 146a6cec2aaa5007255cb157ed415ba180639354 in the upper right. So your checkout command then becomes:

git checkout 146a6cec2aaa5007255cb157ed415ba180639354

This is of course done from INSIDE the module’s folder!

@shgmongohh, I do not. However, Google is your friend. W3Schools is another.

DISPLAY=:0 is a must when attempting to start MM through an SSH connection, otherwise it simply doesn’t have a clue what display to use, the one you’re sitting at, or the one on the rpi?
X-Forwarding is not required nor necessary for a simple ssh login, startup, and exit.

Oh, I just noticed that his post where he said he change it was also done on May 3rd … so perhaps that original version no longer exists, which sort of defeats the purpose of using git …