I created the event in Grand Rapids mi. I know the event said 7pm but the reminder said 8. There appears to be a bug with dst. I know my settings are correct unless something is hidden.
Can you post the UnitID from the URL when you click on the unit?
@JoelYoung Is the device you created it from set to set the TZ of the device automatically? Is the device set to Eastern Time (New York).
I’d think Grand Rapids is far enough from the Central Timezone that your device wouldn’t be confused by that. I’m in Ohio, and it’s working properly for me. So, the root cause isn’t clear. Ed has passed your info onto the developers, also, to see if there’s anything specific on the backend.
I worked with jacobfetzer a couple of months ago to try to fix this for our pack, but it is still doing it. Seeing the amount of different posts about the time problem, there has to be something wrong in the coding causing this, and not the time zone selection option on the unit admin level screen. Hopefully this can be put up higher on the list for the developers as the software is sending out the wrong times to units nationwide.
Thank you for confirming. I think some jump to the conclusion that the problem is between the seat cushion and the keyboard when many users are very competent in troubleshooting and trying to exhaust options that might be self inflicted. I posted after reviewing my configuration and see other posts that asked for the unit number so that the developers could look into it.
I too believe there is a bug or a very deeply hidden user option to recognize DST.
@DanCurley Thanks for reporting this. You’re the first one I’ve heard of that that didn’t work for. Did it work initially and then revert at some point? Is the edit pack/troop page showing the right TZ (even without any interaction on your part). Could you provide your Scoutbook UnitId number again?
@JoelYoung It’s not so much that we assume the problem is user error, but we do have to eliminate that possibility. There are also other variables in play that could be causing the issue. The more we know, the more likely the developers can find the issue and fix it quickly.
Related/Similar issue, but not exactly the same: I’m an experienced Scoutbook user. I must have created 100 events for our Troop in Scoutbook thus far…almost all containing an auto-reminder message. I’m looking at one scheduled for tonight at 8PM (it’s now 9PM) and the auto reminder (scheduled to be sent 2 hours ahead of the meeting) has not been sent. Even Scoutbook “admits” that the reminder has yet to be sent…I see it still “in queue” in the calendar. I created this meeting a day ahead of time, so certainly the auto reminder should have triggered at 6PM today. Thoughts?
@jacobfetzer It was still giving reminders an hour off after we thought it was corrected in the week or so after. I just did another test event and the reminder did send out the correct times, but oddly enough, it said the time zone was “Central Time” after the digits - sent to an iPhone, Gmail and work email account. We are in Eastern time zone and that is confirmed in the Edit Pack page. I guess as long as the times are right now, I’m not too worried about the TZ listed per se.
Thanks for you help!
@DanCurley For the event that has the wrong TZ in the email, could you check the URL of that event for an eventID? Thanks.
Our situation is similar but opposite. Events that were entered in the calendar, since DST in October show times one hour earlier (we are in Eastern UTC-5:00 Indiana East). Our troop meetings are at 7:00 but show in the calendar as 6:00, but email reminders and calendar subscription correctly show the time as 7:00.
@RobertMeacham, I’m guessing you have already edited your time zone to the East (Indiana) variant? It’s under Troop -> Edit Troop
Yes, this has been set correctly for a while now. I tried changing it to CDT (UTC-6:00) and then changed it back to EDT (UTC-5:00) see if that fixed it, but no change.
@RobertMeacham Do your reminder emails have the correct time and timezone?
@jacobfetzer This was one of them that sent out a reminder for 7:30 instead of 6:30 PM in November:
Yes, the reminders and the calendar subscription feed have the correct time.
Here’s a test event I created today. It shows the correct time in Scoutbook, but an hour later in calendar subscription. (Haven’t checked email reminders, but I suspect it will be an hour later as well based on the calendar subscription.)
It seems that the time for all past events have been set back one hour in Scoutbook Calendar as well.
OK, now this is strange: I thought the email notification would be wrong, but it came through with the correct time (7:00-8:30) in the text, but the later time in the ical link.
Certainly I think users expect that Scoutbook WON’T be adjusting times from the times they entered based on DST. If the troop meets at 7:00 and the event is created before (or after) the DST change, the meeting will STILL be at 7:00. We all set our clocks to adjust. This is just making a mess of event scheduling!
@RobertMeacham Aren’t you in Eastern Time though? Your event reminder said central. So, that’s (part of) the bug.
Well that’s interesting. The Edit Troop screen is set for Indiana (East) which is Eastern Time. That’s what it was set for when I created the new event. I hadn’t noticed the Central Time in the email.
We are having the same issue. Our pack is in Fishers, IN near Indianapolis and we are on Eastern time. The Pack profile has (UTC-05:00) Eastern Time (US & Canada) and our first reminder comes out with the correct time but for some reasons it shows CST:
When: Dec 6, 2020, 7pm - 8pm (UTC-06:00) Central Time
Subsequent reminders will adjust the time automatically and update the timezone designation causing half of our pack to show up an hour late:
When: Dec 6, 2020 8pm-9pm (UTC-05:00) Eastern Time (US & Canada)
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.