Posts made by DarrenHill

@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(-)

@snake147 - That is superb - very nice work :)

@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…

Look in this thread for the custom css change:

https://forum.magicmirror.builders/topic/10582/default-clock-size/6

.clock .time {
 font-size: 100px;
}

.clock .date {
 font-size: 30px;
}

It goes in custom.css, which is in the css sub-folder of your main MagicMirror folder (~/MagicMirror/css). Just set the fonts to whatever you like.

@ortizimo You’re welcome :)

In your config.js , you should have something like:

	{
		module: "clock",
		position: "top_left",	// This can be any of the regions.
		config: {
			// The config property is optional.
			// See 'Configuration options' for more information.
		}
	}

If you change the “top_left” to “top_center” or “top_bar” then it should centralise it.

You can see the full configuration options at the link below:
https://docs.magicmirror.builders/modules/clock.html

For the size you can change the analogSize parameter for the analog face. I can’t see where to do it for the digital one, but it can probably be done via a custom css setting.

I’m not a great expert with css though, so someone else can maybe help there?

Also just came across a clash between GmailFeed and both MMM-News and MMM-NewsAPI.

Seems my GmailFeed was a little out of date as a git pull updated stuff there and now they are playing nicely together. Must be something quite recent though as I’m sure I did a full mirror update not so long ago…?

@mumblebaj OK went into MMM-GmailFeed and updated it with git pull. Looks like it has been having some issues with at least one other module from its thread here.

Anyway updated to the latest version and restored it’s config and now both are happily playing together.

Thanks for all the help in getting this sorted out - my mirror is now back fully up and running with MMM-News and MMM-GmailFeed playing nicely together again!