X10 Community Forum
📱X10 WIFI => 🐞X10 WIFI App problems or bugs => Topic started by: ekraus on July 27, 2018, 06:21:36 AM
-
Well I got a new WM100 from Authix after sending my original one in. They couldn't recreate my problem.
But
It seems to be working.
Fixed timers work.
Dusk/Dawn still don't work.
They also said they were waiting for Apple to release the Dusk/Dawn fix.
Problem is I have an Android phone.
-
The dusk dawn fix is tied to a firmware update which when released is auto pulled by both OSes this could lead to extra issues with the old iOS app trying to talk to the WM100.
-
Here is the problem I have with Dusk/Dawn.
All Dusk/Dawn timers are set at +30.
here is what i get.
Actual--------------Timer +30
Miami
6:45AM 6:15AM OFF
8:09Pm 7:39PM ON
It's 30 minutes off.
Need +1 hour.
-
I asked for a 90 min offset be added while the developer worked on the dusk/dawn issue and was told this wouldn't be a problem.
However until we actually see the update with the new dusk/dawn code we have no way to tell what if anything was added. B:(
A 30 min offset is not enough for most users.
-
I asked for a 90 min offset be added while the developer worked on the dusk/dawn issue and was told this wouldn't be a problem.
90 Minutes would be great in 5 minute increments.
-
FYI: In the latest SW/FW, my on/off times are am/pm, and the dusk/dawn times are in military format.
Also, release notes indicate D/D timers are now +-90. Not seeing that in Android app.
-
Which app version are you using?
I just uploaded the newest Android but I don't have the 90 min offset maybe me running the test app messed things up. B:(
I suspect this update to be a real mess It sounds like Authinx had to get another developer on board to get things moving.
-
2.0.08
-
2.0.08
:o ???
I mean are you using Android and or IOS.
-
Android 7.0.
I also have latest version of the app installed on iPad Air 2 with iOS 11.4. As per your earlier note, sync still does not work on iOS either, the D/D setting info does NOT list on/off time, and the advance/delay is +-90, in 15 minute increments. A rather large disconnect from the android app.
To see history records, I use an iPhone 5 running iOS 10.
-
My contact at Authinx states they can see the 90 min offset but I believe they use IOS. Sadly many things in this release were not tested by Authinx or myself. Things were added to the IOS version that may not have been added to the Android version and the other way arround B:(
-
Agreed. Also, just noticed that the increments are 5 minutes up to 30, then 45, 60, 90 (ie. 15 min increments).
Nothing of the sort on android.
-
B:(
-
just noticed that the increments are 5 minutes up to 30, then 45, 60, 90 (ice. 15 min increments).
Yes apparently the developer was not given a path to follow for the offset after 30 mins and that is the way it was designed. >*<
Changing offsets half way through, What developer does that? B:(
-
A junior developer?
-
I think they need to go back to school! ::) :'
Authinx is trying to get the Android app offsets added for a quick update but given the time of day over there I don't expect the message to get passed on to quickly. Hopefully us Android users will see a fix faster then this last update. ::) :'
-
And pick a standard time display format across settings!
-
And pick a standard time display format across settings!
I'm told the IOS app is the same so if the Android version is brought inline with the IOS that should be fixed. ::) :' However since the developer is on the other side of the world it appears their thinking is upside down. B:(
-
If you mean time formats, the latest ios app does not have a timestamp for D/D settings. So, not consistent with Android app. I will grab a screenshot when I get a second.
-
I am showing some strange behavior with the dusk timers. I have an inside light set to come on 10 minutes prior to dusk, and an outside light come on at dusk. Here are the past few days, with inside light time first:
7:28
7:01
7:27
7:37
7:05
7:15
7:23
7:33
7:19
7:29
7:06
7:20
7:18
7:28
6:22
7:26
6:59
7:14
6:36
7:23
6:13
7:21
They did seem to be functioning OK when the app update came out (I did not program them in until the dusk / dawn bug was fixed). But clearly they are getting strange. I do have security set for the off times, but it appears maybe the on time is getting corrupted? Can anyone else confirm they have this happening?
-
I'm told a new app version will be out by weeks end addressing some of the dusk dawn issues.
once it comes out hopefully there will be no more issues with the timers, ::) :'
-
My dusk/dawn +/- timers are having problems. Plain dusk/dawn is working okay, it is the +/- that does not work. This evening I just happened to notice the blue light on the wm100 flash when it should have been turning on a light which didn't happen. I picked up my phone and turned the light on with the app so it appears to be a timer issue. Also, I need to mention I was using +/- 90 minutes. Hopefully the software update will fix these issues.
-
Hey Tuscon, did you have your WiFi Hub in March? Did the Dawn/Dusk times move an hour when DST started? I'm wondering what will happen when DST ends.
-
Did others get the firmware push last night? What is it supposed to fix? I can’t find information on it. Does it fix the Dawn/Dusk issues?
-
I'm still at firmware 0.0.24 and checking states it is up to date on my Andoid phone
-
I just got the new app and firmware 0.0.26 maybe IOS was out sooner.
-
1713 eastern daylight time. Updated was good on my android.
-
Hey Tuscon, did you have your WiFi Hub in March? Did the Dawn/Dusk times move an hour when DST started? I'm wondering what will happen when DST ends.
Yup I did and it work.
-
Hey Tuscon, did you have your WiFi Hub in March? Did the Dawn/Dusk times move an hour when DST started? I'm wondering what will happen when DST ends.
Yup I did and it work.
Thank you, and version 26 had "Dusk" right at Sunset yesterday which was 6:30 PM in the Phoenix, AZ area. My Aquarium Light which is Dusk -75 ended up turning on at 5:15 PM, so I had to adjust all of my lights.
-
I am running firmware 0.26 and iOS app. V 1.2. I don’t see the times that it calculates for dusk and offfset thereof like posted above, so I assume that was on an Android. When I just use Dusk, it uses EST not DST, sunset was at 7:18 today and the WM100 turned on my lights at 6:18. Say what? Yes, I synced the time with my iPhone. The offset did work for -20 on another device. Is this what others are seeing?
-
Yes. Same here. it’s busted.
-
I just bought this thinking it would be a better replacement for my 15 year old PowerLinc 1132. Little did I know it is running pre-release software - 0.0.26 means the first real release has not happened yet - right? I set my porch light to come on at Dusk +30 minutes. Dusk today is 5:31, so it should have come on at 6:01. The light came on at 4:30. You cannot examine any of the information stored in the hub to find out if this giant error is in the stored time zone, daylight savings time, longitude-latitude or if all the info is right and it's just bad processing of the info.
What if I am in a location away from home, different time zone, or may be even the same time zone but dramatically different longitude- latitude. There is absolutely no way to set a dawn or dusk timer if you are not located with your hub. This software is not well thought out at all!
-
The device triggers on sunrise and sunset, not dawn and dusk. Could that be the issue?
As for software, don’t count on much happening on that front. It’s very buggy, and major features are either missing or broken. We haven’t seen an update in over two months. If you are unhappy, return it...it probably won’t get much better.