The Raspberry has its own power supply. It is connected to the Hdmi controller via HDMI cable. The Hdmi controller has its own power supply and is connected to the monitor.
1. Display Turns On/Off
The mirror actually works fine, but the display turns on every now and then. In the console I get the output “The Voltage is low”. However, the Raspberry Pi never restarts, only the display turns on/off.
Actually I assume that the power is sufficient. Can you give me some advice? Possibly the power supply is not enough.
2. Witty Pi Mini und i2cDetect
I bought the Witty Pi Mini and installed it according to the instructions. I would like to start the Raspberry Pi in the morning and turn it off in the evening.
I have built the controller on the Raspberry Pi. So the USB cable from the HDMI controller is connected to the PI.
I can also start the mirror via the switch. However, nothing is detected with i2cdetect - 0 or 1.
I did literally nothing but remove any value from “micConfig:” section in MMM-GoogleAssistant.
But now that you make me double check, I saw that this does not defaults the recorder to “sox”. It actually defaults to “arecord” again.
Then actually, the working step is removing directive
It somehow prevents GA to try going directly “under” PulseAudio, and makes it use the PulseAusio ALSA plugin instead.
Once both goes through PulseAudio, they can work together, as PulseAudio cam make multiple wave recorders work by default
I get a blank screen and says it cant reach a site. So I thought I would just restart the MagicMirror and all would be good. When I run the command npm start I get the following error.
/home/mark/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! email@example.com start: sh run-start.sh
npm ERR! spawn ENOENT
npm ERR! Failed at the firstname.lastname@example.org start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
After looking I did an npm audit and npm audit fix. still the same issue.
Any suggestions to fix this.
Here is the full log
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
2 info using email@example.com
3 info using firstname.lastname@example.org
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle email@example.com~prestart: firstname.lastname@example.org
6 info lifecycle email@example.com~start: firstname.lastname@example.org
7 verbose lifecycle email@example.com~start: unsafe-perm in lifecycle true
8 verbose lifecycle firstname.lastname@example.org~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/mark/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle email@example.com~start: CWD: /home/mark/MagicMirror
10 silly lifecycle firstname.lastname@example.org~start: Args: [ ‘-c’, ‘sh run-start.sh’ ]
11 info lifecycle email@example.com~start: Failed to exec start script
12 verbose stack Error: firstname.lastname@example.org start: sh run-start.sh
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at ChildProcess.emit (events.js:189:13)
12 verbose stack at maybeClose (internal/child_process.js:970:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
13 verbose pkgid email@example.com
14 verbose cwd /home/mark/MagicMirror
15 verbose Linux 4.15.0-129-generic
16 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
17 verbose node v10.15.3
18 verbose npm v6.9.0
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error firstname.lastname@example.org start: sh run-start.sh
23 error spawn ENOENT
24 error Failed at the email@example.com start script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]