X10 Community Forum

X10 WIFI => X10 WIFI App problems or bugs => Topic started by: SkipWX10 on March 10, 2018, 08:48:40 PM

Title: WM100 did not update DST, needed sync to do so
Post by: SkipWX10 on March 10, 2018, 08:48:40 PM
Maybe I missed this topic previously, but shouldn't the WM100 update to correct time with switch to DST via wifi? Opened app this morning and got the time sync warning that module was one hour behind my phone. Does the WM100 only sync to the app? I don't keep the app running on my phone (or any for that matter).

I know there has been discussion of vacation time zone calling for sync, etc...but that's when phone/app have different time zones when app is opened. I thought it was updated to sync time with the wifi router (internet or cell provider) without the app running and then just alerted if phone was different.

To me, this is a bug. It should update to local wifi time without input.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Knightrider on March 10, 2018, 09:05:37 PM
Mine did as well.
Yes, currently the WM only syncs to the app. It's been placed on the wish list to sync with time.nist or similar.

And yes, my timers were off here. I currently have no app connected 24/7 due to AWS (Amazon Web Services) obsoleting my old tablet.

Let's hope a new firmware upgrade resolves this issue before we "Fall Back".
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 10, 2018, 09:13:14 PM
As Knightrider stated the WM100 currently only syncs time with the app.
This was by design so not a bug.
However several arguments have been brought to Authinx's attention for the need of syncing with the internet not the app.
I'm hopeful we'll see this addded into a firmware update soon.



Title: Re: WM100 did not update DST, needed sync to do so
Post by: SkipWX10 on March 10, 2018, 11:38:40 PM
Thanks. For the record, my CM15a was correct when I went to update it this morning, interesting.
Title: More DST woes!
Post by: Tuicemen on March 11, 2018, 09:39:43 PM
It use to be I only needed to worry about AHP and just the dusk dawn settings when this occurred.
However with Alexa, Google home and lesser so Cortana skills(many because there are less of these) there are many more ways this can get screwed up.
I don't have many timers working for the weekend and those that do if their off by an hour it is no big deal( I suspect that is true for most users).
Through the week is where more will notice this.
You'd think apps that run on a phone could get this right. However even cloud based systems can't get this right B:(

Case in point, I have two apps (both official apps for Broadlink) these have timers to turn on my TV and Cable box at a set time 6:45 am the mornings through the week days.
This morning the TV didn't come on I checked the timer in one app(IHC) and the timer had changed to 19:45 :o
I then thought I'll check eControll since when you set a timer in one the other app picks it up so I suspected the timer there to also be 19:45 it wasn't  ::) :' it was 07:45 :o

I realize not every where on planet earth do we experiance DST at the same time of year thus this can get tricky for programers.
But come on, regular timers shouldn't change, just the clock.
I've just started to look at other skills for timer issues created from DST but I don't have many outside the WM100 now.
Alexa timers seem to be still ok and I'd expect that being located in North America.
Google I don't use for timed events nor do I have any skills enabled for it other then SmartThings
Cortana I also don't use Timers and only have the SmartThings app installed for it.

Although there is no Skill as yet for the WM100, being is it has a clock that needs resyncing timers were off.
But they were all still set to the same time.
So if your timers come on late today from the WM100 the issue is not just with it, and it could be worse!
 ::) :'
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Knightrider on March 11, 2018, 09:49:37 PM
To make matters more complicated, there is a growing movement in the States to ditch the time change.
I've never liked DST, and would prefer to stick with Standard time, but now Florida and New England are poking at the idea of making DST the new permanent standard. Hawaii and Arizona don't change. Used to be parts of Indiana  that didn't change. I'm not sure about Eastern Canada, but didn't they have a half hour offset for Newfoundland at one point?

I don't like change.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 11, 2018, 10:24:35 PM
I don't like change.
Few do!
I as well would prefer just one standard, DST or Standard time and stick with it.
There is no reason to switch anymore. Many companies and stores are open 24 hours now.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 12, 2018, 01:01:48 AM
To make matters more complicated, there is a growing movement in the States to ditch the time change...........
I don't like change.

We should have never allowed that "train time" to take effect:
On Nov. 18, 1883, railways in the United States and Canada adopted Standard Railway Time, creating four standardized time zones in the U.S. and five in Canada.

Once you let the government tell you what time it is.... next they'll be controlling your retirement savings, and your healthcare. It's just a big power-grab.  rofl

In a small town near where I grew up.... they still maintained the Clock Park. A tiny park with good southern exposure and a sundial. It was the official local time. In it's day town leaders, business owners, preachers, school administrators, busybodies, ne'er-do-wells, and gossips..... would gather around the sundial near noontime to set their watches and exchange pleasantries, news, opinions and, lies.

Now with DST... no one even thinks about going back to Sun Time... the way God meant us to live.
Title: Re: More DST woes!
Post by: Walt2 on March 12, 2018, 02:55:53 AM

I realize not every where on planet earth do we experiance DST at the same time of year thus this can get tricky for programers.
But come on, regular timers shouldn't change, just the clock.


What needs to clearly change, are all the dusk/dawn calculations.   When one goes in and out of DST, there needs to be a 1 hour "instant" jump in these calculations.

Though, I guess, the WM100 could use only GMT internally, that never changes, and only the apps do a GMT to local time conversion????
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Brian H on March 12, 2018, 04:13:33 AM
After they moved the start and ending dates of DST.
My old Smarthome Manager Essentials. We ended up turning off DST and adding two lines in the location table. So we could pick DST or not. Has one different time zone in the DST one to fool the software.

I believe that the news here in Connecticut. Mentioned they where thinking about Standard Time all year.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: SkipWX10 on March 12, 2018, 11:17:18 AM
If the movement to end the switch really does happen, I hope they decide to stay in DST...I much prefer the longer daylight at the end of the day, it is much more productive for me and I'm comfortable getting up at dark thirty anyway...
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 12, 2018, 11:40:09 AM
I believe that the news here in Connecticut. Mentioned they where thinking about Standard Time all year.

With the new "location" dusk/dawn programing..... as far as our HA is concerned... I think we're already back to "sun" time. And as far as DST... that's an old idea who time never was. Whether or when the useless time change is ever abolished is a moot point... I can't see where my HA setup uses DTS. I use actual (calculated) sunrise, sunset. 

What needs to clearly change, are all the dusk/dawn calculations.   When one goes in and out of DST, there needs to be a 1 hour "instant" jump in these calculations.

I understand the desire to standardize. But it is so easy for computers to calculate dusk/dawn based on location. Why would I want to pay for light not needed... or walk blindly in the dark.... for the sake of standardized. 
Title: Re: WM100 did not update DST, needed sync to do so
Post by: VinRin57 on March 13, 2018, 10:57:25 AM
Ok, trying to follow along... the wm100 gets time of day from app? Hence, from the device- smartphone/tablet being used? Correct? Then where does it go to seek out dusk/dawn times?
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 13, 2018, 11:21:00 AM
....... where does it go to seek out dusk/dawn times? 

I am just guessing.... but I think we gave the app permission to use (know) our (it's) location... hence latitude, longitude. Which is why I said "sun time".
Title: Re: WM100 did not update DST, needed sync to do so
Post by: VinRin57 on March 13, 2018, 08:34:31 PM
I like 'sun time', which is what I need. So, app gets time and location from device, must be reaching out somewhere for dusk/dawn times? Just trying to understand what it gets from where... Thx!
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Ronr43 on March 13, 2018, 09:25:10 PM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 13, 2018, 09:30:01 PM
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.
 >!
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Ronr43 on March 13, 2018, 10:14:30 PM
Did not ask about using my phone's time.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 13, 2018, 11:30:09 PM
go to settings an try a sync
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Ronr43 on March 14, 2018, 08:16:16 PM
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.
 
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 14, 2018, 10:32:42 PM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 14, 2018, 11:46:45 PM
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.  B:(
Title: Re: WM100 did not update DST, needed sync to do so
Post by: BruceC on March 14, 2018, 11:59:04 PM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 15, 2018, 12:48:29 AM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: dhouston on March 15, 2018, 03:17:00 AM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: VinRin57 on March 15, 2018, 09:49:34 AM
Anyone know if there is any chance of a software or hardware update?
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 15, 2018, 07:39:57 PM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 22, 2018, 08:07:50 PM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Knightrider on March 26, 2018, 07:28:51 PM
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.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 26, 2018, 07:38:46 PM
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. ::) :'
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 26, 2018, 07:50:41 PM
The developer has identified some errors in the dusk dawn code of the app........

UPDATE:
I uninstalled/reinstalled  on one device. Currently running app on a phone and tablet ...

I also still have the DST problem.... with the WM100.... AND with another flavor/brand of WiFi device. Apparently... a slightly tricky event to write code for? I found a couple of work-rounds which will hold me till X10 gets this figured out. Although the dusk/dawn timer error is frustrating a user can always just "add the hour delay/advance" in settings... for now (not what I did).

This problem... has shown me how things can quickly get confusing when dealing with multiple  flavors/brands of Home Automation technology.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Knightrider on March 27, 2018, 01:58:14 AM
I also attempted some things on my willy at the cottage and it is still I hour late as well.

I'm an hour early. Last I checked, we were in the same time zone.

I say we just abolish DST.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 27, 2018, 03:07:32 AM
...I say we just abolish DST.

I am all for that! Daylight Saving Time a pain in the butt that accomplishes nothing. Have you set-up a voting thread for that?  rofl
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Ronr43 on March 27, 2018, 03:46:51 AM
I have used a CM15A for 20 years and have never had a problem with the DST change.  Something different in the code for the WiFi unit as opposed to the CM15A.

Hope to see a firmware upgrade soon but until I just do an On/Off time change on a weekly basis and that seems to be working for me. Have 6 switches that rely on Dusk/Dawn times.

Love the WiFi unit and will wait for the change.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: brobin on March 27, 2018, 12:10:06 PM
...I say we just abolish DST.

I am all for that! Daylight Saving Time a pain in the butt that accomplishes nothing. Have you set-up a voting thread for that?  rofl

The Florida legislature passed a bill this session to abolish STANDARD time and use DST year round.  -:) The governor signed the bill into law but before it goes into effect the US Congress must approve it as they have final say on timezones. In essence, Florida will "move" to the Atlantic time zone.  Interestingly, states can choose to exempt themselves from daylight saving time Arizona and Hawaii do but nothing in federal law allows them to exempt themselves from standard time. Several New England states are looking at doing the same.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: SkipWX10 on March 27, 2018, 07:34:18 PM
I will repeat that I am all for moving permanently to Daylight time as opposed to Standard time...much prefer to see light at the 'end' of the day. Interesting to see how this movement shakes out in Congress and the courts...
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 27, 2018, 09:32:58 PM
I will repeat that I am all for moving permanently to Daylight time as opposed to Standard time...much prefer to see light at the 'end' of the day. Interesting to see how this movement shakes out in Congress and the courts...

I say repeal the UTC (Coordinated Universal Time) and GMT time schemes. Forget this "One World Order" Universal Time (UT)... let our relevant position to the sun determine the time.  :'
Title: Re: WM100 did not update DST, needed sync to do so
Post by: JeffVolp on March 27, 2018, 09:33:14 PM
I have used a CM15A for 20 years and have never had a problem with the DST change.

Similarly with our Ocelot - rock solid for 15 years.  Setup was using our zip code to find the GPS coordinates, and then enter them.

Jeff
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on March 27, 2018, 09:39:09 PM
I have used a CM15A for 20 years and have never had a problem with the DST change.

Similarly with our Ocelot - rock solid for 15 years.  Setup was using our zip code to find the GPS coordinates, and then enter them.

I also run a CM15A (2). Are you guys CM15A's connected to running computers? When I removed my CM15A from a running PC... I assumed that the computers clock and AHP software is what kept the CM15A "on time". Does a stand alone CM15A keep accurate time? 
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 27, 2018, 09:40:49 PM
I have used a CM15A for 20 years and have never had a problem with the DST change.  Something different in the code for the WiFi unit as opposed to the CM15A.
Many did have issues so your one of the lucky ones.
Most of the newer DST issues with the CM15 was due to the date changes so dusk /dawn times were only off for the period between the old date change and the new date change.
I suspect this may be part of the issue the manufacture may be using the old dates that DST was to take affect.
If that is true we should see a correction shortly.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Knightrider on March 27, 2018, 10:07:08 PM
Update:

I just installed a new dusk/dawn timer. The app asked permission to use my location. Think this was my problem.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Tuicemen on March 27, 2018, 11:03:02 PM
Update:

I just installed a new dusk/dawn timer. The app asked permission to use my location. Think this was my problem.
I did the same and got the same question but it made no difference.
I've not noticed if the developer has been playing with my Willies yet. rofl
Latest word is the manufacture is looking at using a different data base. ::) :'
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Noam on March 28, 2018, 12:42:32 AM
I have used a CM15A for 20 years and have never had a problem with the DST change.
I think your math may be off just a bit - the CM15A was introduced in 2004. That's only 14 years ago. :-)
Title: Re: WM100 did not update DST, needed sync to do so
Post by: Ronr43 on April 01, 2018, 04:57:35 PM
At my age anything is possible.  I just know that I have used the same unit through 4 house moves and have had no issues with it.

Still love the WiFi unit so I don't have to connect to my computer every time I want to add a unit or change a schedule.
Title: Re: WM100 did not update DST, needed sync to do so
Post by: HA Dave on April 01, 2018, 09:13:41 PM
..... - the CM15A was introduced in 2004. That's only 14 years ago. :-)

I bought a CM11A soon into my entry into X10.... and was miserably disappointed with it. I almost just gave up on X10 and Home Automation altogether... out of frustration.

In 2006 (I believe) Bill posted of his BVC software... which enabled Voice controlled Home Automation using Windows XP SAPI5 voice recognition software. But I needed a CM15A to give it a try. After my experience with the CM11A (which I never got to work).... it wasn't easy for me to make that leap.

It was after buying the CM15A (in 2006) that i learned it was a phase issue that had hindered my setup. After adding a phase coupler, more AHP software, a 24/7 Home Automation PC, BVC.... and more my setup bosomed. It both seems like yesterday.... and a lifetime ago.