• 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

Scheduled Pinned Locked Moved Troubleshooting
99 Posts 27 Posters 96.6k Views 26 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.
  • B Offline
    barnosch
    last edited by Nov 1, 2017, 5:06 PM

    @paviro
    i have the problem currently that
    MMM-FRITZ-Box-Callmonitor is not working anymore.
    So the overlay when someone calls is not showing anymore.

    The current call works without problems.
    Nothing was changed. No idea what happened.
    Fritzbox settings wasn’t changed nor a firmware upgrade was done

    What do i need to check?

    1 Reply Last reply Reply Quote 0
    • 2 Offline
      2fingers @rf0620
      last edited by Nov 5, 2017, 7:44 PM

      @rf0620 i have tried to install the module and i had unnbekannte fehler (unknown issue) error . i followd all the steps but i have another error now:

      pi@raspberrypi:~ $ sudo pip install fritzconnection --upgrade
      Requirement already up-to-date: fritzconnection in /usr/local/lib/python2.7/dist-packages
      Collecting requests>=2.2.0 (from fritzconnection)
      Downloading requests-2.18.4-py2.py3-none-any.whl (88kB)
      100% |████████████████████████████████| 92kB 763kB/s
      Collecting lxml>=3.2.5 (from fritzconnection)
      Using cached lxml-4.1.1.tar.gz
      Collecting urllib3=1.21.1 (from requests>=2.2.0->fritzconnection)
      Downloading urllib3-1.22-py2.py3-none-any.whl (132kB)
      100% |████████████████████████████████| 133kB 880kB/s
      Collecting idna=2.5 (from requests>=2.2.0->fritzconnection)
      Downloading idna-2.6-py2.py3-none-any.whl (56kB)
      100% |████████████████████████████████| 61kB 1.5MB/s
      Collecting chardet=3.0.2 (from requests>=2.2.0->fritzconnection)
      Downloading chardet-3.0.4-py2.py3-none-any.whl (133kB)
      100% |████████████████████████████████| 143kB 983kB/s
      Collecting certifi>=2017.4.17 (from requests>=2.2.0->fritzconnection)
      Downloading certifi-2017.11.5-py2.py3-none-any.whl (330kB)
      100% |████████████████████████████████| 337kB 629kB/s
      Building wheels for collected packages: lxml
      Running setup.py bdist_wheel for lxml … /^error
      Failed building wheel for lxml
      Running setup.py clean for lxml
      Failed to build lxml
      Installing collected packages: urllib3, idna, chardet, certifi, requests, lxml
      Found existing installation: urllib3 1.19.1
      Not uninstalling urllib3 at /usr/lib/python2.7/dist-packages, outside environment /usr
      Found existing installation: idna 2.2
      Not uninstalling idna at /usr/lib/python2.7/dist-packages, outside environment /usr
      Found existing installation: chardet 2.3.0
      Not uninstalling chardet at /usr/lib/python2.7/dist-packages, outside environment /usr
      Found existing installation: requests 2.12.4
      Not uninstalling requests at /usr/lib/python2.7/dist-packages, outside environment /usr
      Found existing installation: lxml 3.7.1
      Not uninstalling lxml at /usr/lib/python2.7/dist-packages, outside environment /usr
      Running setup.py install for lxml … |^canceled
      Can’t rollback lxml, nothing uninstalled.
      Operation cancelled by user

      1 Reply Last reply Reply Quote 0
      • C Offline
        Cyberdyne
        last edited by Oct 8, 2018, 9:06 AM

        Please read this befor you update your Fritzbox with a new FritzOS!

        I upgraded my Fritzbox 6490 to the new FritzOS 7 and the callmonitor stoped working. I tried to but I could not reactivate the callmonitor. Nothing seemed to work and I thought I did something wrong. I contacted AVM to help and got a realy bad answer: They told me that AVM has removed the callmonitor functionality. I asked them how I could downgrade the OS to get the functionality back but they told me that there is no downgrade option. They also told me that they are going to remove the callmonitor functionality from all of their routers OSs.
        Warning to everyone: If you want to keep on using the callmonitor do not install FritzOS updates without checking if the new OS still supports the callmonitor. I would aks AVM befor updating.

        I am not sure if it helps but maybe everyone should write them an email and ask to keep or bring back this feature?!

        With this plugin I now can only see incomming calls (only the number) but no list with history of calls anymore. :o(

        1 Reply Last reply Reply Quote 0
        • S Offline
          Sandy2503
          last edited by Sandy2503 Oct 8, 2018, 2:27 PM Oct 8, 2018, 2:26 PM

          @Cyberdyne - Hmmmm thats strange. I am using a 7590 with the actual AVM OS7.01 from 20th September (and early Beta Versions) and the Call Monitor and Current Call works (with the 7590 and 7490) very well …

          Sandy2503

          1 Reply Last reply Reply Quote 0
          • C Offline
            Cyberdyne
            last edited by Oct 14, 2018, 2:56 PM

            I can only say what AVM has told me. Callmonitor is removed from the 6490 with the OS 7.0 and they also told me that they will remove it from all other boxes as well. They did not tell me in which version on which box. Hete are some emals:

            "Sie schildern, dass Sie den Callmonitor nicht mehr aktivieren können und möchten wissen, wieso dies der Fall ist. Ich bedauere diesen Umstand und nehme mich gerne der Sache an.

            Der Callmonitor wird mittlerweile nicht mehr von den FRITZ!Boxen unterstützt. Wenn Sie mit mitteilen, was genau Sie vorhaben, kann ich Ihnen ggf. Alternativen aufzeigen. "

            "Sie möchten wissen, bei welchen FRITZ!OS der Callmonitor noch unterstützt wird und wie Sie Ihre FRITZ!Box 6490 entsprechend downgraden können. Gerne beantworte ich Ihnen Ihre Frage.

            Ab welchen FRITZ!OS der Collmonitor nicht mehr unterstützt wurde, kann ich Ihnen nicht sagen, da dieser aufgrund der unterschiedlichen FRITZ!OS der verschiedenen FRITZ!Box-Modellen sukzessiv geschehen ist.

            Ein Downgrade von dem FRITZ!OS bei FRITZ!Box Cable ist leider nicht möglich."

            Just be carefull and better ask befor you make an other update if you want to keep on using the callmonitor! It does not work here anymore and no way back. :(

            1 Reply Last reply Reply Quote 0
            • D Offline
              darklight89
              last edited by Dec 30, 2018, 3:30 PM

              Hi guys,
              how can I hide the call history, since the Fritz-Boxes Callmonitor seems to be deactivated in OS 7 and I want to keep at least the alert pop-up.

              1 Reply Last reply Reply Quote 0
              • R Offline
                randpop
                last edited by Apr 25, 2019, 9:59 AM

                Re: MMM-FRITZ-Box-Callmonitor

                Hi all,

                i cannot get the module up and running.

                I’ve tried all the above solutions and nothing really worked.

                We got 2 FritzBoxes at work. One is our router (7590) and the other one (6490) is used as a cable modem and for the telephone connections.

                Callerid and TR-064 access are activated on the 6490 and it is running with OS 6.50. The user i created has access to the FritzBox and has all the necessary rights.
                I’ve tried a CallerMonitor App on macOS and it worked fine.

                This is my config:

                
                   {
                                        module: 'MMM-FRITZ-Box-Callmonitor',
                                        position: 'bottom_left',      
                                        header: "Anrufe", 
                                        config: {
                                        password: "PASSWORD",
                                        username: "USERNAME",
                                        fritzIP: "130.180.xx.xx",
                                        reloadContactsInterval: 1,
                                        vCard: false 
                                       }
                
                

                When i test the connection with:

                python fritz_access.py -p PASSWORD -u USER -i 130.180.xx.xx
                

                i get this:

                Traceback (most recent call last):
                  File "fritz_access.py", line 77, in 
                    main(args)
                  File "fritz_access.py", line 63, in main
                    handle.download_phone_book()
                  File "fritz_access.py", line 22, in download_phone_book
                    result = self.fc.call_action("X_AVM-DE_OnTel", "GetPhonebookList")
                  File "/usr/local/lib/python2.7/dist-packages/fritzconnection/fritzconnection.py", line 406, in call_action
                    return action.execute(**kwargs)
                  File "/usr/local/lib/python2.7/dist-packages/fritzconnection/fritzconnection.py", line 130, in execute
                    result = self.parse_response(response.content)
                  File "/usr/local/lib/python2.7/dist-packages/fritzconnection/fritzconnection.py", line 142, in parse_response
                    root = etree.fromstring(response)
                  File "src/lxml/etree.pyx", line 3222, in lxml.etree.fromstring
                  File "src/lxml/parser.pxi", line 1877, in lxml.etree._parseMemoryDocument
                  File "src/lxml/parser.pxi", line 1765, in lxml.etree._parseDoc
                  File "src/lxml/parser.pxi", line 1127, in lxml.etree._BaseParser._parseDoc
                  File "src/lxml/parser.pxi", line 601, in lxml.etree._ParserContext._handleParseResultDoc
                  File "src/lxml/parser.pxi", line 711, in lxml.etree._handleParseResult
                  File "src/lxml/parser.pxi", line 640, in lxml.etree._raiseParseError
                  File "", line 1
                lxml.etree.XMLSyntaxError: Opening and ending tag mismatch: HR line 1 and BODY, line 1, column 180
                

                All phonebook entries are in the formats 004902211234567 or 02211234567.

                The callermonitor seems to work as it shows incoming numbers but the recent calls and phonebook function are broken.

                Anyone has any thoughts about that? Any kind of solution

                Best,

                R 1 Reply Last reply Aug 8, 2019, 7:18 AM Reply Quote 0
                • R Offline
                  rabbit83ka @randpop
                  last edited by Aug 8, 2019, 7:18 AM

                  Hi @randpop,

                  I’m running this plugin together with the fix by wunderbear and a Unitymedia-Fritzbox 6490 with FritzOS 7.02

                  fritz_access.py does also work an gives a reasonable output.

                  Regards

                  1 Reply Last reply Reply Quote 1
                  • L Offline
                    Laurids
                    last edited by Aug 29, 2019, 8:35 AM

                    Hi all,
                    this is my first post, so please be patient with me ;)
                    I´m trying to use MMM-FRITZ-Box-Callmonitor, but I have some problems, although I followed nearly every hint in this discussion.

                    • When someone is calling, I can see his number but not his name on the screen.
                    • The latest calls only were shown when I don´t config password and username. Why is that?
                    • when I test the connection with:
                    python fritz_access.py -p PASSWORD -u USER -i xxx.xxxx.xx.xx
                    

                    I retrieve all the data from my Fritzbox, so the connection should not be the problem.

                    At least I tried the recommended fix of wunderbear, but after a reboot I only get a black screen (with the cursor top-left) after starting the MagicMirror. What is the reason and how can I solve these problems? I don´t want to start all other again :weary_face:

                    I hope, that someone can help me to fix my problems.

                    Thanks and regards
                    Laurids

                    B 1 Reply Last reply Jun 23, 2020, 11:21 AM Reply Quote 0
                    • B Offline
                      Baschti @Laurids
                      last edited by Jun 23, 2020, 11:21 AM

                      @Laurids Did you solve the Problem? Same here!

                      1 Reply Last reply Reply Quote 0
                      • 1
                      • 2
                      • 5
                      • 6
                      • 7
                      • 8
                      • 9
                      • 10
                      • 7 / 10
                      • First post
                        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