WM100 did not update DST, needed sync to do so

[Ronr43]

Is there a way to get the WM100 to respond to the correct Dusk/Dawn time.  Ever since the change to DST mine is off one hour on each.  Worked perfectly when on Standard time.

[Tuicemen]

Mine worked well prior as well and were off afterwards by one hour as well.
open the app and sync the times then go to the devices which have the dusk/dawn timers and click on the dusk or dawn timer setting Icon.
The app should ask to use your phones location or something like that, allow it then click save.
I think you'll only need to do that for one dusk or dawn setting and the app should update all.
I only have one light using dusk settings so I can't confirm that part.

[Ronr43]

Did not ask about using my phone's time.

[Tuicemen]

go to settings an try a sync

[Ronr43]

Tried everything suggested, even reset the WM100 and reinstalled.  Still the DST time is off by one hour.  Appears that it is getting the Sunset/Sunrise time from a table for only standard time.

Will hopefully wait for the firmware update to fix the issue and will set a specific time for the units to change.  Would also help if there was a +/- 60 minute variable.

Thanks for the help.

[HA Dave]

Tried everything suggested, even reset the WM100 and reinstalled.  Still the DST time is off by one hour.

Mine has yet to sync correctly either. A little frustrating. I may try syncing with the wife's phone.... just to have something different to try. Hopefully... an update will be quick in coming.

[Tuicemen]

Just syncing the time will not fix the Dusk Dawn timers
I had to click on a dusk timer adjust the off set then save. This fixed my dusk timer, I then went back and removed the offset as I had done a pre dusk 30 mins. 

[BruceC]

My experience has been that the Dawn/Dusk function was taking effect about an hour late in my area before DST came into effect (north-east). Now that we set the clocks back, the Dawn/Dusk timers are correct. This is an odd problem.

[Tuicemen]

I'm not sure why results are all over the place for dusk dawn after the DST change.
However during testing of other options I did get different results depending on the phones age even if they were from the same manufacturer
I can understand Androids performing different then a IPhone but since not every one is using the same OS versions it gets tricky to debug.

[dhouston]

I'm not sure why results are all over the place for dusk dawn after the DST change.
However during testing of other options I did get different results depending on the phones age even if they were from the same manufacturer

That's one of the problems with Google's open sores version of Android. While it let manufacturers customize it for their devices, there was no way to force upgrades (even for security issues). One can see how they might prefer to sell you a newer phone/tablet rather than give you a free update of Android.

[VinRin57]

Anyone know if there is any chance of a software or hardware update?

[Tuicemen]

Anyone know if there is any chance of a software or hardware update?

There is a good chance of an update!
However how soon that will be we can only guess.
The developer has a list of issues to look at and fix so I suspect we won't see much in line of adds with the next update.

[Tuicemen]

The developer has identified some errors in the dusk dawn code of the app.
They say to uninstall the app then reinstall and select connect to existing hub this should download all your settings and resync to your phone.
I'm not sure how this will work for those with multiple phones connecting. I suspect all phones will require a app uninstall and reinstall.
Since the guys at Authinx aren't experiancing the dusk dawn isue they can't test this.

[Knightrider]

UPDATE:
I uninstalled/reinstalled  on one device. Currently running app on a phone and tablet (android, Samsung )

Did not correct the problem. Dusk is 1 hour early. Will try a dual uninstalled next.

[Tuicemen]

I also attempted some things on my willy at the cottage and it is still I hour late as well.
I also forwarded some info to the developer so they can connect to my willies as they seem to be stumped as to why this is happening.
Maybe with the ability to connect to a willy that has the issues they'll get it figured out!
I believe the data base they're using for dusk/dawn is corrupt. If or their calculations are messed up then everyone would experiance the issue.