MagicMirror² v2.4.1 is available! For more information about this release, check out this topic.
Please read the release notes carefully since this update requires adjustments to your Raspberry Pi configuration!

Wunderlist won't display entries



  • Re: Wunderlist - Lists not showing up

    As described here, I configured everything like this:

    {
    module: ‘MMM-Wunderlist’,
    position: ‘top_left’, // This can be any of the regions. Best results in left or right regions.
    header: ‘Einkaufsliste’, // This is optional
    config: {
    accessToken: ‘xxxxxxxxxxxxxxxxxxxx’,
    clientID: ‘xxxxxx’,
    lists: [‘inbox’]
    // See ‘Configuration options’ for more information.
    }
    }

    For the test I did within the ./modules/MMM-Wunderlist:
    node fetcher_debug_client.js
    which showed:
    /home/pi/MagicMirror/modules/MMM-Wunderlist/fetcher_debug_client.js:59
    createFetcher(“id”, “Inbox”, 1000, accessToken, clientID);
    ^

    ReferenceError: accessToken is not defined

    is there something I missed? For the API-Key Generator in put in
    API URL: http://localhost:8080
    callback: https://a.wunderlist.com/api/v2/lists

    PS: Is there a possibility to have code formatted? 😉



  • @binderth said in Wunderlist won’t display entries:

    accessToken: ‘xxxxxxxxxxxxxxxxxxxx’,
    clientID: ‘xxxxxx’,
    lists: [‘inbox’]

    Yop,

    you forgot to add your access token, client ID and (maybe) the folder you want.
    you have the answer in the log - ReferenceError: accessToken is not defined
    dont change the API URL and the callback

    in your wondurlist account you can found the key and all



  • @tidus5 said in Wunderlist won’t display entries:

    you forgot to add your access token, client ID and (maybe) the folder you want.

    sorry, I forgot to mention, in the post above, I crossed out my own accessToken and clientID. 😉 That’s what makes me wonder, because I defined my own keys in wundertlist API and put them in the config…?
    As I had difficulties to access my own Folder (which is within a group), I just wanted to access a system-folder provided by Wunderlist.





  • @tidus5 said in Wunderlist won’t display entries:

    maybe that can help you
    same error

    Perhaps I just don’t understand it… 😉
    But: at first, I did create my first keys with the PI’s browser, meaning I did not have any login in this browser yet. But i did created a new pair of keys, after I cleared the cache and stuff:

    https://developer.wunderlist.com/apps/new:

    after that, I get two Keys:

    • CLIENT ID: 20 characters
    • CLIENT SECRET: 60 characters

    Those key I fill in in my config:

    	{
    		module: 'MMM-Wunderlist',
    		position: 'top_left',  // This can be any of the regions. Best results in left or right regions.
    		header: 'Einkaufslisten', // This is optional
    		config: {
    			accessToken: 'CLIENT SECRET',
    			clientID: 'CLIENT ID',
    			lists: ['inbox'],
    			interval: '10',
    			fade: true
    		    // See 'Configuration options' for more information.
    		}
    	},
    

    but: I don’t get any information out of wunderlist. I don’t get an error in the console, but here’s the full console, if that helps:

    pi@MagicMirror:~/MagicMirror $ DISPLAY=:0 npm start

    magicmirror@2.0.0 start /home/pi/MagicMirror
    electron js/electron.js

    Loading config …
    Loading module helpers …
    Initializing new module helper …
    No helper found for module: alert.
    No helper found for module: clock.
    Initializing new module helper …
    Initializing new module helper …
    No helper found for module: compliments.
    No helper found for module: MMM-Globe.
    Initializing new module helper …
    No helper found for module: MMM-Callmonitor-Current-Call.
    No helper found for module: currentweather.
    No helper found for module: weatherforecast.
    Initializing new module helper …
    Initializing new module helper …
    No helper found for module: trainconnections.
    All module helpers loaded.
    Starting server op port 8080 …
    Server started …
    Connecting socket for: MMM-PIR-Sensor
    Staring module helper: MMM-PIR-Sensor
    Connecting socket for: calendar
    Starting node helper for: calendar
    Connecting socket for: MMM-Wunderlist
    Connecting socket for: MMM-FRITZ-Box-Callmonitor
    Starting module: MMM-FRITZ-Box-Callmonitor
    Connecting socket for: MMM-DWD-WarnWeather
    MMM-DWD-WarnWeather helper started…
    Connecting socket for: newsfeed
    Starting module: newsfeed
    Sockets connected & modules started …
    Launching application.
    [2016-12-28 16:23:10] [MMM-PIR] Watching on GPIO #23 …
    Create new calendar fetcher for url: http://calendar.google.com/calendar/ical/xxx%40group.calendar.google.com/private-xxx/basic.ics - Interval: 300000
    Received config for MMM-FRITZ-Box-Callmonitor
    MMM-FRITZ-Box-Callmonitor is waiting for incoming calls.
    Starting access to FRITZ!Box…
    Create new news fetcher for url: http://rss.sueddeutsche.de/rss/Topthemen - Interval: 300000
    Create new calendar fetcher for url: http://calendar.google.com/calendar/ical/xxx/private-xxx/basic.ics - Interval: 300000
    Access to FRITZ!Box finished.
    [2016-12-28 16:23:34] [MMM-PIR] Motion detected
    [2016-12-28 16:23:34] [MMM-PIR] Not turning monitor ON, its already ON
    [2016-12-28 16:23:37] [MMM-PIR] Motion no longer detected
    [2016-12-28 16:23:37] [MMM-PIR] Turning Screen OFF in 120 seconds
    [2016-12-28 16:23:37] [MMM-PIR] Motion detected
    [2016-12-28 16:23:37] [MMM-PIR] Not turning monitor ON, its already ON

    Thanks for help!



  • @binderth said in Wunderlist won’t display entries:

    CLIENT ID: 20 characters
    CLIENT SECRET: 60 characters

    Please be aware, that in the Wunderlist API there’s a CLIENT SECRET, which is exactly as long as the ACCESS TOKEN.
    The ACCESS TOKEN is not shown directly after generating the Keys, there’s a button “CREATE ACCESS TOKEN”, after that, the token is generated on the fly (note: it changes, everytime you press the button!). Then you can put in the token, which then resulted in my lists showing up in the MM as expected! 😉

    So please be aware, there are in fact three keys, only two are needed in config.js.