Significant progress has been made on the UI5 compatible version. Unfortunately this has put several planned enhancements on hold while I get this update out – they’ll be back in a future update.
Attached you will see an example of the changes with UI5 – thermostats with different button styling rendered. I am working hard to get this update out soon with a target of submission to able within 2 weeks from today.
On a side note, the next version with UI5 support will work with the same iOS release levels supported as the current version. Future versions will likely work only with IOS 5. This should not exclude anyone as the same devices that are currently supported can run IOS 5.
Not too keen on how the buttons go off the screen.
Is it possible to just have the most common operations on the screen then the rest in the “full” view?
[quote=“gilesjuk, post:2, topic:169993”]Not too keen on how the buttons go off the screen.
Is it possible to just have the most common operations on the screen then the rest in the “full” view?[/quote]
Agreed. Thermostats are the only devices that don’t work well on the iPhone at the moment. The control area does scroll so that the common controls are accessible directly in the table, but is not ideal. I’m working on it.
The main goal is to get basic UI5 support so those users aren’t left in the dark, then much more polishing and new interface paradigms are on deck.
No problem. I’m a softie myself (software developer), so I’m a bit picky 
Love the app on my iOS 5 but going to hold off updating my Vera until UI5 is stable and my DSC plugin works correctly.
I have one recommendation though. On the DSC alarm arming and disarming is it possible to have just a number pad? It’s a royal pain using the default keyboard. Also with the new updates will it still work with UI4?
Thanks.
Sent from my Sprint iPhone 4s using Tapatalk
[quote=“computerjohn, post:5, topic:169993”]Love the app on my iOS 5 but going to hold off updating my Vera until UI5 is stable and my DSC plugin works correctly.
I have one recommendation though. On the DSC alarm arming and disarming is it possible to have just a number pad? It’s a royal pain using the default keyboard. Also with the new updates will it still work with UI4?
Thanks.[/quote]
Thanks. . UI4 will definitely still be supported for the foreseeable future.
With regard to the pin codes, I made a request to the alarm plugin authors here for this very purpose: http://forum.micasaverde.com/index.php/topic,8906.0.html
You could add this to your plugin xml file if you wanted also. Since Automator.app doesn’t know an alarm from a thermostat it depends on the device definition (static data) to provide the render controls. If the input field used for pin codes has the “Style” attribute set to “numeric” automator will present a number keyboard instead of the default (in the current version as well).
I believe I have most of the functional issues resolved. A current suspected Vera bug is preventing the push plugin from being configurable. I may have to create a new UI in the app to take it’s place rather than wait for MCV to fix, and that will take a little time.
Those anxious for the new version can join the beta (make sure you register your device to be included).
Anyone have a plugin that will make an infant sleep?
Congratulations!
Thanks. She is 3 weeks old now.