@sdetweil thank you!

@cmer3 It looks like the sample locations are postal codes for the UK? Will this work for US postal codes in the format 12345-6789?

@misha2257 if you search on that error you should find instructions on how to compile the DTCs into the proper overlay format on the OS that you’re using. there are OS commands it’s not a magic mirror problem it’s an OS I2C bus interface issue

@sdetweil thanks - that seemed to have worked and makes sense!

@KristjanESPERANTO the entire MMM-Pir modul. Like /* { module: 'MMM-Pir', position: 'bottom_left', config: { debug: false, delay: 1 * 30 * 1000, turnOffDisplay: true, mode: 1, ecoMode: true, displayCounter: true, displayBar: true, displayStyle: "Text", displayLastPresence: true, lastPresenceTimeFormat: "LL H:mm", mode6_gpio: 20, mode6_clearGpioValue: true, pir_gpio: 21, pir_reverseValue: false } }, */ The display runs now 24/7, but i got my departures ;-) I will take a look at the problem with “user_presence” later.

@Max-0 see https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

@dpnguyen Hmmm… Weird. In my test (with my calendars), I cannot find anything wrong. Try self-testing more. Remove all other modules except CX2 from config. (You can backup your original config.js), Then try again. You have two month views on a screen. Usually, screen is not so huge to hold multi month views. Is there any special reason? Anyway try with just one month view. Investigate the Front-end Log and Backend-log. Is there any suspicious message in both? Especially in scanning result in back log, how it shows? (EXAMPLE) [29.08.2023 08:58.32.610] [LOG] [CALEXT2] calendar:Gracie >> Scanning start with interval:60000 [29.08.2023 08:58.32.843] [LOG] [CALEXT2] calendar:Gracie >> Scanned: 18, Selected: 18 [29.08.2023 08:58.33.977] [LOG] [CALEXT2] calendar:General >> Scanning start with interval:60000 [29.08.2023 08:58.34.360] [LOG] [CALEXT2] calendar:General >> Scanned: 23, Selected: 23 [29.08.2023 08:58.34.662] [LOG] [CALEXT2] calendar:Nora >> Scanning start with interval:60000 [29.08.2023 08:58.35.435] [LOG] [CALEXT2] calendar:Nora >> Scanned: 96, Selected: 96 Were the scanned/selected results changed in close cycles? (You can test it with short scanInterval of calendar) Without original ical data and environment, I cannot reproduce your issue. Could you send me the original config.js and custom.css privately? (eouia0819@gmail.com) I’ll drop your ical after investigation.

@sdetweil thank now I understand where, thank you it works. U help me! :-)

@Pjarki said in MMM-YoutubeChannelStats not showing anything: When running the mirror I get this error, dont know if it is related or not: [1376:0822/181638.160309:ERROR:gl_surface_presenta tion_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! nah, thats from the opengl driver…

@OmaBosselt Heureka or not but it works fine… for me. :o) mapFixedArea: true, // if set, the defined area is shown, if not the area is calculated from the plane locations Thanks

Hi, I don’t use that module, but you could try mmm-soccerlivescore module, which works for me

@bruteforce Install this : https://github.com/The-Exterminator/MyMagicMirror/blob/main/MMM-MagicMirrorCompliments/README.md Is work, and easy to set up.

@ankonaskiff17 I have a 4 wire sensor, eunning sudo i2cdetect -y 1 i am getting an error thet could not open file. Anny sugestions?

@lparco you can also try https://github.com/jalibu/MMM-RAIN-MAP which is almost the same module with a few more features.

@videogame95 same as every other module. github. easy search github mmm-alexacontrol

@superior_carter you would have to look at the google requirements for token refresh… I don’t know if they are the same for every api service… in a few services this was not required… but then bad actors misused the api to hammer the google systems, so they have been updating the apis to use oauth and token refresh.

Update. I started fresh with Buster instead of Bullseye and followed these instructions to get MMM-PIR-SENSOR working. https://www.reddit.com/r/MagicMirror/comments/u1eq9u/problem_setting_up_pirsensor_with_magicmirror/

@plainbroke - Huh. Those appear to be graphics driver problems. They’re a known issue between the Raspian OS and the Electron framework. They shouldn’t be related to your issue with the module. Okay, let’s dig up the other log files. Easiest thing to do is to make sure your mirror is running and then use the web browser to view the mirror interface. First, edit the config.js to allow other computers to access the interface. Change the address and ipWhiteList to allow other computers to see your mirror: var config = { address: "0.0.0.0", port: 8080, ipWhitelist: [], ... Save and restart your mirror instance with pm2 restart 0. Now you should point your web browser at the IP address of your mirror. Remember to add the port to the url you enter in the address bar. For example: http://192.168.0.15:8080 should get you your interface if your IP address is 192.168.0.15. Anyhow, you should see the mirror interface in your web browser. Now you need to pull up the developer tools, usually by hitting F12 on your keyboard (I know it works in Chrome and Firefox). A section of your browser will open up with the developer tools. There will be a tab labeled console. These are the other logs I mentioned earlier. Click on the console tab and look for anything that mentions the MMM-SingleStock module. Let us know what it says, especially if it mentions an error.

@Bungle68 have you tried to change the value of fadeSpeedInSeconds to a higher number (e.g. 10)? Just play around with this number until the animation speed is good for you. Usually, a higher number means a slower animation.