Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rdb4762]

My system isn't recognizing the fact we fell back an hour this past weekend -- it still has dusk occurring an hour later than actual. I don't see anywhere to change anything. Do I need to do a full reset or something?

[Marauder2003]

I just came here to complain about the same thing.

[rdb4762]

Misery loves company!

[brobin]

The WM100 doesn't have a real time clock that's updated online. It gets it's time from the device you use to log in to the app; i.e., your phone or tablet. Once you're connected to the WM100 with the app the time should get updated.  This was pretty common for devices designed 15+ years ago like my Hunter-Douglas bridge to control blinds. 

[rdb4762]

The HUB HAS synced to my phone as far as time goes -- timers involving specific times work correctly. But those related to dusk (and, presumably, dawn, although I don't have any) are still on PDT!

[rdb4762]

A further thought: ActiveHome Pro had a "Dawn / Dusk Resolution" setting, updating dawn/dusk times in the CM-15A every few days -- the frequency being user-selected to save memory. I had mine set to "Every 8 Days," the most frequent option, which supposedly used 1.5 percent of memory. I wonder if the HUB might operate in some similar manner?

[rdb4762]

Contacted X-10.com folks directly, told them about the problem I (and others) was having. Their response:

Hi Richard,

Thank you for that. I will let our app developer know to correct this issue.

Regards,

Jacob Z.

[brobin]

Don't hold your breath.

[Tuicemen]

I don't usualy run timers of any sort from my WM100.
I decided to play with adding a couple this morning. I added a dusk dwn timer to one module making sure not to check the non DST region option then created a dusk dawn timer for another module checking the Non DST regionoption. Once done I went to setup and checked sync data. Once this was none I checked the dusk dawn timers on both modules. The dusk dawn timers set to use non DST displayed a time one hour sooner than those set to use DST. I'm in a region that uses DST so the option for using the non DST region should be what works however that is not the case.   Try editing your dusk timers to use a non DST region then rsync your WM100. And see if this fixes your issue.

[Tuicemen]

I fired off an email to the owner with my findings. In Hope's of maybe getting faster action on this issue. Apparently the issue is in the code as the fall back date was coded as Dec. not Nov.  The current solution from x10 is:

1. Select the gear icon on the device you have setup the Dawn/Dusk timer
2. On Edit Device page tap on the individual timer for either Dusk or Dawn
3. Select Non DST region in US or Canada and then select Save.

This will resolve the current time issue. After December 5th, 2023 please repeat step 1-3 to "uncheck" the DST region to return the hub to the correct status.

We apologize for the inconvenience.

Hopefully we'll see a update to the app fixing this soon however I'd follow brobiin's addvice as well.

[rdb4762]

COOL! Thanks, Tuicemen!