@sdetweil is this module dead in the water now?
It was the backbone of my entire MM, using Carousel the mirror nicely flipped between the family calendar and the google photos.
is there a work around still using this module or is it a case of finding an alternative? If the latter which is the best module to use for the same end result?
Sorry to hijack but didn’t want to start a whole new thread.
Cheers.
@sdetweil Sorry for the late response, That’s done the job.
If I get the package-lock.json during any other update, will this work to allow the update to continue?
I’m getting this error when running the latest update,
MagicMirror@raspberrypi:~/MagicMirror/modules/MMM-Carousel $ git pull
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace “git config” with “git config --global” to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Updating fb51858…f14e5e9
error: Your local changes to the following files would be overwritten by merge:
package-lock.json
Please commit your changes or stash them before you merge.
Aborting
I’ve tried - git reset package-lock.json
as was recommended with a similar issue with MMM-CalendarEXT3 but this isn’t offering any steps forward.
Any thoughts?
Cheers.
@sdetweil restarted the MM with PM2, still no info being displayed in the CalendarEXT3 module.
edit to add, after letting the mirror settle down, it’s now pulling the data
@sdetweil
getting this now,
MagicMirror@raspberrypi:~/MagicMirror $ git switch _fix_clipping
Already on ‘_fix_clipping’
so assuming I can now restart mm?
@sdetweil
MagicMirror@raspberrypi:~/MagicMirror $ rm package-lock.json
rm: cannot remove ‘package-lock.json’: No such file or directory
guessing I’m not doing this right
@sdetweil do I run that in just the MagicMirror directory or the Calendar EXT3 module directory?
Below was your guidance from another of my topics with issues with this module, will it work?
(#)put package-lock.json back to last git clone state
git reset package-lock.json
(#) update the module
git pull
(#) rerun npm install with new code
npm install
had to put the # in () to stop the font going enormous
@sdetweil I’ve hit this at the 3 command,
MagicMirror@raspberrypi:~/MagicMirror $ git switch _fix_clipping
error: Your local changes to the following files would be overwritten by checkout:
package-lock.json
Please commit your changes or stash them before you switch branches.
Aborting
@sdetweil I hadn’t seen that, I was about to update the module individually then do some digging on here to see if others had had the issue.
do I use the list of commands in the link above, or the ones in this link?
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code
@sdetweil This is useful to know.
Just add, I’ve had the same Issue as the last MM update, Calendar EXT3 is no longer pulling information from the base calendar module.
out of curiosity, what would I do if I needed to retrieve the back up, do I need a GitHub account?
Finally getting round to updating the base MM version.
used @sdetweil bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)”
and it did what it wanted to do.
How do I know that the second line bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply
can be run without issue?
I get this before it runs through all the package.json files for modules I’m using,
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v20.18.1
Installed Node version: v20.8.0
Node should be upgraded.
Node.js upgrade defered, doing test run
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V10.8.2
Installed npm version: V10.1.0
npm should be upgraded.
npm upgrade defered, doing test run …
is it safe at this point to use the code to make the changes?
Cheers,
John.
@sdetweil so just to be clear its,
git checkout package-lock.json
git reset
git pull
npm install
within the calendar ext3 module folder?
@sdetweil used both of those then tried to up date the rest of the module and still get the same issue when running git pull in the module folder, this is what it says;
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace “git config” with “git config --global” to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Updating 3ca76d9…dfe2425
error: Your local changes to the following files would be overwritten by merge:
package-lock.json
Please commit your changes or stash them before you merge.
Aborting
I’ve had the notification that this module needs an update, the guidance says go into the module folder and run “git pull” when I run this I get an error of,
your local changes to the following files would be overwritten by the merge: package-lock.json
please commit them or stash them before you merge.
Aborting.
How do I mitigate for this issue without causing fundamental problems with my MM setup, It’s working perfectly at the moment and I don’t want to a knock down the first domino in chain of potential issues.
Cheers.
> magicmirror@2.29.0 start
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
[2024-10-08 19:41:58.640] [LOG] Starting MagicMirror: v2.29.0
[2024-10-08 19:41:58.693] [LOG] Loading config ...
[2024-10-08 19:41:58.698] [LOG] config template file not exists, no envsubst
[2024-10-08 19:41:59.497] [INFO] Checking config file /home/MagicMirror/MagicMirror/config/config.js ...
[2024-10-08 19:41:59.584] [ERROR] Your configuration file contains syntax errors :(
Line 94 column 5: Parsing error: Unexpected token weatherEndpoint
That parsing error is for the new line added in for weatherEndpoint
@sdetweil I have it exactly as you have it above.
can you share a config for this module as an example?
I can’t even check if this is working with pm2 not launching the MM
@sdetweil so my config was identical to above, so I’ve added you new line “weatherEndpoint…”
I’m using Putty to access the MM and used pm2 to stop the MM.
which it did.
However now, pm2 via Putty is no longer having any effect on the MM.
MM isn’t launching.
run pm2 logs mm and get a parsing error over adding the new line
unexpected token weatherEndpoint your configuration file contains syntax errors.
all I’ve added is weatherEndpoint: “/onecall”, to a final line under the apiKey line above.
any thoughts?
edit to add, pm2 status and logs show that pm2 exists still it’s just not launching. can pm2 be “updated” or should I follow the process for a first install?
for completeness I don’t want it to launch MM on boot I just want to be able to start and stop the MM using pm2.
@sdetweil So I’ve upgraded to my account on OpenWeather (and added payment details.
Generated a new APIkey and added this to the config of the weather module but it is still stuck on loading.
So I’ve run your update, and the weather still doesn’t load.
Seems odd that the API issue would only arise following the update.
Is this likely?