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-Wunderlist: Invalid namespace Error

    Scheduled Pinned Locked Moved Troubleshooting
    4 Posts 2 Posters 2.4k Views 2 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.
    • H Offline
      huckstopper
      last edited by

      I am unable to get the Wunderlist module to successfully render my list items. I am able to successfully curl the API with my token and client id - my config matches those settings.

      The only error I can see standing out is the "MMM-Wunderlist,‘Invalid namespace’ " error I see in the network traffic back to the socket. I updated node to v7 and socket.io to make sure I was running the latest of each.

      Any help would be appreciated. Thanks.

      1 Reply Last reply Reply Quote 0
      • paviroP Offline
        paviro Admin
        last edited by paviro

        ‘Invalid namespace’ is logged to the console?

        We're all stories in the end. Just make it a good one, eh?

        – The Doctor

        1 Reply Last reply Reply Quote 0
        • H Offline
          huckstopper
          last edited by huckstopper

          Correct. When viewing the socket traffic in the Network tab. I’ve also stepped through the JS on the client side and confirmed nothing is in the array.

          0_1479656148246_upload-4ef3273a-8930-4425-ac99-0d00dfd04ae8

          My config:

          	 {
          	        module: 'MMM-Wunderlist',
          	        position: 'top_left',  // This can be any of the regions. Best results in left or right regions.
          	        header: 'Home', // This is optional
          	        config: { // See 'Configuration options' for more information.
          	            accessToken: 'token',
          	            clientID: 'client_id',
          	            maximumEntries: 60,
          	            interval: 60,
          	            lists: [ "Home" ],
          	            fade: false
          	      }
          	    },
          
          1 Reply Last reply Reply Quote 0
          • H Offline
            huckstopper
            last edited by

            Successful curl:

            0_1479734984391_upload-0649f5be-43e3-4221-9b67-d1f9b3dc2a7b

            However, on the client side when it is checking for ToDos, nothing comes through:
            0_1479735598080_upload-e83f3dd2-ebed-4d40-909e-bb93cca5bf05

            0_1479736036922_upload-2f2887b4-ca87-41b1-ade6-c603636241f5

            Obviously there will be subsequent I/O with the socket but I’m assuming if nothing returns here then any of the other requests will follow suit.

            Is there a specific spot in the server side code I should focus on?

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            • 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