I did find it could be done when a template was available, something like this one for Home Assistant code_text ```climate: platform: mqtt name: "Master Bedroom" current_temperature_topic: "homeassistant/sensors/flair/puck/Master Bedroom-30f/Temperature" current_temperature_template: "{{(value * 9/5)+32}}" precision: 0.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 device: “plughw:0” 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

@sdetweil said in Help with MMM-SleepWake: @chanster ok, my module doc gives u the new lines for motion.conf Yes, nothing wrong with your docs at all.

ok, I will look at it. Thank you. See if that’s what’s blocking the connection.

@gkchimz said in Hello Lucy - face at Startup: How do I get the face to show when the mirror starts ? I have go the voice working , but not the face. You need MMM-EasyPix (or another image module). EasyPix was designed for Lucy and works by default with her. Out of interest is it possible to change the face? Yes, any image you like (just about) Also can the start-up sound/greeting be set to be scheduled or by PIR sensor? Not as written. Feel free to fork the module and make any changes you like. :-)

@sdetweil Hehe, I only remembered to mention the script after I already replied. Let me take this opportunity to thank you for what you do or this community!

Thank you @MaXi-XCeL that was the problem. Case sensitive variables? Come on… :-( And you need the useBeaufort: false to have it work. useBeaufort: false, useKMPHwind: true, Thank you again, on step closer.

cd into ~/magicmirror/run folder and execute docker-compose up -d --force-recreate.

@ofb its probably the port number. change the port in config.js to 8090

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! magicmirror@2.7.1 start: sh run-start.sh npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the magicmirror@2.7.1 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 npm@6.9.0 3 info using node@v10.15.3 4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ] 5 info lifecycle magicmirror@2.7.1~prestart: magicmirror@2.7.1 6 info lifecycle magicmirror@2.7.1~start: magicmirror@2.7.1 7 verbose lifecycle magicmirror@2.7.1~start: unsafe-perm in lifecycle true 8 verbose lifecycle magicmirror@2.7.1~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 magicmirror@2.7.1~start: CWD: /home/mark/MagicMirror 10 silly lifecycle magicmirror@2.7.1~start: Args: [ ‘-c’, ‘sh run-start.sh’ ] 11 info lifecycle magicmirror@2.7.1~start: Failed to exec start script 12 verbose stack Error: magicmirror@2.7.1 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 magicmirror@2.7.1 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 magicmirror@2.7.1 start: sh run-start.sh 23 error spawn ENOENT 24 error Failed at the magicmirror@2.7.1 start script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ]

hello, ive been using Face5 for a while pretty nice ,is there a way to change it to arabic numbers ? thanks

it works with bizType to tuya thx to slametps

@Egnos try this pm2 stop all export NODE_OPTIONS=--max_old_space_size=4096 npm start u can add that export line to the installers/mm.sh if using pm2

@sdetweil ok so what do I need to do to provide you the information you need?

@jew_lion openweather.com? appid shouldn’t change, just identifies u

Hi, I’m having an issue with the MMM-GooglePhotos module where it won’t display new pictures when I add them to my Google Photos album. The only way I can get the added pictures to show is to restart MagicMirror. Any ideas on getting this to work without using a workaround of programming a MagicMirror restart every so often?

@sdetweil I will have to mess with that when I have more time.

@kvicksson that code will be in the new release on Friday, 1/1

@jthewarrior7 weird… kiosk is what removes the titlebar

Perhaps you deal with these two great modules and could get them to work together without any impacts. I could not. After I installed and set up the MMM-NewPIR, I installed and set up the MMM-GoogleTasks. After that, the graphical output of the count-down bar disappeared. Did anybody experienced the same behaviour?