Read the statement by Michael Teeuw here.
MMM-GoogleKeep config.js
-
@svenpisa yes, the instruction leave out an important step
after step 2
then change to the module foldercd MMM-GoogleKeepTHEN
npm install
you can do that step now, in the module folder
-
@sdetweil i did it…
I went directly to ~/MagicMirror/modules/MMM-GoogleKeep $ and started npm install but then only got error messagesnpm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: MMM-GoogleKeep@1.0.0
npm ERR! Found: stylelint@15.11.0
npm ERR! node_modules/stylelint
npm ERR! peer stylelint@“15.x” from grunt-stylelint@0.19.0
npm ERR! node_modules/grunt-stylelint
npm ERR! dev grunt-stylelint@“latest” from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev stylelint-config-standard@“latest” from the root project
npm ERR!
npm ERR! Conflicting peer dependency: stylelint@16.2.0
npm ERR! node_modules/stylelint
npm ERR! peer stylelint@“^16.1.0” from stylelint-config-standard@36.0.0
npm ERR! node_modules/stylelint-config-standard
npm ERR! dev stylelint-config-standard@“latest” from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/sven/.npm/_logs/2024-01-25T19_14_43_524Z-eresolve-report.txtnpm ERR! A complete log of this run can be found in: /home/sven/.npm/_logs/2024-01-25T19_14_43_524Z-debug-0.log
-
@svenpisa gr… the developer junk
edit package.json and change
"devDependencies"to
"devDependencies1"then do the
npm install
again -
@sdetweil You’re great… Thank you very much
Partly good news.
It could now be installed and entered in config.js. MM also starts cleanly and is also displayed cleanly, but the KEEP module is unfortunately not displayed on the MM.
Now I need to get the list displayed somehow.
I have tried it with the APP password 16 digits as well as 4x4 digits and also with the Google password but unfortunately it is not displayed.
Any more ideas? -
@svenpisa sorry, don’t know the internals of the module
-
@sdetweil What? I thought you were the God Father of Magic Mirror Modules!!! ;-)
No problem, maybe there is someone who has used this module before and it works for him to tell me what to do… I would be very happy anyway!!!
-
I have tried to get the module to run, but have also failed. It seems to me that there is a problem with gkeepapi. A simple query with gkeepapi already fails.
There seems to be a workaround with docker (see https://github.com/kiwiz/gkeepapi/issues/81), but I didn’t tested that. In the issue discussion the maintainer of gkeepapi mentioned waiting for a new release of gpsoauth. Then MMM-GoogleKeep might work again without any tinkering 🙂
-
@KristjanESPERANTO Thank you very much. Do I understand correctly that I may only have to wait until the module works or do I have to make additional settings? Can I see the status somewhere when it should work again?
-
@svenpisa well I can fix most install problems.
-
@svenpisa said:
Do I understand correctly that I may only have to wait until the module works or do I have to make additional settings?
I haven’t looked at the code in detail, but that could be possible, yes. Of course, it may still be the case that something needs to be adjusted in gkeepapi and/or MMM-GoogleKeep.
The best thing would probably be to look at alternatives.
Can I see the status somewhere when it should work again?
If a gpsoauth version newer than 1.0.4 appears here, we can try again. You can also follow this discussion: https://github.com/kiwiz/gkeepapi/issues/81.
-
Hi @KristjanESPERANTO I have seen that something has happened in the issue. But I didn’t understand what was changed and what was adjusted. May I come back to your help? If you have time, could you take a look at the issue on GitHub?
Thank you very much and best regards -
I still can’t see a new version of gpsoauth or gkeepapi. In the issue they seem only talking about a workaround.
-
@KristjanESPERANTO ah ok, then I took it the wrong way. Sorry and thanks
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login