And it only comes in black…?

@sdetweil @Vit73520 Do the same for MMM-Hotword if you’re using it, with the snowboy node module.

@vinp Ugh. You know how sometimes you can’t see the forest for the trees? This is one of those times. Thanks for pointing out the obvious—I completely missed that.

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?