MMM-doomsDay - The countdown module,

broberg

@Mykle1 Okay, do a new git pull now. I have altered the method of rounding the numbers, which I should have done from the beginning if I knew better :P

Anyhow. Try the new version!

Mykle1

@broberg said in MMM-doomsDay - The countdown module,:

Anyhow. Try the new version!

I’ll get it right now. Thanks for dealing with this for me.

Did the git pull

I changed my test to the 7th as a 3 day test. I didn’t want to wait till the 15th to see if it was working correctly. It’s reporting 3 Days Left so that’s an improvement right away. I’ll check it in the morning. Thanks again

strawberry 3.141

@broberg date and time stuff can get really painful, that’s why I’m using moment for those tasks. there are some clever brains that thought about all kind of edge cases etc. you might want to check it out http://momentjs.com/docs/#/displaying/to/

broberg

@strawberry-3.141 Yeah I’ve noticed. If this module keeps misbehaving I will look in to the moment.js instead. looka a lot simpler, thanks for the link!

yawns

@strawberry-3.141
Absolutely right, moment.js makes life a lot easier when it comes to times and dates.

Snille

Hi there! I just posted a PR to you on github, adding the “passed” text via the config. And also let the “toWhat” event to still be shown when the event has passed (makes more sense i think if you use the “passed” text.) :)

broberg

@Snille There is already a text being displayed once the day has passed, not configurable, but, there is one :D

Snille

@broberg I know, that’s why I only made it configurable. :) Then ppl don’t have to change your code to set their own message. :)

Mykle1

@broberg said in MMM-doomsDay - The countdown module,:

If this module keeps misbehaving

Hey Bro, I just wanted to report that my last 3 day test worked correctly, without a hitch. When I looked at my mirror this morning, it said, “Did it work?” :thumbsup_tone1:

broberg

Finally got around to adding the option to change the text displayed when the doomsDay has passed as @Snille suggested!

Mykle1

@broberg said in MMM-doomsDay - The countdown module,:

Finally got around to adding the option to change the text displayed when the doomsDay has passed as @Snille suggested!

So I should do a git pull?

broberg

@Mykle1 Only if you feel like it!
But the latest is the coolest, don’t you think? ;)

Mykle1

@broberg said in MMM-doomsDay - The countdown module,:

Only if you feel like it!

Of course I feel like it.

But the latest is the coolest, don’t you think?

No doubt! I’m a huge fan of this module. :thumbsup:

Mykle1

@broberg
Actually, I won’t know for 26 days. I’ll let you know then!

broberg

@Mykle1 Hahaha, fair enough :thumbsup:

pjkoeleman

My MagicMirror is updating around 23:00 hour, and can’t find what I did wrong. Has nothing to do with the time zone (I think).

This is what I have in my config.js

{
  module: 'MMM-doomsday',
  position: 'top_center',
  config: {
    doomsDay: '2017-03-31 24:00:00',
    toWhat: 'End of month'
  }
},

I even made a test file in my browser, and then it’s is working as aspected.
Does any one now where the problem is.

broberg

@pjkoeleman nope, probably a timezone issue on the Pi itself, does the clock work correctly? daylight saving time?

Try changing the time from 24:00:00 to 23:59:00

pjkoeleman

@broberg The Pi itself is working correctly, the clock module is giving me the right time and date. And is updating around midnight.

I Will try 23:59 and see what come’s out off it.

pjkoeleman

With time set to 23:59 the module is changing at 0:44. The question is were is the offset off 45 minutes comming from ?

Mykle1

@pjkoeleman said in MMM-doomsDay - The countdown module,:

With time set to 23:59 the module is changing at 0:44. The question is were is the offset off 45 minutes comming from ?

I’m not trying to answer for broberg. It’s his module, but I use this module and I’ve had great success with it. It’s possible that the module is changing at 0:44 if you have the default updateInterval: 60 * 60 * 1000, . If you started the mirror at 44 minutes past any hour, then it wouldn’t update until the next 44 minute mark. If this is your case, then your module updated at 23:44 and not again until 0:44. The logical solution would be to set the updateInterval: to a smaller value or launch the module exactly on the hour, if that’s even possible. I don’t know if the module is set to always update at 24:00. If it’s not, then I would humbly request that it be added to the module.