Here you can see that the display and the css don’t match.

@Sean Doing this with both MMM-AssistantMk2 and MMM-Hotword (snowboy) did the trick. Thanks!

Hi,

Had previously been running MM v2.6.x and had a problem with the default calendar module always fading, even when my config said fade: false. I eventually just edited the calendar.js file and hardcoded in the false, which worked right up until I upgraded to MM v2.7.0. Now it’s broken again because the calendar module has been updated. I’ve now learned not to edit the calendar.js file because git will yell at me about it eventually, so how do I stop the calendar from fading? Here’s what’s in my config.js, for the record:

                     {
                        disabled: false,
                        module: "calendar",
                        header: "Upcoming",
                        position: "top_left",
                        maximumNumberOfDays: 365,
                        displayRepeatingCountTitle: false,
                        defaultRepeatingCountTitle: "",
                        maxTitleLength: 24,
                        wrapEvents: true,
                        fetchInterval: 5 * 60 * 1000,
                        animationSpeed: 2000,
                        fade: false,
                        urgency: 7,
                        timeFormat: "absolute",
                        dateFormat: "MMM D",
                        dateEndFormat: "HH:mm",
                        fullDayEventDateFormat: "MMM d",
                        showEnd: false,
                        getRelative: 48,
                        fadePoint: 0.25,
                        //maximumEntries: 8, //does this still work?
                        hideOngoing: true,
                        config: {
                                colored: true,
                                coloredSymbolOnly: true,
                                calendars: [
                                        {
                                                symbol: "calendar",
                                                color: "#a3ea80",
                                                url: "https://somecalendarsite.com/b852c7e3115dcac07828de/calendar.ics"
                                        },
                                        {
                                                symbol: "plane",
                                                color: "#f8ff70",
                                                url: "webcal://someothercalendarsite.com/5hsjrwtcddiw1fkue9vjks5dsf9vexn6.ics"
                                        }
                                ]
                        }
                },

Hello,

Upgraded to MM v2.7.0 (backed up first!) and npm start dev shows the following error:

Cannot find module '/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/node/extension_binary/electron-v3.0-linux-arm-glibc/grpc_node.node'

I believe this is detailed here at the bottom under the heading “downgrade grpc to v1.13” but I’m not experienced enough to know if this will also work with MM v2.7.0. Anyone tried it yet?

@bhepler RPi 3 B+

@jcasman Good question! First, the frame: I’d reinforce the corners rather than running struts across the middle. I thought the struts would be dual-purpose, holding in the display as well as strengthening the frame, but as you can see in the pics the frame is bulging a little on the left side. I think I’d strengthen the corners and then just put a couple of blocks about 40% of the way down to hold the display in place. These would be screwed to the side of the frame rather than running the full width or depth across to the other side.

Second, I’d fully disassemble the display, taking the LCD controller and power circuitboard out of their metal housing, to decrease bulk and weight.

Third: shorter cables. Everything I’ve used for power, usb, etc on the back side is what came with each piece, so a full-length power cord, full-length USB, full-length HDMI… All of that adds bulk. I’d get the shortest versions possible next time.

Fourth: glass mirror. While the glass+mirrored film works, it was a pain to get the film to adhere properly, with bubbles or cat hair in between it and the glass, and took a long time to fully cure. The end result, as i said, works, and the text is quite legible through the film, but the mirror does have a bit of a funhouse effect (note top of door on the left).

All said and done, this gives me a great idea of how a finished version could look and it lets me move it around to try different positions, walls, rooms, etc. Doesn’t feel like I wasted any time and I’m not really out of pocket for any of the parts except the film.

Just installed MMM-NetworkScanner but it keeps reporting NO DEVICES ONLINE, even though all devices on my network are assigned static ip addresses and I tried both ip and mac address in the config file. I went back to the install instructions and tried running arps2mm.sh (after updating arp-scan) and got this error:

ERROR: failed to send packet: Resource temporarily unavailable

So I tried running the arp-scan manually (same command that’s in arps2mm.sh) and I got the same error. Is arp-scan broken? Shouldn’t matter, though, because ping works, and isn’t that what MMM-NetworkScanner should be using?

@jobjha1973 You need to register with OpenWeather and they will provide you with an API key.

So here’s my first attempt at a smart mirror using MagicMirror. I’ve had it displayed on a monitor rotated 90º for about a month while I tweaked the modules and researched mirrors. Given that…

• it is my first attempt
• I’m not very handy with tools
• I wanted to get a feel for it quickly
• I wasn’t sure about final placement in my apartment

…I took the cheap route. I had an Ikea picture frame lying around that has a glass insert and used a small monitor that work was throwing away. I bought mirrored film and applied it to the back of the glass as the instructions indicated. This was by far the worst step. The sides of the film kept rolling up on me. It isn’t perfect, but I didn’t expect it to be the first time around (see bullet points above). I’m happy with how it functions, though, so building a better frame and using proper two-way glass next time will be my focus.

Lights off:

Lights on:

I need to get a usb-powered speaker so I can actually hear MMM-AssistantMk2, but the usb microphone plugged into the back of the monitor picks up my voice quite well.

Thoughts?

I’m trying to get this working as well, not with Scenes but just with Routines in general. I have a couple of Routines setup in the Google Assistant app on my iPhone, but the MMM-AssistantMk2 module doesn’t recognize them. I realize it isn’t a full-featured Google Assistant but I was hoping Routines would be accessible. Anyone done it?

SUCCESS!!

@Sean This is weird. I just downloaded my credentials again and this time got

{"installed":{"client_id":"1023635200...

I’ll try this again when I get home. No idea how it could have changed.

@sean My file starts with

{"web":{"client_id":"10236352...

@Sean I don’t think so. I got it to work twice. My browser launched, I logged in, I got a code back and paste that into the prompt presented by auth_and_test.js. Twice. Now the third time, after downgrading grpc to v1.13, it won’t work and I get the above error.

Reposting because I put this in the wrong forum the first time.

I’ll try to make a long story short:

Installed MMM-AssistantMk2 and MMM-Hotword. Added default config for both to config.js. Got nothing but a black screen. Narrowed the problem down to MMM-AssistantMk2 and grpc. So went through the troubleshooting tips to switch to grpc-js instead (same problem) and to downgrade to v1.13 of grpc. I’ve now (for the third time) created my credentials.json file and am trying to run

node auth_and_test.js

This is what shows up after a few seconds:

/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/google-assistant/components/auth.js:27
  const oauthClient = new OAuth2(key.client_id, key.client_secret, key.redirect_uris[0]);
                                     ^

TypeError: Cannot read property 'client_id' of undefined
    at new Auth (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/google-assistant/components/auth.js:27:38)
    at new GoogleAssistant (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/google-assistant/index.js:21:16)
    at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-AssistantMk2/auth_and_test.js:60:19)
    at Module._compile (internal/modules/cjs/loader.js:654:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10)
    at Module.load (internal/modules/cjs/loader.js:566:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:506:12)
    at Function.Module._load (internal/modules/cjs/loader.js:498:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:695:10)
    at startup (internal/bootstrap/node.js:201:19)

And I’m stuck. Help?

I was just about to go home and try installing this module. Glad I looked here first! Not sure I’ll bother now…

Thank you. Just changing the width did the job.

If I’m understanding this correctly, I should be able to add the following to my custom.css file to increase the spacing between the top_left and top_right divs. The monitor I’m using isn’t very wide when rotated 270º so left to right I don’t have much real estate.

So I modified my custom.css like this:

.region.top.left {
  margin-right: 20px !important;
}
.region.top.right {
  margin-left: 20px !important;
}

I’ve tried it with padding-left and padding-right instead, and even added a style before this like this:

.region.top.center {
  padding-right: 10px;
  padding-left: 10px;
}
.region.top.left {
  margin-right: 20px !important;
}
.region.top.right {
  margin-left: 20px !important;
}

Nothing changes. The right-hand side of my top_left div and the left-hand side of my top_right div are almost touching each other. What am I missing here?

@mykle1 said in MMM-PilotWX:

.MMM-PilotWX .bottom_bar {
color: cyan; /* Color line. Default is white. /
font-size: .9em; / Or you can use Ex. 12px */
}

Yep, that works. Perfect. Thank you.