Print

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

[Tuicemen]

I'm not sure if this is just related to my phone or the shear number of events the app is trying to pull up.
This has been happening since my first experience with the app in beta.
I believe when I tried the iOS version there was no issue but the history event numbers were small.

At least the app doesn't crash now it just restarts. however the idea of the history was for trouble shooting so I guess I have to rely on AHP for now.

[HA Dave]

I posted this elsewhere.... but my iPhone X10 app updated (just fine) this morning.

[Tuicemen]

 I'm sure the issue is only Android based , but is it just my phone?
Has anyone else using an Android had success with history pull not timing out?
If I clear the history then switch just a few devices(15) on and off they display in the history just fine.
However if I wait till the next morning with who knows how much activity the unit has seen, the history will time out and no history is displayed (app restarts)
I also find fetching the history to take extremely long  even with only 15 device activities in the history.
I don't remember it taking that long on the iPhone however I could be wrong!

I'd just like to know if it is only my phone. (Nexus S8+)
 

[Ronnie1234]

I’m using an iPhone and ani iPad both will not down the history. I have reset the Hub twice trying to get the Dawn Timmer to work. My iPad will not up date with the Hub. Got Dawn  using a minus delay to work but it thinks we are in daylight saving time. Dawn trigers 1 hour late. Can’t see that my phone is the problem.
The time zone and time of day are both correct on my phone.

[Tuicemen]

I received Email that this is definitely a bug that is currently being worked on by the developer so I've edited the OP to reflect that.

[Knightrider]

I'm having problems with this too.  Think it worked last week due to checking the WM100 with very few history events. Now that this thing has run for a week or two, I can't pull anything.

[Tuicemen]

I found 15 events was about the max history events I could get to report, any more would cause the app to restart.
At least this is being worked on by the developer more in depth now.

[ceedee]

More data...history not working on my Moto G5 Plus running 7.0.  For me, this is a key feature of the product, and I do hope a fix is in the works.

- does not work on IPad 2 running iOS 11.4.1
- does not work on Moto running Android 7.0
- does work on iPhone 5 running iOS 10.3.3

[Tuicemen]

The test update I have doesn't address this but that doesn't mean it wasn't fixed. we'll have to see what all besides the dusk dawn issues got addressed.

[bubbah]

Can we have version change logs please ??