I just installed Vera Premium on an iPhone and an iPad and on both devices clicking one of the mode buttons instantly causes the app to crash.
A silly bug made it into the final version of 8.7 for this. I’m trying now to get 8.8 pushed through Apple quickly which should fix this…
8.8 installed and pressing “Mode” buttons does not seem to crash the app anymore but neither does it seem to do anything. The mode does not change in Vera.
Edit: the mode buttons now seem to be working and maybe were before if I had been willing to wait long enough. Seems I am having the same problem I have with activating scenes with geofence and could be other things if I did much else with Veramate and that is that it can take seconds to hours for Vera to respond to commands from Veramate and some time no response. Worse if I am on Cellular vs WiFi. I really like VeraMate except for this inconsistency. Not sure if this is a common problem or if it is a problem with Vera, VeraMate, IOS (8.1.3) or something I am doing wrong.
[quote=“sasaba, post:3, topic:186000”]8.8 installed and pressing “Mode” buttons does not seem to crash the app anymore but neither does it seem to do anything. The mode does not change in Vera.
Edit: the mode buttons now seem to be working and maybe were before if I had been willing to wait long enough. Seems I am having the same problem I have with activating scenes with geofence and could be other things if I did much else with Veramate and that is that it can take seconds to hours for Vera to respond to commands from Veramate and some time no response. Worse if I am on Cellular vs WiFi. I really like VeraMate except for this inconsistency. Not sure if this is a common problem or if it is a problem with Vera, VeraMate, IOS (8.1.3) or something I am doing wrong.[/quote]
This first preset mode implementation does have a feedback deficiency in the UI for these buttons, which would have confused this - I’ll be looking to fix this in a later version.
For the timing, I know some users have had the “blue refreshing” note appearing constantly meaning VeraMate can’t regain a session - I’m still trying to determine why some users get this. However, any straight commands (such as preset mode) sent to Vera only attempt it 10 times, otherwise will show an alert if it fails to connect. If it’s taking into the hours for the preset command to go through, I would tend to believe it is the Vera box - I myself know some of my commands (whether through VeraMate, or otherwise), maybe once a week or so seem to take that long. If this happens again, please send diagnostic via VeraMate and I’ll try and confirm if there was a problem in VeraMate though.
For the GeoFencing delay, then this is VeraMate - it’s not always possible to get an accurate location via iOS, so VeraMate uses multiple mechanisms to get maxium accuracy, and minimum battery usage. For instance, turning on your wifi can utiise extra location points. Either way, this is now configurable to let you play with how much battery VeraMate uses as it may depend on the cell tower coverage etc in your location - look under settings/GeoFences/Battery Usage.
Thanks for the reply. I did set up notifications when geofence activates a scene on both the Veramate side and the Vera side and have noted that I get a notification about the geofence being activated (as well as the scene being triggered) probably 80% of the time or more but only notified of the scene being run in Vera less then 50% of the time so you are probably right about the alot of the problem being on the Vera side. I am using UI 7 so I don’t know if other UI’s were better and I have also not used any other remote apps more then just briefly as I liked Veramates look and feel as well as its capabilities so much better. Will just hope that Vera UI 7 will become more responsive it has improved alot since it first came out.
I have the same issue, but it’s more like 90% of the time I get notified of the scene, and only two times has it ever actually fired, so less than 10%.
There have been a couple of niggly bugs affecting the UI6/7 connections (as a session token needs to be refreshed every 24 hours). I suppose this could cause the scene to not properly fire on Vera (although I haven’t seen that case in any diagnostics yet).
I’ve been focusing on trying to fix this issue, and 8.10 fixed one, 8.11 fixes another I found. It might be the case the GeoFence triggers aren’t properly detecting the session expiring if these are occurring 24 since you opened VeraMate? I’ll look into this, although I think it is handling it.