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

    Posts

    Recent Best Controversial
    • MMM-KeyBindings install error

      I’m new to MagicMirror and am having difficulty installing the KeyBindings Module. I’ve been searching the previous posts on the subject, but nothing seems to help. Additionally, I’m new to npm, so I’m having trouble interpreting the error message it spit out. I think the below is telling me there is a dependency issue (ERR! Code 1), and ultimately the error resides with (I think): node:internal/process/task_queues:82:21. Unfortunately, my attempt at researching the error is not turning up anything.

      name@raspberrypi:~/MagicMirror/modules/MMM-KeyBindings $ npm install
      npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
      npm WARN deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
      npm WARN deprecated electron-rebuild@3.2.9: Please use @electron/rebuild moving forward.  There is no API change, just a package name change
      npm ERR! code 1
      npm ERR! path /home/jlward73/MagicMirror/modules/MMM-KeyBindings/node_modules/lzma-native
      npm ERR! command failed
      npm ERR! command sh -c node-gyp-build
      npm ERR! gyp info it worked if it ends with ok
      npm ERR! gyp info using node-gyp@8.4.1
      npm ERR! gyp info using node@20.11.0 | linux | arm64
      npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"
      npm ERR! gyp http GET https://nodejs.org/download/release/v20.11.0/node-v20.11.0-headers.tar.gz
      npm ERR! gyp WARN install got an error, rolling back install
      npm ERR! gyp ERR! configure error 
      npm ERR! gyp ERR! stack FetchError: request to https://nodejs.org/download/release/v20.11.0/node-v20.11.0-headers.tar.gz failed, reason: 
      npm ERR! gyp ERR! stack     at ClientRequest.<anonymous> (/home/jlward73/MagicMirror/modules/MMM-KeyBindings/node_modules/minipass-fetch/lib/index.js:110:14)
      npm ERR! gyp ERR! stack     at ClientRequest.emit (node:events:518:28)
      npm ERR! gyp ERR! stack     at TLSSocket.socketErrorListener (node:_http_client:495:9)
      npm ERR! gyp ERR! stack     at TLSSocket.emit (node:events:530:35)
      npm ERR! gyp ERR! stack     at emitErrorNT (node:internal/streams/destroy:169:8)
      npm ERR! gyp ERR! stack     at emitErrorCloseNT (node:internal/streams/destroy:128:3)
      npm ERR! gyp ERR! stack     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
      npm ERR! gyp ERR! System Linux 6.1.0-rpi7-rpi-v8
      npm ERR! gyp ERR! command "/usr/bin/node" "/home/jlward73/MagicMirror/modules/MMM-KeyBindings/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
      npm ERR! gyp ERR! cwd /home/jlward73/MagicMirror/modules/MMM-KeyBindings/node_modules/lzma-native
      npm ERR! gyp ERR! node -v v20.11.0
      npm ERR! gyp ERR! node-gyp -v v8.4.1
      npm ERR! gyp ERR! not ok
      

      In addition to getting KeyBindings working, I do want to get better at understanding/troubleshooting issues that come up with npm, so any guidance in either of those areas would be greatly appreciated.

      posted in Troubleshooting
      J
      jlward73
    • MMM-CalendarExt3 color formatting

      I’m new to Magic Mirror, but am running into an issue getting MMM-CalendarExt3 to format colors properly. I have been able to pass multiple calendars and the events are displaying the correct information, but the color formatting for each calendar is not working, they are all just showing white text or white background with black text. I know some color is working as the weekends were showing up red and “dodgerblue” before I commented those out (Go Padres!). I’m running module version 1.8.0 and have the following calendar snippet in my config.js file:

      {
      module: 'calendar',
      header: 'Upcoming Events',
      position: 'top_left',
      config: {
           coloredText: true,
           coloredSymbol: true,
           customEvents: [{keyword: "Birthday", symbol: "birthday-cake", color: "#FFFF00"}],
           calendars: [
                {
                fetchInterval: 1000*60*60*24*7, //Holiday Calendar
                name: "holidays",
                color: "#385723", 
                symbol: 'umbrella-beach',
                broadcastPastEvents: true, 
                url: 'https://calendar.google.com/calendar/.../basic.ics',
                },
                {
                fetchInterval: 1000*60*5,  //Family Calendar
                name: "Family",
                color: "#7030A0",
                symbol: 'calendar-check',
                broadcastPastEvents: true, 
                url: "https://calendar.google.com/.../basic.ics",
                },
           ]
      } //close config
      }, //close module
      

      The keyword for birthdays is working within the default calendar, but that does not transfer over to the CalendarExt3 Module.
      Additionally, in looking at the .css file, I see the following snippet:

      .CX3 .event.fullday,
      .CX3 .event.multiday {
        background-color: var(--calendarColor);
        mix-blend-mode: difference;
        border-radius: 4px;
        color: var(--oppositeColor);
      }
      
      
      .CX3 .event.singleday .headline:not(.useSymbol)::before,
      .CX3 .event.singleday .headline.useSymbol .symbol.noSymbol::before {
        content: "⬤";
        color: var(--calendarColor);
        display: inline-block;
        padding-right: 2px;
        font-size: 75%;
      }
      

      It appears the CalendarExt3 module should be pulling the color from the basic calendar module in the config file, but I’m not seeing it.
      I do see in the .CX3 .event {} block above this that uses color:--defaultcolor. Is this overriding something? Any guidance would be appreciated.

      posted in Troubleshooting
      J
      jlward73
    • 1
    • 2
    • 3
    • 3 / 3