• 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
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

MMM-FRITZ-Box-Callmonitor-py3 unknown_error

Scheduled Pinned Locked Moved Solved Troubleshooting
15 Posts 4 Posters 2.4k Views 4 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    rkorell @wuermchen
    last edited by Jan 30, 2025, 2:46 PM

    @wuermchen
    Hi.
    I guess it SHOULD work - at least it works for me at current github status (approx. 2-3 old - not sure what you have archived).
    At my own initial setup I got the same error message and after some researches it was caused by refused authentication on the fritzbox side.

    So I would start at this point initially - not at module side.
    My first attempt was login without password (as possible for console) - this doesn’t work.
    I’ve created a separate user on AVM side with full access to phonebook and so on and this worked from scratch.
    I see that you have an explicite user/pw as well - so I would double check if this user exists on AVM side and do have the right access privileges.

    For being sure I would recommend to delete all parameters from configuration you do not really need and experiment with the base parameters.
    E.g. you have set the Port number - at default - I would delete this one.

    I’m not sure if you are aware but you can find the documentation of the module in your module folder as well - you do not need the - closed - github entry.
    “README.md” is the file.

    Good luck!
    Ralf

    1 Reply Last reply Reply Quote 0
    • K Offline
      KristjanESPERANTO Module Developer @sdetweil
      last edited by Jan 30, 2025, 3:50 PM

      @sdetweil said in MMM-FRITZ-Box-Callmonitor-py3 unknown_error:

      i do not know how the module works but i suspect this
      https://forum.magicmirror.builders/post/123380

      Where do you see the connection? The maintainer of MMM-FRITZ-Box-Callmonitor-py3 is drtorchwood.

      S 1 Reply Last reply Jan 30, 2025, 5:45 PM Reply Quote 0
      • S Offline
        sdetweil @KristjanESPERANTO
        last edited by Jan 30, 2025, 5:45 PM

        @KristjanESPERANTO bad post, didn’t check source, he had one too

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        1 Reply Last reply Reply Quote 1
        • W Offline
          wuermchen
          last edited by Jan 31, 2025, 6:07 PM

          • I tried a new config with default values, without success
          • Reinstalling and turning off the other modules, without success
          {
          		module: 'MMM-FRITZ-Box-Callmonitor-py3',
          		position: 'top_right',
          		header: "Recent calls",
          		config: {
          			password: "pass",
          			username: "user",
          			fritzIP: "192.168.188.1",
          			showContactsStatus: true,
          			vCard: false
          		}
          	},
          

          npm start has errors

          pi@raspberrypi:~/MagicMirror $ npm start
          
          > magicmirror@2.30.0 start
          > npm run start:x11
          
          
          > magicmirror@2.30.0 start:x11
          > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
          
          [2025-01-31 18:47:25.363] [LOG]   Starting MagicMirror: v2.30.0
          [2025-01-31 18:47:25.394] [LOG]   Loading config ...
          [2025-01-31 18:47:25.398] [LOG]   config template file not exists, no envsubst
          [2025-01-31 18:47:26.001] [INFO]  Checking config file /home/pi/MagicMirror/config/config.js ...
          [2025-01-31 18:47:26.140] [INFO]  Your configuration file doesn't contain syntax errors :)
          [2025-01-31 18:47:26.142] [INFO]  Checking modules structure configuration ...
          [2025-01-31 18:47:26.269] [INFO]  Your modules structure configuration doesn't contain errors :)
          [2025-01-31 18:47:26.272] [LOG]   Loading module helpers ...
          [2025-01-31 18:47:26.275] [LOG]   No helper found for module: alert.
          [2025-01-31 18:47:26.283] [LOG]   Initializing new module helper ...
          [2025-01-31 18:47:26.284] [LOG]   Module helper loaded: updatenotification
          [2025-01-31 18:47:26.285] [LOG]   No helper found for module: clock.
          [2025-01-31 18:47:26.286] [LOG]   No helper found for module: compliments.
          [2025-01-31 18:47:26.461] [LOG]   Initializing new module helper ...
          [2025-01-31 18:47:26.462] [LOG]   Module helper loaded: MMM-FRITZ-Box-Callmonitor-py3
          [2025-01-31 18:47:26.463] [LOG]   All module helpers loaded.
          [2025-01-31 18:47:26.473] [LOG]   Starting server on port 8080 ...
          [2025-01-31 18:47:27.320] [LOG]   Server started ...
          [2025-01-31 18:47:27.322] [LOG]   Connecting socket for: updatenotification
          [2025-01-31 18:47:27.324] [LOG]   Starting module helper: updatenotification
          [2025-01-31 18:47:27.325] [LOG]   Connecting socket for: MMM-FRITZ-Box-Callmonitor-py3
          [2025-01-31 18:47:27.327] [LOG]   Starting module: MMM-FRITZ-Box-Callmonitor-py3
          [2025-01-31 18:47:27.329] [LOG]   Sockets connected & modules started ...
          [2025-01-31 18:47:28.262] [LOG]   Launching application.
          [2025-01-31 18:47:29.866] [INFO]  System information:
          ### SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.1; virtual: false
          ### OS:       platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.6.62+rpt-rpi-v8
          ### VERSIONS: electron: 34.0.2; used node: 20.18.1; installed node: 20.18.1; npm: 10.9.2; pm2: 5.4.3
          ### OTHER:    timeZone: Europe/Berlin; ELECTRON_ENABLE_GPU: undefined
          [96922:0131/184730.026384:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.026830:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.027196:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.027321:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.027499:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.027625:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.027798:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.027902:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.028061:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.028171:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.028341:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.028445:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.028602:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.028704:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.030069:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.030275:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.030478:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.030618:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.030807:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.030950:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.031137:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.031248:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.031471:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.031751:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.031946:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.032053:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.032219:ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [96922:0131/184730.032326:ERROR:gbm_wrapper.cc(262)] Failed to export buffer to dma_buf: Datei oder Verzeichnis nicht gefunden (2)
          [2025-01-31 18:47:31.626] [LOG]   Received config for MMM-FRITZ-Box-Callmonitor-py3
          [2025-01-31 18:47:31.631] [LOG]   MMM-FRITZ-Box-Callmonitor-py3 is waiting for incoming calls.
          [2025-01-31 18:47:31.680] [INFO]  updatenotification: Updater Class Loaded!
          [2025-01-31 18:47:31.682] [INFO]  updatenotification: Checking PM2 using...
          [2025-01-31 18:47:31.684] [INFO]  updatenotification: [PM2] You are not using pm2
          [2025-01-31 18:47:31.689] [INFO]  Checking git for module: MMM-FRITZ-Box-Callmonitor-py3
          [2025-01-31 18:47:31.730] [INFO]  Checking git for module: MagicMirror
          :ERROR:gbm_wrapper.cc(79)] Failed to get fd for plane.: Datei oder Verzeichnis nicht gefunden (2)
          [2025-01-31 18:48:11.502] [INFO]  updatenotification: Updater Class Loaded!
          [2025-01-31 18:48:11.503] [INFO]  updatenotification: Checking PM2 using...
          [2025-01-31 18:48:11.503] [INFO]  updatenotification: [PM2] You are not using pm2
          
          
          R 1 Reply Last reply Feb 1, 2025, 7:37 PM Reply Quote 0
          • R Offline
            rkorell @wuermchen
            last edited by rkorell Feb 1, 2025, 8:25 PM Feb 1, 2025, 7:37 PM

            @wuermchen
            The log info from MMM-FRITZ-Box-Callmonitor seems to be O.K. …
            Regards,
            Ralf

            1 Reply Last reply Reply Quote 0
            • W Offline
              wuermchen
              last edited by Feb 6, 2025, 5:01 PM

              I reinstalled Fritzcallmonitor. The error still exists.
              During installation there were changes compared to the template:

              python-dev = Doch die folgenden Pakete ersetzen es: python-dev-is-python3
              
              sudo pip install fritzconnection  error: externally-managed-environment   sudo pipx install fritzconnection
              

              Does anyone have any idea what I’m doing wrong?

              S 1 Reply Last reply Feb 6, 2025, 5:15 PM Reply Quote 0
              • S Offline
                sdetweil @wuermchen
                last edited by Feb 6, 2025, 5:15 PM

                @wuermchen does the pip setup require a virtual environment?
                which you have to enable again before launching MagicMirror

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                1 Reply Last reply Reply Quote 0
                • W Offline
                  wuermchen
                  last edited by Feb 6, 2025, 5:56 PM

                  I installed pipx before and then “sudo pipx install fritzconnection” so I don’t need a virtual environment

                  S 1 Reply Last reply Feb 6, 2025, 6:25 PM Reply Quote 0
                  • S Offline
                    sdetweil @wuermchen
                    last edited by Feb 6, 2025, 6:25 PM

                    @wuermchen yes, but it failed

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    1 Reply Last reply Reply Quote 0
                    • W Offline
                      wuermchen
                      last edited by Feb 7, 2025, 7:29 AM

                      When I try to reinstall fritzconnection I get the following message:

                      'fritzconnection' already seems to be installed. Not modifying existing
                      installation in '/root/.local/pipx/venvs/fritzconnection'. Pass '--force' to
                      force installation.
                      
                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 1 / 2
                      1 / 2
                      • First post
                        7/15
                        Last post
                      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