There are a couple ways I can think of. The easiest one, that wouldn’t require recoding the traffic module would be to have 2 config.js files. One with the destination of town, and the other, work. You could set up a small bash script to switch the files and restart the mirror. You could then put that script in your crontab that runs it at the beginning of the weekend and then at the beginning of the week.

A more lengthy way would be to have your traffic module take an array of origins/destinations/weekdays and then use it’s internal programming to display the correct commute.

Another lengthy way would be to have the traffic module use a notificationReceived() with the payload being a origin/destination and then you creating another module that passes that info at a certain date/time.

I’m sure there are may other ways this can be done, but those are the ones that come to mind.

@willharwell Glad to hear it!

I can’t help you then. That was my last option. I don’t receive that error nor do I know what that error means.

@BeLuGe Try running rm -rf node_modules/ inside the MMM-Swipe folder then running npm install again.

Can you make another config.js file with just the MMM-Swipe module in there? I don’t know what the:
WARNING! Could not load config file. Starting with default configuration. Error found: Error: Module version mismatch. Expected 49, got 48. means.

No worries. Yeah the sensor looks like it has 2 detectors on it. I’m pretty sure one is the speaker and the other is the microphone detector.

@Mitchfarino

Your left sensor

Vcc goes to pin #2
Gnd goes to pin #6
Trig goes to physical pin #26 (Which is labeled GPIO 23)
Echo goes to physical pin #18 (Which is labeled GPIO 24)

Your right sensor

Vcc goes to pin #4
Gnd goes to pin #9
Trig goes to physical pin #22 (Which is labeled GPIO 25)
Echo goes to physical pin #37 (Which is labeled GPIO 26)

You need both sensors if you want to detect movement.

@BeLuGe So I just tried this myself. When I created the module, I was connected to the pi to test. I just tried using SSH to start the program and got the same error you’re getting. Looks like it’s a issue with running a sudo command over SSH, the workaround I found was to run sudo cp ~/.Xauthority /root/ then run DISPLAY=:0 sudo npm start. The problem with this is that everytime you restart your mirror you will need to run the copy command again.

@Mitchfarino You don’t need a breadboard. I just used one to test out my configuration. You can hook it up directly to the pi using those wires you have already connected. When I tested out my setup, I used these pins.

echoLeftPin: 24,       
triggerLeftPin: 23,     
echoRightPin: 26,      
triggerRightPin: 25,   

Remember that those are the GPIO #'s and not the physical pin #.

@BeLuGe Have you run npm install in the MMM-Swipe folder? Are you running the mirror with sudo? If so would you mind posting your config.js file. Thanks.

I just updated the module to catch some problems. Can you go into the MMM-Nest module folder and run git pull. That should get the most updated version. If you are still having problems, can you run the following command
rm ~/.pm2/logs/mm-error-0.log
Restart your mirror then post the contents of both your console.log and the mm-error-0.log. Thanks.

I’m not sure if this is the right way, but I use chrome on my computer and go to http://your-raspi-ip:8080. This should take you to your magicmirror webpage. Then I open up the developer console with ctrl-shift-I. On the top, you can select console. It should have all the info from your modules there.

Are you seeing anything in the console logs? It sounds like the XML Request isn’t responding with the data. I’ve really only tested my own system so I haven’t caught all the problems yet. How is your nest set up? Do you just have 1 unit?

I’ve taken apart a couple different monitors (and was able to get them back together with minimal extra screws). The bezels usually take a little prying to start, but once you get a section open, the rest come out easy. I used a putty knife to get things going, then just pulled the rest of it apart. Make sure you remove all the screws you see in the back. If the bezel gives you resistance at a certain point, look to see if you missed a screw under a sitcker or something before pulling harder. Once the bezel is removed, there is usually a couple circuit boards with some ribbon connectors. If you want to make life easier, take a picture of how they’re all connected. My asus monitor had a couple of the same connectors, so I had to remember which board was plugged into which connector.

@Mitchfarino According to this article, putting Alexa on the pi makes is usable wherever you are.

Ha, that’s one way to put it!

Don’t judge me too harshly but I here’s what the back looks like. Lots of tape, hot glue, and wires.

@Mitchfarino Sure. Here’s a demo video of Alexa.

I finally got all the parts and pieces I needed to build the mirror for my wife and me.

Luckily I was purchasing the monitor during the Amazon Prime Day so I got it at a little discount.

Monitor - ASUS VE278H 27" via HDMI
Sound - Kingwin USB 3D Sound Adaptor (for Alexa)
Button - PV6F240SS-3R1
Mirror - 1/4" Acrylic
Raspberry Pi 3

ToDo’s:
Add Swipe wiring (sensors are already installed behind speaker mesh)
Add PIR wiring (already mounted too)

I used the AlexaPi program with the Button/LEDs to get Alexa Voice (independent of the mirror app)

Looking up close, I wish I put some electrical tape under the edge of the monitor to try and stop it from coming through, same goes for the wood “notch” it sits on.

@Mitchfarino Looks almost all good. I’m not sure if you have your trigger pin hooked up to ground from this picture. The pins in the config are not the actual pin #'s of the header. It uses the GPIO#. I use this picture as a reference.

As an example you can see that pin 32 is called GPIO12. If you connected your Trig wire to that and your Echo wire to GPIO16 (physical pin 36). In the config.js you would use :

echoLeftPin: 12,
triggerLeftPin: 16,

and then a similar setup for your other sensor.
If you are still having issues with the setup, please let me know.

As a reference point, your red wire is connected to physical pin #2.

Here’s what it should look like for you.