It works with the master branch because the update was also pushed to that a few days ago. So you’ll all good. :)

It’s on @MichMich’s radar …

On my radar is the possibility to live a 37 hour day without having an psychotic episode.

I did it for you. For future reference, you will have to set the topic as a question first, then you can change it later to solved. On the bottom right of the posts, there are three dots in a vertical line. Click on that to change the topic to a question (which will mark it 'Unsolved'), then when you’re ready to change it, click on the three dots again and you’ll have an option to set it to 'Solved'.

Not as written. It would require a bit of rewriting to allow for a local call to a file. Not impossible, just not written.

When in doubt, pull the plug.

You could also look at what’s already been done, such as https://github.com/moshen/node-googlemaps …

It’s confusing to readers when an original post gets changed later. It’s better to make an announcement in the thread. Keep the original for posterity.

At the moment, no.

@tyho, there is a huge difference on how you use the Google Maps API to display a map in a browser, compared to how it needs to be done within the core module system of MagicMirror. MagicMirror isn’t simply a browser that displays HTML or JS … it processes the information fed to it, and that information needs to be in a very specific format to be processed successfully. This is why my recommendation to you was to try and understand the core system first, before you try to integrate something as complex as any of the Google APIs, not just the maps one.

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

A true hack-your-own project. Love it.

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.

@bscarano, regardless of which branch you are on, you are in charge of your mirror, including updating the code.

Reading your posts and your code, there are two things that stand out for me, one is that you are really trying, you want to figure it out, and you are doing everything you can think of to make things work. That is something I look for in any and all of the kids I teach in school: the desire to want to try and figure things out and not just memorize the book and regurgitate it back up later. The other side of that is that as hard as you are trying, you are struggling with it and a lot of it is because there seems to be a lack of understanding how the underlying code works and in some cases, even the simple fundamentals of JavaScript.

While looking at other people’s code is certainly a possibility, for what you are trying to do, that isn’t working so well. You have unfortunately also picked a harder to implement system than many others. My recommendation is to start with something simple first, try to understand how the system works, how a module gets integrated into the core system, how a module works on its own, how does it communicate with the outside world if it needs to. I recommend reading the module development page and work through that. Start small.

I’m not here to discourage you from what you are attempting to do, it is certainly possible to do what you want, but at the same time I also want to try and guide you, rather than just telling you ‘this is wrong’, ‘do that’, etc., etc. No one learns from that.

In your post you mentioned both wanting the maps integration, and also voice control. Those are two completely different systems, and require completely different controls. Do things one at a time. Either do the voice control part first, and get that working (you don’t need the ‘maps’ feature for this). You can always come back later and add to it. Or, do the maps integration first, and get that working the way you want it to. Integrating a button is by far the easiest way to have some kind of interaction between the mirror and the user. A simple button push can do something, like for example, display an alert message. So get that working, push button, alert message pops up (‘Hi, you pushed my button!’). Again, you can always change it later to say, trigger the display of a map. Whichever you do first, just pick one and get it working, and get it working correctly and have it stable, not just ‘it works sometimes’ …

Small steps, one at a time, together they form a bigger achievement. You can do it.

With mine, as the temperature started to get higher and higher, the HDMI started dropping out. It would cause the monitor to blank out momentarily. It would stop late in the evening and be fine, but then during the day I would start seeing it again. Boosting the HDMI signal on the rpi didn’t help (in fact it made the temperature go up a bit higher even), but whenever I just blew across the rpi’s CPU, it would stop. That’s how I realized it was just getting too hot, even at the default speed. Now that I put it in a case with a fan, I haven’t had any issues.

That would affect all modules though. Just keep that in mind.

@pigreco, I didn’t expose the other clock hands to be easily accessible to change the colors on. I’ll have to add that in in a later update. As @MichMich said, making changes to those core files will cause git to start complaining at you.

Likely a bug recently discovered. Follow the instructions in the first post here to try the 'develop' branch:

https://forum.magicmirror.builders/topic/445/looking-for-beta-testers

@pigreco, feel free to post your ideas in the various sections they might pertain to, modules, core system, or a general topic.

@d3r, if you checkout the code as per @MichMich’s instructions above, it will automatically download and over write the current codebase with the develop branch. It will NOT overwrite your current config.js file.