@jopyth can you explain me how I can implement a HIDE_ALL? I’m very new in such things and looking for something like that. Want to be able to activate one module and hide all other for the time. Thanks

Hi! I am a happy tinkering, first time Magic Mirror creator and I am having trouble with the Remote-Control / Network-Scan module. I’m using the “standard” code as given in the example on * { module: ‘MMM-NetworkScanner’, position: ‘top_left’, config: { devices: [ { ipAddress: “github.com”, name: “Github”, icon: “globe”}, { macAddress: “1a:1b:1c:1a:1b:1c”, name: “Server”, icon: “server”}, { macAddress: “2a:2b:2c:2a:2b:2c”, name: “Desktop”, icon: “desktop”}, { ipAddress: “10.1.1.10”, name: “Laptop”, icon: “laptop”}, { macAddress: “4a:4b:4c:4a:4b:4c”, name: “Mobile”, icon: “mobile”}, ], showUnknown: false, showOffline: true, keepAlive: 600, updateInterval: 5, residents: [“Mobile”, “Laptop”], occupiedCMD: {notification: ‘REMOTE_ACTION’, payload: {action: ‘MONITORON’}}, vacantCMD : {notification: ‘REMOTE_ACTION’, payload: {action: ‘MONITOROFF’}}, } }, * With my devices MAC ID’s and names, the scan works fine and the module for the remote control receives the “MONITOROFF” and “MONITORON” notifications and executes them as expected… When none of the listed devices are active on the network, the monitor shuts off. But there is something that makes the screen go off and then on again every 20-30 seconds, i have previously had the PI 3B+ running for hours without this phenomena occur, but now with the modules installed it seems that the network scan sends the on/off notifications to the remote control module more often than intended. As you see in the code, the “keepAlive” timer is set to 10 minutes, and the scan is set to every 5 second. In my small understanding of code e.t.c the keepAlive timer should hold the “MONITOROFF” notification for 600 seconds before sending it to the remote-control module IF it does not detect any network activity from the specified devices… Does anyone know why this happens on what i could do to make it work more smoothly? I’m thinking of basing the shutoff sequence on the calendar and time instead… although it would be nice to have the network part of it working. Best regards.

Looks like I should have looked closer to home than all over the web! I watched more closely at the boot-up procedure of my RPi and noticed a FAILED step involving dhcpcd. I looked that up on the web and found that newer distros don’t want you to edit the file /etc/network/interfaces. See this link for more information: https://www.raspberrypi.org/forums/viewtopic.php?t=203530 I followed the directions there and then went back Raspberrypi.org to follow the directions for properly (and easily) setting up my wifi. Once I did all that the dhcpcd error was gone and my MM2.5 reboot issues were resolved. Case closed.

@lavolp3 said in Calendar show wrong time.: ‘absolute’ I had test and see it doesn’t work that you said. The mirror is show me pm or am time instead for show me an exampel 16:00. That I want it’s the calendar not the time. What I do now?

@bkeyport . You’re absolutely right in that, and that’s how I did it all the time. But to create a script where it does not matter where you are at that moment, it seemed like a fun project to start building scripts again. Do you happen to have an answer about my questions?

@rudibarani Prepare two config - config.snowon.js and config.snowoff.js. Make a code to copy one of both to config.js when your trigger is activated. The next time rebooted, it will be applied. Instead of copying file, you can read config.js and rewrite it directly. but a bullet-proof-parsing js code is not so easy for unexperienced one.) However, MMM-Snow has no node_helper.js to refer. You have to build node_helper.js to do your job. (In MMM-Snow.js itself, approaching filesystem is limited.)

Would also appreciate you marking the issue as solved, as this is not an issue with the MMM-CalendarWeek module :) Thanks!

@mykle1 cool, mykle, didnt know that streetplan existed. Good reading on the silmarillion. Heavy stuf, but I liked the big plan that unfolds if you read more on tolkiens universe.

@cjmaverick There are to many ] modules: [ in your config.js. There should be only one time modules: [ somewhere in the beginning of your config.js and one time ] near the end of config.js Greetings AxLED

I see several examples where Today and Tommorow is displayed, but did not see the corresponding config. In my config I added / changed urgency: 2, getRelative: 6, Still no joy.

Hi @sean, Thanks for your explanation! This helps alot! And no… :smiling_face_with_open_mouth_smiling_eyes: :smiling_face_with_open_mouth_smiling_eyes: I’n not building my own module… I’m to inexperienced for that. Maybe one day… For now I’m just setting up a nice MagicMirror for in my livingroom for me and my family. And I found so many great modules here that they can’t fit all on one page. But okay… I must check my config.js were I went wrong because the pages aren’t switching. At the issue page of Edward someone issues a problem and put his config.js code there. I’ll check his motition there hoping I can spot the differance. :winking_face: Thanks again for your help! With kind regards, Mike (from the Netherlands)

I ended up removing the ~/MagicMirror folder entirely, reinstalling, and reinstalling MMM-GooglePhotos and all seems to be working now! thanks for your help, @Sean ! -kal

@sepal22 EDIT alexyak/camera module is not built for displaying taken photos on MM screen. Of course, you can modify it. When the module gets SEND_EMAIL socketNotification from node_helper, the payload will contain dataUrl. I think it might be the url or path of photo taken by this module. Now you can create code for displaying photo on screen with that value. I’m seeing inside of that module, and I’ve found it has the feature selfie snapshot already. If that module works properly, taken photo will be shown on MM screen. If not so, your module has a problem or not be activated.

@richland007 Unless someone tells different, from my point of view you do not have any CPU or memory issues. In fact, it makes me wonder why I am seeing the electron.js processes so high in my output. I do not use MMM-watchdog and I do not know exactly what it is doing. Do not know what it is pinging, but something on your MM makes it time out and as a cause it restarts mm. The log only tells you that it failed, but not what exactly failed. Would be nice to know how you can send this ping manually, then you can observe the behavior yourself. I take it, that you have your monitor connected to your Pi. So MM not running as server only and the display not on a client. Anyway, good to hear that you potentially have found the issue and you learned a bit of Linux on the side.

@dcalix No nothing in addition to the above other errors have arisen… read here from the beginning for more details https://forum.magicmirror.builders/topic/8569/mmm-mirrormirroronthewall-installation-issue/63?page=7

@keonhee 한국분이니까 한국어로 답변을… 로그는 정상인데요. 화면에 아무것도 안뜨나요? 아니면 소리만 안나나요? eouia0819@gmail.com으로 메일 주시거나 텔레그램 @eouia로 톡 주세요. 카톡은 안해요.

@sean said in Alert module is always on: @cr4z33 Remove position field? Not tested. @bkeyport said in Alert module is always on: Position field isn’t supposed to be used. { module: "alert", }, Alert will pop over entire screen when called. Above is as shown within the sample config Ouch my bad. :grimacing_face: Thanks to both of you.

Re: Changing compliments I am new to a lot of this but getting the hang of it. Anyways, I am making a MagicMirror for my gf and we have a special time of the day (4:22). I was wondering how I would go about setting up a few compliments that randomize at 4:22 in the morning and in the afternoon?