@lealittlefiele90 - Hmmm, I'm not sure why it would do that either. I believe the program running on the table obtains current time from your phone, when you first connect to it. Are you using your phone to connect, or just the web browser interface?
Bruce is correct, the table pulls time when connecting with the mobile app. The current implementation of night mode is less than ideal and will be improved as we continue develeopment. Here’s a list of caveats to keep in mind:
When we improve this functionality it will:
We’re working on many updates to the app so I don’t have a date of when this will improve, but it is on our list and we’re doing everything possible to expedite develeopment.
Please let me know if this is helpful or it’s still not operating correctly.
Thanks for this bug report - I will relay it to our devs...
Update: The bug has been fixed and will be pushed to the Google Play and Apple App stores in the next day or two.
We'll need more info to track this down. Please contact support here, which is best place to do this.
@Bruce - I am having similar issues where regardless of the schedule I provide, the table does not follow it. I've rebooted the table, rebooted my phone, turned Night Mode off, Saved, Turned back on, Saved and no go.
Likewise, I've noticed when I turn the feature back on, it is defaulting to an On time of 10am and an Off time of 8am... I started noticing the issue right around the Daylight Savings time change, whether it is connected or not.
Sometimes, it almost looks as if the app is throwing an error when going to the Night Mode screen, but it is quickly covered by the normal app page.
I submitted a request, 7325, through Support. Likewise, I provided some screenshots from the app showing the strange default time settings.