Are you working on your raspberry? Or are you connected via ssh?
If you are connected via ssh you need to run DISPLAY=:0 npm start instead to tell the raspberry to use the display connected to the raspberry instead of the not working ssh connection
Read the statement by Michael Teeuw here.
Posts
-
RE: Starter problem
-
RE: Starter problem
Hi Kurt,
before you run
npm startyou need to change into the right directory. Default would becd MagicMirror npm install npm startThe
npm installcommand only needs to be run first time after you downloaded the MagicMirror package. If you have already done that you can skip this step. -
RE: Showcase Guidelines
@paviro said in Showcase Guidelines:
You can now edit posts forever :)
Yeah, finally :thumbsup_tone1:
I update my module threads yesterday -
RE: Module about module updates
@tosti007 said in Module about module updates:
@yawns Checked again, it cycles through all the modules except the default modules.
My bad, you are absolutely right. Sorry!
-
RE: [ORDER CLOSED] Two way mirror order in Germany
@Goldjunge_Chriz
Köln - Koblenz is 120km one way, which would be okay but not preferred. We only have a VW Fox (Polo size), I don’t feel very comfortable transporting so many mirrors in a small car.
If this is the only safe way I’d do that -
RE: How I got my Magic Mirror working on a Raspberry Pi 0 (zero)
@SebTota
cp -r source destination -
RE: MMM-FRITZ-Box-Callmonitor
@ostfilinchen
There is a " missing after passwort -
RE: [ORDER CLOSED] Two way mirror order in Germany
My measurements need to be reduced to 765mm * 765mm
The rest (polished edges, delivery to Cologne) stays the same.Confirmed with this change.
Sidenote: @Binog would like to share delivery to Cologne with me. So if he confirms his order, then please take this into your calculations ;)
-
RE: Trouble getting it to start
@PhilsterM9 said in Trouble getting it to start:
I am not sure if it is supposed to happen!
Just as a side note: This is linux. No news is good news. By default there is no feedback like “1 file copied”.
If you don’t feel comfortable with the shell you can work on your raspberry directly using the file explorer -
RE: Alert box location
I just did a quick test on my laptop.
Edit~/MagicMirror/css/custom.cssand add the following:.ns-box { top: 50%; }This should move the alert box to the vertical center. You can use the config position @MichMich mentioned to move to the horizontal center.
-
RE: Something I'm working on ...
Okay, I was able to add my module right now. However now it says it cannot find the readme. This affects all modules, not only mine.
-
RE: Something I'm working on ...
@tosti007 said in Something I’m working on ...:
I cannot upload any modules at all, either with pc (windows, firefox) or android (chrome). Is this currently supposed to be like that (aka disabled) or am i doing something wrong? :) I am on the correct github account and the repositories are public.
I just tried as well. You can click “Step 1 - Select repository” but nothing happens. The console is showing a HTTP500 error:
vue.js?3de6:5729 Download the Vue Devtools for a better development experience: https://github.com/vuejs/vue-devtools vue-resource.common.js?2f13:1071 GET http://beta.magicmirror.builders/api/me/repositories 500 (Internal Server Error) (anonymous) @ vue-resource.common.js?2f13:1071 PromiseObj @ vue-resource.common.js?2f13:198 xhrClient @ vue-resource.common.js?2f13:1025 sendRequest @ vue-resource.common.js?2f13:1140 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 before @ vue-resource.common.js?2f13:966 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 timeout @ vue-resource.common.js?2f13:1014 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 method @ vue-resource.common.js?2f13:980 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 body @ vue-resource.common.js?2f13:853 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 jsonp @ vue-resource.common.js?2f13:942 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 header @ vue-resource.common.js?2f13:997 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 cors @ vue-resource.common.js?2f13:824 exec @ vue-resource.common.js?2f13:1097 next @ vue-resource.common.js?2f13:1122 (anonymous) @ bootstrap.js?5e63:36 exec @ vue-resource.common.js?2f13:1097 (anonymous) @ vue-resource.common.js?2f13:1125 PromiseObj @ vue-resource.common.js?2f13:198 Client @ vue-resource.common.js?2f13:1090 Http @ vue-resource.common.js?2f13:1350 Http.(anonymous function) @ vue-resource.common.js?2f13:1379 fetchRepositories @ AddModule.vue?5997:99 boundFn @ vue.js?3de6:131 mounted @ AddModule.vue?5997:141 callHook @ vue.js?3de6:1833 insert @ vue.js?3de6:2007 invokeInsertHook @ vue.js?3de6:4159 patch @ vue.js?3de6:4301 Vue._update @ vue.js?3de6:1722 (anonymous) @ vue.js?3de6:1697 get @ vue.js?3de6:740 Watcher @ vue.js?3de6:732 Vue._mount @ vue.js?3de6:1696 Vue$3.$mount @ vue.js?3de6:5716 Vue$3.$mount @ vue.js?3de6:7873 initRender @ vue.js?3de6:2218 Vue._init @ vue.js?3de6:2580 Vue$3 @ vue.js?3de6:2624 (anonymous) @ app.js?8b67:47 (anonymous) @ app-c86aef609d.js:1578 __webpack_require__ @ app-c86aef609d.js:20 (anonymous) @ app-c86aef609d.js:64 (anonymous) @ app-c86aef609d.js:67 AddModule.vue?5997:105 Responsebody: "↵↵ ↵ ↵ ↵ ↵ ↵ ↵ <div>↵ <h1>Whoops, looks like something went wrong.</h1>↵ <h2>↵ 1/1↵ RuntimeException in <a>Client.php line 70</a>:Pipeline.php line 104↵ <li>at Pipeline->then(<em>object</em>(Closure)) in <a>Router.php line 644</a></li>↵ <li>at Router->runRouteWithinStack(<em>object</em>(Route), <em>object</em>(Request)) in <a>Router.php line 618</a></li>↵ <li>at Router->dispatchToRoute(<em>object</em>(Request)) in <a>Router.php line 596</a></li>↵ <li>at Router->dispatch(<em>object</em>(Request)) in <a>Kernel.php line 267</a></li>↵ <li>at Kernel->Illuminate\Foundation\Http\{closure}(<em>object</em>(Request)) in <a>Pipeline.php line 53</a></li>↵ <li>at Pipeline->Illuminate\Routing\{closure}(<em>object</em>(Request)) in <a>CheckForMaintenanceMode.php line 46</a></li>↵ <li>at CheckForMaintenanceMode->handle(<em>object</em>(Request), <em>object</em>(Closure)) in <a>Pipeline.php line 137</a></li>↵ <li>at Pipeline->Illuminate\Pipeline\{closure}(<em>object</em>(Request)) in <a>Pipeline.php line 33</a></li>↵ <li>at Pipeline->Illuminate\Routing\{closure}(<em>object</em>(Request)) in <a>Pipeline.php line 104</a></li>↵ <li>at Pipeline->then(<em>object</em>(Closure)) in <a>Kernel.php line 149</a></li>↵ <li>at Kernel->sendRequestThroughRouter(<em>object</em>(Request)) in <a>Kernel.php line 116</a></li>↵ <li>at Kernel->handle(<em>object</em>(Request)) in <a>index.php line 53</a></li>↵ ↵</h2></div>↵↵ ↵ ↵"bodyBlob: BlobbodyText: PromiseObjdata: (...)get data: ()arguments: (...)caller: (...)length: 0name: "get"prototype: Object__proto__: ()[[FunctionLocation]]: vue-resource.common.js?2f13:856[[Scopes]]: Scopes[4]set data: (body)arguments: (...)caller: (...)length: 1name: "set"prototype: Object__proto__: ()[[FunctionLocation]]: vue-resource.common.js?2f13:859[[Scopes]]: Scopes[4]headers: Headersmap: Object__proto__: Objectok: falsestatus: 500statusText: "Internal Server Error"url: "/api/me/repositories"__proto__: Object (anonymous) @ AddModule.vue?5997:105 -
RE: LocalTransport-Module and calendar
@tosti007
Well, feel free to change the code and submit a pull request to the original developer and it’s repository.
This way you make it official and everyone can benefit from it. If you just hack the code you would run into trouble if the developer releases an update. -
RE: WE WANT YOU! [New Moderators]
@tosti007 said in WE WANT YOU! [New Moderators]:
@strawberry-3.141 how about yourself? You also seem active and always really helpful!
I would recommend him too, but he is currently working on his bachelor stuff. I could imagine he is really short on time
-
RE: [ORDER CLOSED] Two way mirror order in Germany
@olexs
The language in this forum is english. Some users replied in German, maybe because they fear mistakes when writing in a foreign language and not native language.
But we should stick with english, so everyone can follow this thread. -
RE: White Screen after starting Magic Mirror
@Squirrel
Yes, I forgot to mention that. You can also press ctrl + c in console to kill the mirror process. So you don’t have to close the terminal every time -
RE: White Screen after starting Magic Mirror
Are you working on your raspberry directly? You should be able to switch with alt + tab.
As an alternative you could run
node serveronly, open the browser on your own and go to http://localhost:8080 -
RE: [ORDER CLOSED] Two way mirror order in Germany
@Binog
I am working in cologne (Bayenthal), so I guess delivery will be cologne. Sure, if this is fine for Chris we can share delivery