ERROR: Bad Request with plannedTasks true about mmm-microsofttodo HOT 6 CLOSED

I improved error logging in last commit 9e9ba1a. Could you please update to the latest version with git pull and post the related logs from Magic Mirror? Thanks!

from mmm-microsofttodo.

@jjonnela you have to have at least one valid value in the includedLists value. That array takes any regex, and the default is setup to match all lists. If you want all lists, just remove that value in your config and let the default take over.

from mmm-microsofttodo.

@thobach Here's the error

[24.01.2022 16:40.38.357] [ERROR] Response {
size: 0,
timeout: 0,
[Symbol(Body internals)]: {
body: Gunzip {
_writeState: [Uint32Array],
_readableState: [ReadableState],
_events: [Object: null prototype],
_eventsCount: 5,
_maxListeners: undefined,
_writableState: [WritableState],
allowHalfOpen: true,
bytesWritten: 0,
_handle: [Zlib],
_outBuffer: <Buffer 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 55 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... 16334 more bytes>,
_outOffset: 0,
_chunkSize: 16384,
_defaultFlushFlag: 2,
_finishFlushFlag: 2,
_defaultFullFlushFlag: 3,
_info: undefined,
_maxOutputLength: 1073741823,
_level: -1,
_strategy: 0,
[Symbol(kCapture)]: false,
[Symbol(kCallback)]: null,
[Symbol(kError)]: null
},
disturbed: false,
error: null
},
[Symbol(Response internals)]: {
url: 'https://graph.microsoft.com/v1.0/me/todo/lists/xxxxx/tasks?$top=200&$filter=status%20ne%20%27completed%27%20and%20duedatetime%2Fdatetime%20lt%20%272022-02-21T16%3A40%3A37%2B02%3A00%27%20and%20duedatetime%2Fdatetime%20ne%20null&$orderby=duedatetime/datetime',
status: 400,
statusText: 'Bad Request',
headers: Headers { [Symbol(map)]: [Object: null prototype] },
counter: 0
}
}
[24.01.2022 16:40.38.364] [ERROR] [MMM-MicrosoftToDo]: Error: checkFetchStatus failed with status 'Bad Request' {"size":0,"t

from mmm-microsofttodo.

@jjonnela I assume your timezone is not in the Greenwich Mean Time / Western European Time zone. I had the same issue being based in UTC+1 and addressed the issue by adjusting the filter query to remove the timezone. Please check out the latest version.
@spyder007 FYI

from mmm-microsofttodo.

Thanks @thobach, I have been thinking about how to add a few tests to this to check for these things. For sidetracked with my day job! Thanks for the assist.

from mmm-microsofttodo.

@thobach Thanks for the update, I will check it out later and hopefully get it working.

from mmm-microsofttodo.