@yawns That’s fixed it, thank you!
Read the statement by Michael Teeuw here.
Posts
-
RE: Updated, but 'MMM-EventHorizon' still shows as being behind.
-
RE: Updated, but 'MMM-EventHorizon' still shows as being behind.
pi@raspberrypi:~/MagicMirror/modules/MMM-EventHorizon $ git pull && npm installUpdating 73d1110..6d5a53a error: Your local changes to the following files would be overwritten by merge: MMM-EventHorizon.js Please, commit your changes or stash them before you can merge. AbortingWhat does that mean?
I think I’ve made any changes to the Event Horizon module. -
Updated, but 'MMM-EventHorizon' still shows as being behind.
‘MMM-EventHorizon’ says my MM is 27 commits behind.
I’ve updated, twice, but still the same 27 commits message remains.
Any idea why, please?Thanks.
-
RE: Simple daily countdown timer
Well this is very odd.
Another MM stop/start seems to have fixed it.Happy days! :)
-
RE: Simple daily countdown timer
@mykle1 Peculiar. I’ve no idea why it’s giving different results for you.
I’ll have a play when I have time, but for now the ‘fudge-fix’ (deducting five hours in config.js) works ok for me.Thank you!
-
RE: Simple daily countdown timer
@mykle1 said in Simple daily countdown timer:
n179
if (this.config.countUp == "yes" && this.config.size == "small"){ // small iframe.src = "http://free.timeanddate.com/countdown/i6f519yg/n136/cf12/cm0/cu4/ct0/cs0/ca0/cr0/ss0/cac0ff/cpc0ff/pc000/tcfff/fs100/szw256/szh108/tat" + this.config.text1 + "/tac0ff/tpt" + this.config.endText1 + "/tpc0ff/mat" + this.config.text2 + "/mac0ff/mpt" + this.config.endText2 + "/mpc0ff/iso" + this.config.date + "T" + this.config.time; } else if (this.config.countUp == "yes" && this.config.size == "medium") { // medium iframe.src = "http://free.timeanddate.com/countdown/i6f519yg/n136/cf12/cm0/cu4/ct0/cs0/ca0/cr0/ss0/cac0ff/cpc0ff/pc000/tcfff/fs100/szw320/szh135/tat" + this.config.text1 + "/tac0ff/tpt" + this.config.endText1 + "/tpc0ff/mat" + this.config.text2 + "/mac0ff/mpt" + this.config.endText2 + "/mpc0ff/iso" + this.config.date + "T" + this.config.time; } else if (this.config.countUp == "yes" && this.config.size == "large") { // large iframe.src = "http://free.timeanddate.com/countdown/i6f519yg/n136/cf12/cm0/cu4/ct0/cs0/ca0/cr0/ss0/cac0ff/cpc0ff/pc000/tcfff/fs100/szw576/szh243/tat" + this.config.text1 + "/tac0ff/tpt" + this.config.endText1 + "/tpc0ff/mat" + this.config.text2 + "/mac0ff/mpt" + this.config.endText2 + "/mpc0ff/iso" + this.config.date + "T" + this.config.time; } if (this.config.countUp != "yes" && this.config.size == "small"){ iframe.src = "http://free.timeanddate.com/countdown/i64zeztz/n136/cf100/cm0/cu4/ct5/cs0/ca0/cr0/ss0/cac33d9ff/cpc000/pct/tcfff/fs100/szw192/szh81/tat" + this.config.text1 + "/tac33d9ff/tpt" + this.config.endText1 + "/tpc33d9ff/mat" + this.config.text2 + "/mac33d9ff/mpt" + this.config.endText2 + "/mpc33d9ff/iso" + this.config.date + "T" + this.config.time + "/bo2/pd2"; } else if (this.config.countUp != "yes" && this.config.size == "medium") { iframe.src = "http://free.timeanddate.com/countdown/i67bgd3d/n136/cf12/cm0/cu4/ct0/cs1/ca0/cr0/ss0/cac0ff/cpc0ff/pct/tcfff/fs100/szw448/szh189/tat" + this.config.text1 + "/tac0ff/tpt" + this.config.endText1 + "/tpc0ff/mat" + this.config.text2 + "/mac0ff/mpt" + this.config.endText2 + "/mpc0ff/iso" + this.config.date + "T" + this.config.time + "/bo2/pd2"; } else if (this.config.countUp != "yes" && this.config.size == "large") { iframe.src = "http://free.timeanddate.com/countdown/i67bgd3d/n136/cf12/cm0/cu4/ct0/cs1/ca0/cr0/ss0/cac0ff/cpc0ff/pct/tcfff/fs100/szw576/szh243/tat" + this.config.text1 + "/tac0ff/tpt" + this.config.endText1 + "/tpc0ff/mat" + this.config.text2 + "/mac0ff/mpt" + this.config.endText2 + "/mpc0ff/iso" + this.config.date + "T" + this.config.time + "/bo2/pd2"; }Changed n179 to n136, as shown.
Stopped and restarted MM.
Did not change time in config.js, and expected results to now be incorrect, but there’s no change.
The module still shows the correct time for my countdown. -
RE: Simple daily countdown timer
OK, got it working now.
Had to fudge the time to make it work for GMT.
How do you change the time zone properly? -
RE: Simple daily countdown timer
@mykle1 I just added this module as it looks good for something I would like to do.
However, nothing happens. MM starts up OK, but the module doesn’t show.{ disabled: false, module: 'MMM-EventHorizon', position: 'bottom_right', config: { size: "large", // small, medium or large countUp: "yes", // Yes or no (when timer ends) date: "2018-12-03", // (YYYY-MM-DD) Date timer will end time: "00:00:01", // (HH:MM:SS) Exact time you want timer to end text1: "Open the damn pool", // 1st line of text during timer. About 18 characters total. text2: "Winter sucked ass", // 2nd line of text during timer. About 18 characters total. endText1: "It's gonna be fun", // 1st line of text when timer ends. About 18 characters total. endText2: "Where's my bikini", // 2nd line of text when timer ends. About 18 characters total. } },GitHub shows -
disabled: f,
Here it shows -disabled: false,Is that an issue?
Thanks.
-
RE: Calendar entries showing end time.
That’s fixed it, thank you.
The “showEnd:” parameter wasn’t listed in my config.js. When was that changed, where’s the documentation?
-
RE: Calendar entries showing end time.
@alvinger said in Calendar entries showing end time.:
It is one of the new features in the latest beta. You can turn it off in config.js.
Excellent!. How, what needs to be changed?
-
RE: Calendar entries showing end time.
Strange, does no-one else have the same issue?
-
Calendar entries showing end time.
Since installing the last 8 commits, calendar is now showing the end time of events.
All-day events, e.g. birthdays, span two days.What’s changed, how do I get it back to normal?
Thanks.
-
RE: MM Crashed twice. Time to abandon MM?
Ok, I’ll try that, thank you.
How do I get it back if I want to?
And can I still VNC to the Pi desktop? -
RE: MM Crashed twice. Time to abandon MM?
How then do I convert my existing MM to
serveronly?All the instructions seem to be for making a
serveronlyMM from the start.Thanks.
-
RE: MM Crashed twice. Time to abandon MM?
I tried
dtoverlay=vc4-fkms-v3dThat doesn’t work for me, MM boots to a few lines about blocks, then nothing else.
(see https://forum.magicmirror.builders/topic/7554/applied-change-to-config-txt-mm-fails-to-boot/6)I used rpi config instead.
Ambient room temp is about 23/24C
“buck converter”?
Will try serveronly when I get a moment.
-
RE: MM Crashed twice. Time to abandon MM?
It’s currently running at 74.1C
-
MM Crashed twice. Time to abandon MM?
Getting steadily more disillusioned with the whole MM project. :(
Twice recently it’s crashed, at 01:09, and 21:44
When it boots back up again, the screen flashes blank a few times before it settles.Pi feels warm, temp shows 63.4C - despite making the changes to the Pi config.
I tend mostly to view MM on a browser away from the host Pi.
Would running MM in ‘server mode’ avoid the Electron browser temp problem?But if it keeps crashing like this, I think I might abandon the whole thing, and use the Pi for something else.
-
RE: Applied change to config.txt, MM fails to boot.
Done through raspi-config, seems ok, boots and runs fine.
sudo vcgencmd measure_tempshows 56.9C
-
RE: Applied change to config.txt, MM fails to boot.
Ok, when I get time, I’ll create a backup of the MM SD card first, and then try the GUI config tool.
Thanks.
-
RE: Applied change to config.txt, MM fails to boot.
No, because if that kills it, I don’t know how to bring it back - what file to edit etc…?