• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
  1. Home
  2. cyclonej
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
C
Offline
  • Profile
  • Following 0
  • Followers 0
  • Topics 3
  • Posts 11
  • Groups 0

cyclonej

@cyclonej

3
Reputation
1
Profile views
11
Posts
0
Followers
0
Following
Joined Dec 25, 2024, 1:33 AM
Last Online Feb 10, 2025, 1:39 AM

cyclonej Unfollow Follow

Best posts made by cyclonej

  • My Goodness, My Mirror

    Framed and hung in kitchen. Raspberry Pi 5 and 22" Asus monitor (case removed), mounted in handmade wood frame. Total weight is about 10 pounds. Hanging on a gorilla hook rated for over 20 pounds.

    Displaying default clock and default calendar module in upper left, default weather module twice in upper right. MMM-CalendarExt3 at bottom, which pulls calendar data from another default calendar module which is not displayed. Using the two separate default calendar modules allowed me to show more events in MMM-CalendarExt3 than are displayed in the upper left default calendar module.

    45d38933-12b7-4336-b40a-04c2d3ed96da-image.png

    posted in Show your Mirror
    C
    cyclonej
    Jan 16, 2025, 6:19 PM

Latest posts made by cyclonej

  • My Goodness, My Mirror

    Framed and hung in kitchen. Raspberry Pi 5 and 22" Asus monitor (case removed), mounted in handmade wood frame. Total weight is about 10 pounds. Hanging on a gorilla hook rated for over 20 pounds.

    Displaying default clock and default calendar module in upper left, default weather module twice in upper right. MMM-CalendarExt3 at bottom, which pulls calendar data from another default calendar module which is not displayed. Using the two separate default calendar modules allowed me to show more events in MMM-CalendarExt3 than are displayed in the upper left default calendar module.

    45d38933-12b7-4336-b40a-04c2d3ed96da-image.png

    posted in Show your Mirror
    C
    cyclonej
    Jan 16, 2025, 6:19 PM
  • RE: Calendar number of events to display

    @sdetweil I found a fix.

    1. add a second default MM calendar module as a complete copy of the original, with just a few changes:
    //position: "",                      //commented out so this module does not show on screen
    maximumNumberOfDays: 45,
    
    1. change the default MM calendar module to:
    maximumNumberOfDays: 10,
    
    1. change the names of all the calendars in the original default MM calendar module, so they are unique and distinct from the second default MM calendar module.

    2. used the CalendarSet in the MMM-CalendarExt3 module to select the calendars in the hidden default MM calendar module

    posted in Troubleshooting
    C
    cyclonej
    Jan 6, 2025, 1:57 AM
  • Calendar number of events to display

    I am new to Raspberry Pi and MM and CSS and Github, but learning fast. I am running MM on a Raspberry Pi 5. I am using the default MM calendar module to show upcoming stuff in upper left and MMM-CalendarExt3 module to show previous, current, and next 2 weeks.

    I want the default MM calendar module to show only a few days (maybe up to a week of upcoming events) and I want the MMM-CalendarExt3 to show everything in the visible date range (previous week, current week, and next 2 weeks). The purpose being to see near-future detail in a quick view at upper left while also being able to see further future at bottom.

    The problem I am encountering is it seems that if I limit the default MM calendar module to a desirable number of events (using maximumEntries=10), then the MMM-CalendarExt3 module also will hide events. In my tinkering, I have not found a way to limit the MM calendar module while not limiting the MMM-CalendarExt3 module. I tested using the ExcludedEvents filterBy, which worked for the default MM calendar module, but unfortunately also suppressed events in the MMM-CalendarExt3 module. I also tested with the fadePoint in the default MM calendar module, but this does not seem to do much (the fading is too gradual for a long list of events).

    Does anyone have any pointers for how I might limit the number of events shown in the default MM calendar module while not limiting the number of events shown in the MMM-CalendarExt3 module?

    config.js excerpts:

                   {
                            module: "calendar",
                            header: "upcoming",
                            position: "top_left",
                            config: {
                                    maximumEntries: 50,              //don't want to show this many, but if I reduce, then events start disappearing from MMM-CalendarExt3
                                    fade: true,
                                    fadePoint: 0,                                     //does not help with hiding
                                    wrapEvents: true,
                                    wrapTitleLines: true,
                                    broadcastEvents: true,
                                    broadcastPastEvents: true,
                                    titleReplace: {
                                            'Christmas Day':'Christmas',
                                    },
                                    maximumNumberOfDays: 45,
                                    excludedEvents: [
                                            "Hanukkah",
                                            "Kwanzaa",
                                            //{filterBy: "", until: "7 days"},          //testing
                                    ],
                                    hideDuplicates: true,
                                    coloredSymbol: true,
                                    coloredText: true,
                                    fetchInterval: 60 * 60 * 1000,
                                    ...
                                    },
                                    {
                                                            module: "MMM-CalendarExt3",
                                                            position: "bottom_bar",
                                                            header: "Family Calendar",
                                                            config: {
                                                                    mode: "week",
                                                                    locale: 'en-US',
                                                                    maxEventLines: 10,
                                                                    firstDayOfWeek: 0,
                                                                    calendarSet: [],
                                                                    skipDuplicated: true,
                                                                    useWeather: true,
                                                                    displayWeatherTemp: true,
                                                                    weekIndex: -1,
                                                                    weeksInView: 4,
                                                                    useMarquee: true,
                                      ...
                                       },
    

    faa452fc-b5d4-46b4-9240-b73879886dbb-image.png

    posted in Troubleshooting
    C
    cyclonej
    Jan 4, 2025, 2:38 AM
  • RE: scaling gone wonky

    @sdetweil

    I thought I would post the final fix for the screen resolution.

    Through many Google searches, I found some commands that would theoretically would force the OS to use 1920x1080 resolution. (https://forums.linuxmint.com/viewtopic.php?t=274540)
    However, I was receiving errors on execution of the cvt command.

    cvt 1920 1080
    

    More Google searches revealed that I had to install cvt.

    sudo apt-get install xcvt
    

    next, I was getting errors on the last xrandr command (setting the current output mode).

    xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2276  1080 1083 1088 1120 -hsync +vsync
    xrandr --addmode WAYLAND1 1920x1080_60.00
    xrandr --output WAYLAND1 --mode "1920x1080_60.00"
    

    More Google searches indicated WAYLAND output is enabled when VNC is enabled for remote connections. More searches lead me to the raspi-config, where I found the display was set to ‘WAYLAND’. I had to change the display setting to X11. Now the commands could all succeed.

    xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2276  1080 1083 1088 1120 -hsync +vsync
    xrandr --addmode HDMI-1 1920x1080_60.00
    xrandr --output HDMI-1 --mode "1920x1080_60.00"
    

    However, the resolution setting would not persist through a reboot. I started exploring how to set these xrandr commands to execute at startup. Google searches lead me to try modifying config files, which failed due to access denied. Then I remembered that MM uses pm2 to auto start when OS starts. So I created a .sh file to execute the xrandr commands and followed the same steps in MM (https://docs.magicmirror.builders/configuration/autostart.html#using-pm2) , replacing file names as needed, to launch my Set_Resolution.sh at startup.

    Viola!

    My raspberry pi 5 now boots up and sets screen to 1920x1080 right away!

    It took a great deal of searching and learning how Raspberry Pi works. In the end, I got there.
    dd9b81f6-c87f-4dd0-b13e-5e8135efce22-image.png

    posted in Troubleshooting
    C
    cyclonej
    Jan 4, 2025, 2:06 AM
  • RE: scaling gone wonky

    @cyclonej said in scaling gone wonky:

    @cyclonej said in scaling gone wonky:

    @sdetweil

    I am marking this as solved. I think when I first booted up the Raspberry Pi, the resolution was 1920x1080. I am not sure what is preventing from going to that resolution now. That is where I will focus my troubleshooting.

    Thanks all for the assistance.

    I spent another couple hours trying things in the preferences, display settings, even tried to modify the /boot/config to no avail. I then reseated the HDMI cable and the OS started allowing resolutions up to 1920x1080. MM looks great again!

    Thanks again everyone for your help.

    After I got everything working nicely, I disconnected everything to move to the permanent installation location. Hung everything on kitchen wall, then reconnected everything and powered on… screen resolution stuck back on 1024x768.

    30191b4c-f159-4e8e-acbb-5bd0969cf829-image.png

    posted in Troubleshooting
    C
    cyclonej
    Dec 27, 2024, 2:49 AM
  • RE: scaling gone wonky

    @cyclonej said in scaling gone wonky:

    @sdetweil

    I am marking this as solved. I think when I first booted up the Raspberry Pi, the resolution was 1920x1080. I am not sure what is preventing from going to that resolution now. That is where I will focus my troubleshooting.

    Thanks all for the assistance.

    I spent another couple hours trying things in the preferences, display settings, even tried to modify the /boot/config to no avail. I then reseated the HDMI cable and the OS started allowing resolutions up to 1920x1080. MM looks great again!

    Thanks again everyone for your help.

    posted in Troubleshooting
    C
    cyclonej
    Dec 25, 2024, 10:04 PM
  • RE: scaling gone wonky

    @sdetweil

    I am marking this as solved. I think when I first booted up the Raspberry Pi, the resolution was 1920x1080. I am not sure what is preventing from going to that resolution now. That is where I will focus my troubleshooting.

    Thanks all for the assistance.

    posted in Troubleshooting
    C
    cyclonej
    Dec 25, 2024, 7:04 PM
  • RE: scaling gone wonky

    @MMRIZE

    Currently 1024x768, maximum allowed.

    9e5151d4-0d02-494f-82e4-3631a6c80803-image.png

    posted in Troubleshooting
    C
    cyclonej
    Dec 25, 2024, 6:08 PM
  • RE: scaling gone wonky

    @sdetweil

    I went ahead and installed Ext3. This looks just as bad as Ext2. The calendar is occupying the whole screen. I think something has gone arwy in MM. Normal websites look fine. Its just in the MM page that the calendar is too big and i guess the date/time and weather information seem larger/wider than they should be.

    In case I forgot to mention earlier, I have my display in portrait orientation

    .

    f9e55f89-b6c1-46e9-a8ac-69abbcb2779e-image.png

    new config.js

    /* Config Sample
     *
     * For more information on how you can configure this file
     * see https://docs.magicmirror.builders/configuration/introduction.html
     * and https://docs.magicmirror.builders/modules/configuration.html
     *
     * You can use environment variables using a `config.js.template` file instead of `config.js`
     * which will be converted to `config.js` while starting. For more information
     * see https://docs.magicmirror.builders/configuration/introduction.html#enviromnent-variables
     */
    let config = {
    	address: "localhost",	// Address to listen on, can be:
    							// - "localhost", "127.0.0.1", "::1" to listen on loopback interface
    							// - another specific IPv4/6 to listen on a specific interface
    							// - "0.0.0.0", "::" to listen on any interface
    							// Default, when address config is left out or empty, is "localhost"
    	port: 8080,
    	basePath: "/",	// The URL path where MagicMirror² is hosted. If you are using a Reverse proxy
    									// you must set the sub path here. basePath must end with a /
    	ipWhitelist: ["127.0.0.1", "::ffff:127.0.0.1", "::1"],	// Set [] to allow all IP addresses
    									// or add a specific IPv4 of 192.168.1.5 :
    									// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.1.5"],
    									// or IPv4 range of 192.168.3.0 --> 192.168.3.15 use CIDR format :
    									// ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::ffff:192.168.3.0/28"],
    
    	useHttps: false,			// Support HTTPS or not, default "false" will use HTTP
    	httpsPrivateKey: "",	// HTTPS private key path, only require when useHttps is true
    	httpsCertificate: "",	// HTTPS Certificate path, only require when useHttps is true
    
    	language: "en",
    	locale: "en-US",
    	logLevel: ["INFO", "LOG", "WARN", "ERROR"], // Add "DEBUG" for even more logging
    	timeFormat: 12,
    	units: "imperial",
    
    	modules: [
    		{
    			module: "alert",
    		},
    		{
    			module: "updatenotification",
    			position: "top_bar"
    		},
    		{
    			module: "clock",
    			position: "top_left"
    		},
    		{
    			module: "weather",
    			position: "top_right",
    			config: {
    				weatherProvider: "openmeteo",
    				type: "current",
    				lat: REDACTED
    				lon: REDACTED
    			}
    		},
    		{
    			module: "calendar",
    			header: "REDACTED",
    			position: "top_left",
    			config: {
    				calendars: [
    					{
    						name: "REDACTED",
    						symbol: "calendar-xmark",
    						coloredBackground: true,
    						bgColor: "white",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    					{
    						name: "REDACTED",
    						symbol: "cake-candles",
    						coloredBackground: true,
    						bgColor: "white",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    					{
    						name: "REDACTED",
    						symbol: "google",
    						coloredBackground: true,
    						bgColor: "white",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    					{
    						name: "REDACTED",
    						symbol: "truck",
    						coloredBackground: true,
    						bgColor: "green",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    					{
    						name: "REDACTED",
    						symbol: "basketball",
    						coloredBackground: true,
    						bgColor: "orange",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    					{
    						name: "REDACTED",
    						symbol: "school-circle-xmark",
    						coloredBackground: true,
    						bgColor: "red",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    					{
    						name: "REDACTED",
    						symbol: "school",
    						coloredBackground: true,
    						bgColor: "blue",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    					{
    						name: "REDACTED",
    						symbol: "school-circle-exclamation",
    						coloredBackground: true,
    						bgColor: "white",
    						fetchInterval: 7 * 24 * 60 * 60 * 1000,
    						url: "REDACTED",
    					},
    				]
    			}
    		},
    		{
    			module: "MMM-CalendarExt3",
    			position: "bottom_bar",
    			title: "",
    			config: {
    				mode: "month",
    				instanceId: "basicCalendar",
    				locale: 'en-US',
    				maxEventLines: 7,
    				firstDayOfWeek: 1,
    				calendarSet: [],
    			}
    		}
    	]
    };
    
    /*************** DO NOT EDIT THE LINE BELOW ***************/
    if (typeof module !== "undefined") { module.exports = config; }
    
    
    posted in Troubleshooting
    C
    cyclonej
    Dec 25, 2024, 4:55 AM
  • RE: scaling gone wonky

    @sdetweil said in scaling gone wonky:

    they use the default calendar module to get data, which then broadcasts it to other modules just comment out the default cal position to have it not show on the screen.

    I used MMM-CalendarExt2 because I liked the look in the sample better than the one in Ext3. This meant less work for me to do to get the look I was after.

    I do not have the default calendar module included in my config.js (I assume you mean the MM-supplied calendar module).

    posted in Troubleshooting
    C
    cyclonej
    Dec 25, 2024, 3:16 AM
Enjoying MagicMirror? Please consider a donation!
MagicMirror created by Michael Teeuw.
Forum managed by Sam, technical setup by Karsten.
This forum is using NodeBB as its core | Contributors
Contact | Privacy Policy