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

    Posts

    Recent Best Controversial
    • RE: new update/upgrade script, ready for testing

      @sdetweil said in new update/upgrade script, ready for testing:

      bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/uninstall_node.sh)”

      pi@MagicMirror2:~/MagicMirror $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/uninstall_node.sh)"
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      The following packages were automatically installed and are no longer required:
        libc-ares2 libjs-highlight.js
      Use 'sudo apt autoremove' to remove them.
      The following packages will be REMOVED:
        nodejs*
      0 upgraded, 0 newly installed, 1 to remove and 20 not upgraded.
      After this operation, 183 MB disk space will be freed.
      Do you want to continue? [Y/n] Y
      (Reading database ... 112341 files and directories currently installed.)
      Removing nodejs (20.5.1-deb-1nodesource1) ...
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/which/bin' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/text-table' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/tar/lib' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/semver/bin' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/rimraf' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/retry' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/read' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/read-package-json' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/once' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/npmlog' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/npm-user-validate' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/npm-install-checks' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/nopt' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/mkdirp/bin' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/minimatch' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/lru-cache' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/init-package-json' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/ini' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/inherits' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/inflight' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/graceful-fs' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/glob' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/columnify' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/cmd-shim' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/chownr' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/archy' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/node_modules/abbrev' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/man/man7' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/man/man5' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/man/man1' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/lib/utils/completion' not empty so not removed
      dpkg: warning: while removing nodejs, directory '/usr/lib/node_modules/npm/bin' not empty so not removed
      Processing triggers for man-db (2.9.4-2) ...
      pi@MagicMirror2:~/MagicMirror $ bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/node20_install.sh)"
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      Package 'nodejs' is not installed, so not removed
      The following packages were automatically installed and are no longer required:
        libc-ares2 libjs-highlight.js
      Use 'sudo apt autoremove' to remove them.
      0 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
      rm: cannot remove '/etc/apt/sources.list.d/nodesource.list': No such file or directory
      Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
      Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
      Reading package lists... Done
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      ca-certificates is already the newest version (20210119).
      curl is already the newest version (7.74.0-1.3+deb11u7).
      gnupg is already the newest version (2.2.27-2+deb11u2).
      The following packages were automatically installed and are no longer required:
        libc-ares2 libjs-highlight.js
      Use 'sudo apt autoremove' to remove them.
      0 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
      deb [arch=arm64 signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main
      Get:1 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
      Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease          
      Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
      Get:4 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages [3,264 B]
      Fetched 15.4 kB in 1s (12.8 kB/s)
      Reading package lists... Done
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      The following additional packages will be installed:
        libnode72 nodejs-doc
      Suggested packages:
        npm
      The following NEW packages will be installed:
        libnode72 nodejs nodejs-doc
      0 upgraded, 3 newly installed, 0 to remove and 20 not upgraded.
      Need to get 0 B/9,956 kB of archives.
      After this operation, 43.3 MB of additional disk space will be used.
      Selecting previously unselected package libnode72:armhf.
      (Reading database ... 106718 files and directories currently installed.)
      Preparing to unpack .../libnode72_12.22.12~dfsg-1~deb11u4_armhf.deb ...
      Unpacking libnode72:armhf (12.22.12~dfsg-1~deb11u4) ...
      Selecting previously unselected package nodejs.
      Preparing to unpack .../nodejs_12.22.12~dfsg-1~deb11u4_armhf.deb ...
      Unpacking nodejs (12.22.12~dfsg-1~deb11u4) ...
      Selecting previously unselected package nodejs-doc.
      Preparing to unpack .../nodejs-doc_12.22.12~dfsg-1~deb11u4_all.deb ...
      Unpacking nodejs-doc (12.22.12~dfsg-1~deb11u4) ...
      Setting up libnode72:armhf (12.22.12~dfsg-1~deb11u4) ...
      Setting up nodejs-doc (12.22.12~dfsg-1~deb11u4) ...
      Setting up nodejs (12.22.12~dfsg-1~deb11u4) ...
      Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ...
      Processing triggers for man-db (2.9.4-2) ...
      pi@MagicMirror2:~/MagicMirror $ node -v
      
      v12.22.12
      pi@MagicMirror2:~/MagicMirror $ 
      

      Why is it installing 12 .22.12???

      posted in General Discussion
      G
      gonzonia
    • RE: Buttons only work if I access via python first

      @MMRIZE No. I still need to run my little test script to get the buttons to work. It’s not a huge deal, I just wonder why that’s the case.

      posted in Troubleshooting
      G
      gonzonia
    • RE: new update/upgrade script, ready for testing

      @sdetweil I found the this thread and I tired running with “force” but I’m getting the same issue when it tries to update npm.

      pi@MagicMirror2:~/MagicMirror $ uname -a
      Linux MagicMirror2 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
      
      pi@MagicMirror2:~/MagicMirror $ lsb_release -a
      No LSB modules are available.
      Distributor ID:	Raspbian
      Description:	Raspbian GNU/Linux 11 (bullseye)
      Release:	11
      Codename:	bullseye
      
      posted in General Discussion
      G
      gonzonia
    • RE: new update/upgrade script, ready for testing

      I rebooted, and for some reason, MM didn’t restart right away, so I ran the script . It got further but then has an issue upgrading npm

      posted in General Discussion
      G
      gonzonia
    • RE: new update/upgrade script, ready for testing

      Running the upgrade script to install v2.25.0 and I get the following result. The last time I hit a roadblock I screwed things up enough that I did a fresh install. What are the proper steps to correct this?

       bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      The following packages were automatically installed and are no longer required:
        libc-ares2 libjs-highlight.js libnode72 nodejs-doc
      Use 'sudo apt autoremove' to remove them.
      The following packages will be REMOVED:
        nodejs*
      0 upgraded, 0 newly installed, 1 to remove and 20 not upgraded.
      After this operation, 919 kB disk space will be freed.
      (Reading database ... 106969 files and directories currently installed.)
      Removing nodejs (12.22.12~dfsg-1~deb11u4) ...
      Processing triggers for man-db (2.9.4-2) ...
      Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
      Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
      Reading package lists... Done
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      ca-certificates is already the newest version (20210119).
      curl is already the newest version (7.74.0-1.3+deb11u7).
      gnupg is already the newest version (2.2.27-2+deb11u2).
      The following packages were automatically installed and are no longer required:
        libc-ares2 libjs-highlight.js libnode72 nodejs-doc
      Use 'sudo apt autoremove' to remove them.
      0 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
      deb [arch=arm64  signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main
      Get:1 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
      Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease                                                 
      Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
      Get:4 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages [3,264 B]
      Fetched 15.4 kB in 1s (15.7 kB/s)
      Reading package lists... Done
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      Suggested packages:
        npm
      The following NEW packages will be installed:
        nodejs
      0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded.
      Need to get 0 B/148 kB of archives.
      After this operation, 919 kB of additional disk space will be used.
      Selecting previously unselected package nodejs.
      (Reading database ... 106907 files and directories currently installed.)
      Preparing to unpack .../nodejs_12.22.12~dfsg-1~deb11u4_armhf.deb ...
      Unpacking nodejs (12.22.12~dfsg-1~deb11u4) ...
      Setting up nodejs (12.22.12~dfsg-1~deb11u4) ...
      update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
      Processing triggers for man-db (2.9.4-2) ...
      doing test run = false
      update log will be in /home/pi/MagicMirror/installers/upgrade.log
      Check current Node installation ...
      Node currently installed. Checking version number.
      Minimum Node version: v20.8.0
      Installed Node version: v12.22.12
      Node should be upgraded.
      A Node process is currently running. Can't upgrade.
      Please quit all Node processes and restart the update.
      running process(s) are
      pi 934 932 0 Sep14 ? 00:00:00 node ./node_modules/.bin/electron js/electron.js
      
      
      posted in General Discussion
      G
      gonzonia
    • RE: Buttons only work if I access via python first

      Oh, I’m realized I’m not actually using https://github.com/sdetweil/MMM-Buttons to fix the install issues

      posted in Troubleshooting
      G
      gonzonia
    • RE: Buttons only work if I access via python first

      @MMRIZE Sorry for the delay I missed your response.

      I’m using https://github.com/Jopyth/MMM-Buttons but happy to switch if there’s something better.

      I’m using it to switch scenes in MMM-Scenes by sending “SCENES_NEXT” or “SCENES_PREV”

      posted in Troubleshooting
      G
      gonzonia
    • RE: MMM-CalendarExt3Agenda

      I have two instances of MMM-CalendarExt3Agenda showing with different calendar sets.

      For one set it shows data for 4 days, with all days populated.

      For the other one, it shows 4 days but the last day isn’t populated. If I increase the endDayIndex by 1 it will add a 5th day and day 4 will be populated but the 5th day will not, so I know the data is there.

      Any ideas what would cause this?
      Working instance 1:

      {
      			module: "MMM-CalendarExt3Agenda",
      			position: "top_right",
      			classes: "SceneFamily",
      			header: "Upcoming Family Calendar",
      			config: {
      				instanceId: "FamilyAgenda",
      				locale: 'en-US',
      				firstDayOfWeek: 1,
      				startDayIndex: 0,
      				endDayIndex: 3,
      				showMiniMonthCalendar: false, 
      				useSymbol: true,
      				calendarSet: ['Dad', 'Mom', 'Kid1', 'Kid2', 'Work1', 'Work22, 'Home'],
      			}
      		}
      

      Missing Data Instance 2

      		{
      			module: "MMM-CalendarExt3Agenda",
      			position: "top_left",
      			classes: "SceneFamily SceneKids",
      			header: "Chores",
      			config: {
      				instanceId: "Chores",
      				locale: 'en-US',
      				firstDayOfWeek: 1,
      				startDayIndex: 0,
      				endDayIndex: 3,
      				showMiniMonthCalendar: false, 
      				useSymbol: true,
      				calendarSet: ['Dad Chores', 'Kid Chores', 'Mom Chores'],
      			}
      		},
      
      posted in Utilities
      G
      gonzonia
    • Buttons only work if I access via python first

      I’ve had this problem for a while and I’m not sure how to fix it.
      I’m using MMM-Buttons to switch between scenes from MMM-Scenes and it’s working. However, it only works if I first use a little python test program I have to test the buttons. Why? I don’t even have to actually press a button, just run the python and then exit. After that, the buttons work.

      I thought I posted this before but can’t find it. I apologize if this is a duplicate.

      Python:

      import RPi.GPIO as GPIO
      import time
      
      GPIO.setmode(GPIO.BCM)
      
      GPIO.setup(25, GPIO.IN, pull_up_down=GPIO.PUD_UP)
      GPIO.setup(24, GPIO.IN, pull_up_down=GPIO.PUD_UP)
      
      
      while True:
          input_state25 = GPIO.input(25)
          input_state24 = GPIO.input(24)
          if input_state25 == False:
              print('Button Pressed 25')
              time.sleep(0.2)
          if input_state24 == False:
              print('Button Pressed 24')
              time.sleep(0.2)
      
      posted in Troubleshooting
      G
      gonzonia
    • RE: MMM-CalendarExt3

      @MMRIZE Thank you! That’s just what I wanted!

      posted in Utilities
      G
      gonzonia
    • 1
    • 2
    • 5
    • 6
    • 7
    • 8
    • 9
    • 13
    • 14
    • 7 / 14