@Cyric - You’re welcome.
I did the same update myself this morning, so know what needed to be changed…
Don’t forget to mark the issue as solved.
@Cyric - You’re welcome.
I did the same update myself this morning, so know what needed to be changed…
Don’t forget to mark the issue as solved.
@Cyric The new module uses apiKey rather than appid in the config. Try changing that in each entry.
@sdetweil Good to know.
git status got me out of it, as I think things got out of sync rather than really needing merging or proper tracking (if subsequent research on what package.json actually means and does).
But useful to know how to actually see the differences for future reference. I really need to get more skilled-up on GitHub, but it always defeats me as I’m only an occasional hobby programmer for personal usage rather than for sharing/collaboration.
@sdetweil Yes, I’m not quite sure what the weatherforecast.js change was, but that’s blown away now. As you say, the new module is fine with a little tweaking via custom.css.
It was the package.json file that screwed things up, and that I know I have never touched and have no idea what it was and why it got out of sync.
Anyway I learned a bit of stuff about GitHub and stashing, so that’s a bonus and we’re up and running again fine (after swapping out the depreciated weather modules too).
@Canguingo You need to put in your key (which used to be in the appid entry in your old config) into the apiKey entry there. What is listed is just a default dummy one in the example you quote.
I’m actually just doing the update myself at the moment, and now tweaking the newer module to emulate the appearance of the old two.
Can you post your old config.js entries for the modules (removing key strings and anything else you want to keep private) and then we can try to get your new version transposed across. Just finished mine, now minor tweaks ongoing.
OK did some searching and some reading of GitHub documentation and have resolved it. Used “Git Status” and the command options given therein.
Now just have to up the update for the default modules due to the depreciations
I think I need a little GitHub help.
Just updated from 2.18 to 2.19 using the updater script, and accepted the stashing of a couple of files (including package.json iirc) and then selected unstashing at the end.
But after reboot I just go to the Pi desktop rather than the mirror, and the logs have this in them:
npm ERR! code EJSONPARSE
npm ERR! path /home/pi/MagicMirror/package.json
npm ERR! Merge conflict detected in your package.json.
npm ERR!
npm ERR! Please resolve the package.json conflict and retry.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2022-04-02T09_27_46_355Z-debug-0.log
npm ERR! code EJSONPARSE
npm ERR! path /home/pi/MagicMirror/package.json
npm ERR! Merge conflict detected in your package.json.
npm ERR!
npm ERR! Please resolve the package.json conflict and retry.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2022-04-02T09_27_48_900Z-debug-0.log
npm ERR! code EJSONPARSE
npm ERR! path /home/pi/MagicMirror/package.json
npm ERR! Merge conflict detected in your package.json.
npm ERR!
npm ERR! Please resolve the package.json conflict and retry.
How do I resolve that conflict? If I try to move package.json away and git pull I get
error: Pulling is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm <file>'
hint: as appropriate to mark resolution and make a commit.
fatal: Exiting because of an unresolved conflict.
My GitHub-fu is not strong enough to know how to resolve this one. Can someone assist in what commands I need?
The git stash is
fonts/package-lock.json | 26 -
modules/default/weatherforecast/weatherforecast.js | 2 +-
package-lock.json | 15293 ------------------------------------------------------------------------------------------------
package.json | 1 +
vendor/package-lock.json | 154 -
5 files changed, 2 insertions(+), 15474 deletions(-)
@ortizimo said in Just the Clock at night:
@darrenhill one last question… do you know why once they turn off except those ignored, the following day it doesn’t restart as normal? All are off except those ignored and have to restart the pi for it to work…thnx.
On mine they come back fine, so that’s a little weird. All I can think of is that there’s something off in your set-up somewhere, but as you can see from the snippets I posted before the plugin gives times for both turn-off and turn-on, so not sure there…
@dcginmd I’ve just tried to resurrect this module in my mirror, and hit exactly the same problem.
One thing I do note is that to get things working on the website, you need to use https:// rather than http:// . If you try unsecure http to the website you get an unauthorised token error.
Unfortunately adding https in the MM config still just gives the “loading…” message forever still, but I think we might be hitting such an issue here?
The GH repo hasn’t been touched in 3 years though, so I think this is a dead module unfortunately…