@jukums said in ZOOM /Scaling: Ok, got same problem… Connecting the keyboard and hitting Ctrl+0 to reset zoom seemed to work. Seems that zoom value is being cached somewhere… Thanks a lot for this. I am currently in setup, so I still have a Keyboard connected and this did the trick.

Hmm Okay Thanks

Super! Thank you

I remove MMM-DHT Sensor, MMM-DHT22 and MMM-dht22, I did not removel node-dht-sensor because I don’t know how to remove, I reinstall MMM-DHT Sensor, I left in GPIO 2 (3) not to change the config.js and the MMM-DHT-Sensor.js, it does not work either, after several relaunch of MM, it worked one time but after a relaunch again it does not work anymore. . It’s crazy, I ordered a new DHT22 because it may be defective …

Howdy folks, As the title suggests im looking to run multiple instances of MMM-google-route on different pages of MMM-Pages. so i want one page displaying best route to work and one page displaying best route to office. do i need to rename modules to have em run on different pages? many thanks, Richie

hi been using mm for a while just put a new card with noobs to start a new mirror but on boot message saying no vga cable yet the original card is ok.tried with raspian loaded and same prob. any ideas why this should happen with two latest updates. cheers,geo

@do1mps the calendar reader expects ics format. others have been able to download ics file ( into module folder) and point config to the downloaded file

Hi, Generally, this error happen when you don’t do the step 4 OAuth Consent Screen setup of the Google Assistant Setup

Thanks. That worked.

@pw94 I had issues also running those PIR mods… the only mod that worked for me was ‘MMM-NewPIR’, I love this module. It also has the ability to not TURN OFF the display but rather just throw up a black screen or “hide” the modules . my config for MMM-NewPIR is below if it helps any. { module: 'MMM-NewPIR', position: 'bottom_left', config: { useSensor: true, sensorPin: 22, reverseValue: false, delay: 2* 60 * 1000, turnOffDisplay: false, ecoMode: true, governor: "", text: "", counter: false, rpi4: true, debug: false } },

Had the same issue my solution was to go back and regenerate a new Auth Code and subsequent new Refresh Token. I remember a logfile stating this has expired. My take is: Client ID is permanent Client Secret is permanent Auth Code expires Refresh token will not work if the included Auth Code has expired

Are there no aspect ratio settings?

@banbutcher You’re right, it sorted itself out this morning. That’s really weird. The guy who wrote the module isn’t maintaining it, but it would be nice if someone who knows code could take a look at it and fix it. Not a big issue but certainly annoying!

I tried to edit my 1st post but I can’t: “You are only allowed to edit posts for 3600 second (s) after posting”. in the case I published which is: **** Liste des Périphériques Matériels CAPTURE **** carte 1: USB [WordForum USB], périphérique 0: USB Audio [USB Audio] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pi@raspberrypi:~ $ aplay -l **** Liste des Périphériques Matériels PLAYBACK **** carte 0: b1 [bcm2835 HDMI 1], périphérique 0: bcm2835 HDMI 1 [bcm2835 HDMI 1] Sous-périphériques: 4/4 Sous-périphérique #0: subdevice #0 Sous-périphérique #1: subdevice #1 Sous-périphérique #2: subdevice #2 Sous-périphérique #3: subdevice #3 carte 2: Headphones [bcm2835 Headphones], périphérique 0: bcm2835 Headphones [bcm2835 Headphones] Sous-périphériques: 4/4 Sous-périphérique #0: subdevice #0 Sous-périphérique #1: subdevice #1 Sous-périphérique #2: subdevice #2 Sous-périphérique #3: subdevice #3 pi@raspberrypi:~ $ my mic in on card 1, device 0 because " Liste des Périphériques Matériels CAPTURE", and my 3.5 jack headphone is on card 2, device 0 because " Liste des Périphériques Matériels PLAYBACK" , and in card 0, device 0 it’s HDMI. is it correct ?

Hi, can someone confirm that https://github.com/alexBeuth/MMM-germanwordclock is not running un 2.11/2.12 anymore? Module just doesn’t show up.

@sdetweil THANKS YOU! That’s the problem, we dont need to use API!

rm -rf /kalliope and no rm -rf / kalliope but it’s the same