@dwleo Oh boy, you’re really new to this :-)
How can i describe?
https://www.raspberrypi.org/documentation/remote-access/ssh/
You’ve got a lot to learn young padawan
@dwleo Oh boy, you’re really new to this :-)
How can i describe?
https://www.raspberrypi.org/documentation/remote-access/ssh/
You’ve got a lot to learn young padawan
@dwleo can you ssh into the mirror?
If you access the mirror directly type in
pm2 stop mm
to stop the mirror.
Lokk for a response that the mm fork has been stopped. If you got an error, look for the process name using
pm2 status
However I think it’s best to ssh into the mirror.
As soon as you have control :-) go into the MagicMirror folder and type
npm run config:check
Look if there is an error message, go into the config.js and try to solve it.
If you don’t know what to do, post your config withoit sensitive information
@andurii I agree with you on both points and I’m working on it :-)
Basically the implementation of showEnd is quite messed up.
I’m trying to use my freshly gained JS beginner skills on this :-)
Have send a PR for the fulldayevent fix and I expect this to be included in the next release.
Guys, going through the thread, I see that a lot of good ideas were implemented in forks but not sent as PRs. I think it would be a good idea to have some of these included into the original. dmcinnes/MMM-forecast-io, since this is the one referenced in the original MagicMirror.
@dmcinnes what do you think?
Do you want this rep to be bloated up or do you want it to be kept mostly as it is and leave major changes to forks?
I would expect at least to have some of @morozgrafix very good ideas implemented as optional (sunset, precipitation probability).
Also @rak 's ideas look very very promising but I admit might be a bit much as changes for the master.
@mykle1 said in MMM-rainfc wouldn't start/show:
@cirdan said in MMM-rainfc wouldn't start/show:
Hanging out with my friend Ossë
Excellent! Got my hands on a Silmaril. Olórin is none to happy about that. I’m going to use it to woo Lúthien Tinúviel.
Nerds.
@cirdan I’ve read them all but that one I had to look up.
Short story very OFF-TOPIC!
Was in Zeeland in holidays this summer. On the way back to Germany did a random stop in Geldrop to find an Albert Heijn and pack up with all the good stuff you nieghbours have there.
I couldn’t belive my eyes…

I was in AH Laan van Tolkien btw…
@cyberphox
I find it most comfortable to look this up in the browser. Open the mirror in Chrome, then press F12. Move the mouse over the calendar and right click and “discover” or however the last point is called. Activate the "Styles tab in the developers console (see picture)
Then you can find the referring styles in the window, see the sources of the styles, and see that some styles are crossed out because they are overruled by other ones.

Now go for it, Sherlock!!
I agree, the glass looks great. Real silver mirror touch. What brand is it?
The rest of course looks great too :-)
So I guess I have found a “solution”.
This is in fact a systemic problem.
A full day event is given by the ical source as starting at 0:00 on a day and ending at 0:00, but one day ahead. The duration is exactly a multiple of 24h.
There is a one-liner as workaround, but I’d invite everyone to find a more gentle solution.
The workaround: subtract one second from the endDate time:
Include this line into calendar.js just at the beginning of the if clause in line 262:
event.endDate -= 1000;
So it looks like this:
if (event.fullDayEvent) {
event.endDate -= 1000;
if (event.today) {
This should solve the issue. It worked for me at least.
If you’re referring to the 0:00 that is shown in the picture, that MAY be the end time.
Can you please go into the config.js and set
timeFormat: 'absolute'
It should then show the swedish version of:
“22.11. 9:00”
I think with a relative timeFormat, the end dates (that seem to be shown here) don’t really make much sense and are misleading here.
You can switch them off using
showEnd: false
However, this needs to be addressed somehow in further releases.
Please note there is a more recent module also using the buienradar API called MMM-rain-forecast.
Apart from that can you please post the config entry and confirm that you have cloned the module to the MagicMirror/modules folder and not to the MagicMirror folder itself? :-)
@dawookie1979 @Status-Board
can you please explain again how (the command) and from which folder you have installed pm2?
And what is your system running?
Looks good!
Since I’m currently working on the calendar module: What does your module do with multi-day events?
@cjmaverick You can easily use the server just using any browser on any tablet or pc and going to YOURMIRRORIP:8080.
But please be aware that you need to include the device to the IP whitelist in the config.
@branchi It’s going too far off topic but a hint:
If your Pi is not booting, look at what the LED’s do. They may be blinking at the beginning. That resembles a code which you can look up with google.
However, If it’s not too much work a completely new install is advisable.
@sean as far as I understand this will create a local branch and that’s it.
he will need to track pull the branch 2.0.0 doesn’t he? So for example
git branch -f 2.0.0 origin/2.0.0 //create branch 2.0.0 and track origin/2.0.0
git checkout 2.0.0
git pull
@andurii
Yeah that’s what is still missing and why i said this is still only some type of workaround.
However, the if-clause will be needed in the end because for a full one-day event you do not want to be shown an endDate. As soon as the full-day-event is longer than one day, you may want it again.
E.g.
Mario’s birthday Nov 16th
(and NOT Nov 16th - Nov 16th)
Luigi’s Holiday Nov 16th - Nov 23rd
What you’re pointing at is the root cause and it lies somewhere else. I’m sure it can be solved. Give me one weekend ;-)
@mykle1 So what were the respective versions of node? Maybe the older ubuntu version uses an older node version?
I had the feeling that it was purely note-related but I may be wrong.
@andurii OK I found a way to properly deal with one-day events. Will send a PR to the develop branch.
If you want to include it already:
Exchange the if-clause starting at line 292 with this.
if(this.config.showEnd){
if(event.endDate - event.startDate > oneDay) {
timeWrapper.innerHTML += "-" ;
timeWrapper.innerHTML += this.capFirst(moment(event.endDate , "x").format(this.config.fullDayEventDateFormat));
}
}
BEWARE OF CHANGING THE MODULE FILES THEMSELVES.
Only do it if you know what you’re doing.
(You’re not breaking anything irreversibly however)
This only shows the end date for a more-than-one-day-full-day-event.
However, still a workaround. Still searching into the problem itself