Wunderlist - your todos on the mirror

[carteblanche]

@SexyTrogg you have a typo on “accessToken:” in the config file.

[SexyTrogg]

@carteblanche bah sorry that was a typo in the post not in my config :S

[carteblanche]

@SexyTrogg damn…ok i assume you double checked your access token and client ID in the config match up perfectly with what you received from Wunderlist? Other than that I can’t think of any other reason why it wouldn’t show the lists.

[Sunburned]

@pugsly Thanks for the suggestion. I gave repulling the app a shot and am still having the same issue, after a certain amount of time wunderlist decides to stop updating. It does seem to be lasting longer so i changed my cron job to restart the pi once a day and increased the wunderlist update interval to 120. We shall see how that works.

[pugsly]

@Sunburned Yeah i spoke too soon, the app is still not updating again after a few hours. I really don’t want to make a cron job and restart the mm. I think im going to give this one a try:

https://github.com/cbrooker/MMM-Todoist

[Sunburned]

Knock on wood… the wunderlist has been updating without issue. I have the pi and MM applicaiton restarting once a day at 2am and the interval is set at 120.

[Headcrush]

Hey guys,

i have the following problem:

• header will be shown
• list is empty
• The code in line 42 always returns “undefined”

it looks to be the same problem Kukielka58 had.
Did someone find out where the problem could be?

if i use:
curl -H “X-Access-Token: TOKEN” -H “X-Client-ID: ID” https://a.wunderlist.com/api/v1/lists

the console returns: “{“unauthorized”: true}” but i have no idea why.

this are my configs:

i hope someone can help me.

With best regards.
Headcrush

[Sunburned]

@Headcrush
I would try increasing your interval. 1 may be too short. Try 100, or at least 60

[Headcrush]

I got a hint via private message.
The problem i had was something with the website of wunderlist.
I deleted all cookies and the cache.
Following i need to generate a new access token.
Now its working.

Special thanks to SexyTrogg.

[cowboysdude]

Been playing with this for 2 hours… same issues… blank lists… no real answers. NO errors in the console, throwin in the towel on this one… too much work for something simple. NEVER thought I’d say this but going to stick with Google Calendar… it just works.

[pugsly]

I kept having this same problem where it would stop pulling the To-Do’s so I switched to ToDoist and thought the problem was solver but low and behold it started doing it with ToDoist as well.

Although I do like the interface of ToDoist much better so I think i am going to stick with this one my only resort is to set a cron job to restart the pi nightly before it goes to sleep and blanks out the monitor.

anyone know how I can get PM2 to automatically restart at midnight rather then reboot the entire pi?

[Sunburned]

@pugsly

This is the page that I used to set up my cron job. I set it up to reset at 2am and start the mirror at 2:03.

[pugsly]

@Sunburned
I don’t want to reboot, I just want to restart pm2 and I have added it to my crontab but it doesn’t seem to work.

i see in the logs that cron has executed the command but the node process never restarts.

[Mar]

Im managed to get this up and running, great job!!

The one thing I’m trying to do is create two of these modules one for to-do and one for another list to keep them separate as we cant tell what is on each list. but putting two modules throws an error? Has anyone managed to get two lists up (from the same wunderlist account) in two separate modules or lists (not as one big list on the mirror).

[onetwankyfive]

@Mar mine worked fine

 {
        module: 'MMM-Todoist',
        position: 'top_left',  // This can be any of the regions. Best results in left or right regions.
        header: 'Alexa TO-DO List', // This is optional
        config: { // See 'Configuration options' for more information.
            accessToken: 'accesstokenaXXXXCXCC687',
            maximumEntries: 60,
            interval: 60,
            lists: [ 12345 ],
            fade: false
      }
    },


 {
        module: 'MMM-Todoist',
        position: 'top_left',  // This can be any of the regions. Best results in left or right regions.
        header: 'Alexa Shopping List', // This is optional
        config: { // See 'Configuration options' for more information.
            accessToken: 'XXXX',
            maximumEntries: 60,
            interval: 60,
            lists: [ 1234 ],
            fade: false
      }
    },

[Hein-Jan]

I also have 2 Wunderlist/lists running one underneath the other.
I also implemented this by having the module twice in the config.

[Mar]

@onetwankyfive Thanks, i couldnt figure out if it was not supported or something I did wrong. Appreciate you posting how you did it. Looks like it was my error. Thanks for the help! Glad that this works.

[Mar]

I’ve had two wunderlist lists running under each other for just under month now without issues, but now it seems like the lists are not updating at all?

I requested a new accesstoken and it worked again for a couple refreshes but ive come back and checked on it later in the day and the lists werent updating. I’ve restarted the MM and the lists dont seem to be loading at all.

It sort of seems like its rejecting the token, or the token is being locked out after some time. Has anyone else had this issue before?

edit: Also there are no errors at startup via pm2 logs.

[bminer1]

I have been running with 2 lists since the beginning of Jan. No issues with loading or the lists not updating. This may be an isolated incident. My wife and i are on the lists and either of us can add or delete. When we make a change, it changes on the mirror. Here is my config:

{
			"module": "MMM-Wunderlist",
			"position": "top_right",
			"header": "To Do",
			"config": {
				"accessToken": "Your Token Here",
				"clientID": "Your clientID here",
				"maximumEntries": 5,
				"order": "normal",
				"lists": [
					"To Do"
				],
				"interval": 60,
				"fade": false,
				"fadePoint": 0.25
			}
		},
		{
			"module": "MMM-Wunderlist",
			"position": "top_right",
			"header": "Groceries",
			"config": {
				"accessToken": "Your Token Here",
				"clientID": "Your clientID here",
				"maximumEntries": 15,
				"order": "normal",
				"lists": [
					"Groceries"
				],
				"interval": 60,
				"fade": false,
				"fadePoint": 0.25
			}
		},

[Hein-Jan]

@Mar

I had similar problems. A search on the forum revealed that a daily reboot acts as a work-around. I am using the MMM-Remote-Control in combination with the MMM-ModuleScheduler for the nightly reboots.
It works like a dream ever since.