You might be interested in this. It’s not titled For absolute beginners, but it’s close enough.
While trying to debug modules, I’ve been given quite mixed feedback regarding what to use to print messages to console, on either local system or in remote browser DevTools.
So far, I have found the only reliable way that always seem to print something in the browser, is using console.error(). The others have varied. I’m on MM v2.2.2 (master).
I reinstalled the whole system using another SD-card.
Now I can use the seperate USB-Mic and the audio Out comes from the other USB-Soundcard.
After that I installed all my modules like MMM-Podcast.
I played the video and … sound comes from the audio jack again:-(
However the usb mic and alexa are still working fine. It is just MMM-Podcast which uses the audio jack.
How can that be? I installed the dependecies especially the omxplayer. But that can´t be the reason, or what do you think?
Bus 001 Device 004: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller
Bus 001 Device 005: ID 0d8c:0014 C-Media Electronics, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
**** Liste der Hardware-Geräte (PLAYBACK) ****
Karte 0: Device_1 [USB Audio Device], Gerät 0: USB Audio [USB Audio]
Sub-Gerät #0: subdevice #0
sudo nano ~/.asoundrc
Do you have an idea? Seems like I am almost there.
I’m trying to install MM on my synology. The steps I already performed:
Install nodejs on synology
Install MM in serveronly mode
Copied config file and tried to whitelist IP address
I now can access the page on xxx.xxx.x.x./MagicMirror/ but i get an error that the config file is missing although it is available.
If I look at the console error I see that http://xxx.xxx.x.x./socket.io/socket.io.js is not loading. I already tried to change this to a CDN pointed location, with no luck.
I’m kidda stuck here, can anybody help me on the way?
I have problem with polish letters such as “ą,ć,ś,ń” but only in News Feed module. In Calendar module everything is alright. Here’s some screenshots:
I know there was topic about about 7 month ago but it didn’t solve my problem.
I think you might be able to rebuild MM…
it takes a few minutes, but that is one thing that has helped me in the past fix several different errors.
Also, you can re-install the MM and your modules, especially the last one you added prior to getting this error…
Start with the last module… cd modules/[last-module-name] >>> npm install
Then run the npm install with MM. Or, the npm rebuild
then restart MM
Also, try rebooting the Pi by shutting it off, then turn it back on.
(works better to help fix errors than using restart)
@meyraa from what i heard in the forum here, the users of the pi zero reported all that midori is the only browser on this pi that has no performance issues. The advantage of the chromium browser is that it is completely compatible, as electron internally uses the chromium project.
ty for the code. Sadly it didn’t help. It’s so weird, I set the whole css and config folder back to master-version and I still get a black screen. That are the only two folders I touched so far.
I think the only way I can fix this is to reinstall everything.
@bbdv I had the same problem. Midori has problems with ES6 and the arrow functions. I just deinstalled Midori and installed chromium-browser.
You can rewrite the startMidori.sh
xset -dpms # disable DPMS (Energy Star) features.
xset s off # disable screen saver
xset s noblank # don’t blank the video device
chromium-browser --no-sandbox --disable-infobars --start-maximized --noerrdialogs --kiosk --incognito http://localhost:8080
If you want you can rename startMidori.sh to startChromium.sh, but don’t forget to rename it in the startMagicMirror.sh too.
My startMagicMirror.sh looks like this:
node serveronly &
sudo xinit /home/pi/startMidori.sh
@sdetweil said in Raspberry 2 clean install showing as black screen:
npm remove electron
npm install email@example.com
I will have to try that. Thank you! My fix had been to install another web browser and use that. Electron’s built-in browser seemed to always show a black screen.