@cyberphox, Sorry for the “New Year Delay”. I use docker for all my stuff. But besides that, I mainly used this tutorial: https://www.home-assistant.io/docs/ecosystem/nginx_subdomain/ It’s about home-assistant, but the principle works for everything @sdetweil, Thank you a lot. That was my fear

@sean Thank you Sean it works, sorry I didn’t fully understand the title replace concept. Happy new year to you.

@maykesplana said in Installing MagicMirror2 on Ubuntu Mate 16.04 issue with electron: I have a device with Atom CPU in it and will try to install the 32Bit Ubuntu next time as it was unsuccessful try last night. If that Atom CPU is 64bit then use the 64bit version of ubuntu. However, the 32bit version of ubuntu works quite well with MM. Have a look here. There’s a video link under the last picture. You can watch how well it works. https://forum.magicmirror.builders/topic/6376/macmirror

@j-e-f-f Sure, that’s the magic of the overflow: hidden style. But what puzzles me is this: An example: If you run a webpage in fullscreen mode (either through Electron using Chromium or in a regular browser), and style the body like this: body { background-color: #333; width: 100vw; height: 100vh; padding: 0; margin: 0; overflow: hidden; } you will have a grey area that takes up the entire width & height of your screen. If, on the other hand, you styled the body tag like this: body { background-color: #333; width: calc(100vw-10px); height: calc(100vh-10px); padding: 0; margin: 0; overflow: hidden; } you will have a grey area that is 10px shorter and narrower than the available screen space. The only reason this wouldn’t be the case is if the html tag has a margin or padding (which would restrict the amount of space available to the body tag) or if you’ve specified a specific screen size directly in Electron (using electronOptions.width and electronOptions.height). It’s no different than the standard body styles defined in MagicMirror’s main.css file - in there, a margin of 60px is set and then the height & width are set with width: calc(100%-120px) and height: calc(100%-120px) respectively.

I’m still curious where the default clock module gets its font css from… I was hoping to selectively change the size/font of the month in the default clock.

Re: Unable to install dependencies - npm not found With Rasbian of 2018-11-13, I had the same issue. So I installed only npm, sudo apt-get install npm sudo npm install -g npm@latest Also I used the pre-built node which is 8.x in the latest version of Rasbian. While I install, I made a video and please check https://youtu.be/UBgH5hejYtM. Thanks, Dependency Versions OS : 2018-11-13-raspbian-stretch-full.img MagicMirror2 : 2.5.0 MMM-Hotword : 1.1.0 MMM-AssistantMk2 : 2.1.2

So I got two steps further: First the easy fix for the fetchInterval. Those config parameter needs to go into the config section of course … doh :smiling_face_with_smiling_eyes: module: "calendar", header: "Kalender", position: "top_left", config: { fetchInterval: 600000, maximumEntries: 5, calendars: [ { symbol: "calendar-check-o ", dateFormat: "dd.MM.yyyy", url: "https://url-to-ical-sevrer/", } ] } }, The problem, why the calendar couldn’t be fetched, is TLS related. I used the debug.js file which I found in the modules folder to trace down the error: Error "unable to verify the first certificate" The provided certificate is signed by let's encrypt - as a workaround I currently used: process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0; I know that this is not the recommended way. I am running node version 9.11.2 - maybe someone has a working fix for that problem?

Hello does anybody can “translate” this Error Message when i start MM² with npm start 0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 2 info using npm@6.4.1 3 info using node@v10.15.0 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle magicmirror@2.5.0~prestart: magicmirror@2.5.0 6 info lifecycle magicmirror@2.5.0~start: magicmirror@2.5.0 7 verbose lifecycle magicmirror@2.5.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle magicmirror@2.5.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games 9 verbose lifecycle magicmirror@2.5.0~start: CWD: /home/pi/MagicMirror 10 silly lifecycle magicmirror@2.5.0~start: Args: [ '-c', 'sh run-start.sh' ] 11 info lifecycle magicmirror@2.5.0~start: Failed to exec start script 12 verbose stack Error: magicmirror@2.5.0 start: `sh run-start.sh` 12 verbose stack spawn ENOENT 12 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18) 12 verbose stack at ChildProcess.emit (events.js:182:13) 12 verbose stack at maybeClose (internal/child_process.js:962:16) 12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5) 13 verbose pkgid magicmirror@2.5.0 14 verbose cwd /home/pi/MagicMirror 15 verbose Linux 4.14.90+ 16 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 17 verbose node v10.15.0 18 verbose npm v6.4.1 19 error file sh 20 error code ELIFECYCLE 21 error errno ENOENT 22 error syscall spawn 23 error magicmirror@2.5.0 start: `sh run-start.sh` 23 error spawn ENOENT 24 error Failed at the magicmirror@2.5.0 start script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ] thank you…

@idoodler Originally I translated them by creating a new file called il.js and added it to the translations.js file. By debugging and reading the thread mentioned above I understood that something was wrong with the locale. It got me thinking that Israel locale is he_IL and that maybe I used the IL instead of the HE. That means that the MM uses that locale for other things too. I changed the file name to he.js and updated the tranlations.js and that got things to work.

@xclasher-0 MMM-voice is in its own page and there is no other module linked with that page so it won’t show anything other than the voice module, voice itself does not work like that, it seems like you need Hello Lucy as that is more the features of that upgraded module.

@strawberry-3-141 I’m having a little trouble with MMM-voice it comes up with an error anytime you view the mirror through mmm remote control, but you say the mirrors magic word and it works as it should displaying voice by the mic 🎤 viewing it via VNC it works perfectly without Errors but then viewing it through remote control it comes up with error, any help please

SOLVED This is not really a solution, but my error was that I was logged in on “Ubuntu on Wayland” which doesn’t have DPMS. On the login screen of Ubuntu you can click the little gear-icon and choose what kind of Ubuntu you want to login to. Wayland is a bit restricted, so just go with “Ubuntu” and not “Ubuntu on Wayland”

@akkor said in Problem server client configuration: I could test but I need your assistance 'couse I’m not a programmer I’m just good following guide… Why I think it won’t work. You’ll be running MM and MMM-voice on the server machine. The client machine will only have a browser pointed at MM running on the server machine. The client has no way of accepting the voice commands because only the browser is running. Now, if you had a microphone (at the client machine) with a cable that reached all the way to where the server machine is . . . :)

@dazza120 - Remember to mark the topic as solved. I’m glad you got it working.

I recently setup a MagicMirror on a Pi 3B+ with a physical monitor attached and all went well. Today I was hoping to get things setup with the various modules that I require. To do this I was hoping to VNC into the box for visual checks whilst using SSH for implementing the modules etc. However, without a physical monitor attached via HDMI and using VNC all the modules output is a mess of overlapping content. Is there a way to force the screen resolution so that appears as expected via VNC ? Thanks.

@oththegentel It sounds like your MagicMirror instance is not running. How did you start MagicMirror, do you have pm2 installed?

@el-bardo You never know how other module devs use such functions. Always use the most non-inversive way which would be the custom CSS way.

@sollekram Awesome!

Up… and Running … Now I can hear the hadrdisk working… I don’t wounder how much access the HD does , the sd cards died quickly :(

I solved this link! https://forum.magicmirror.builders/topic/9258/unable-to-install-dependencies/