The latest usable UI2 firmware seems to be:
http://download.controlmyhouse.net/betafirmware/ftp/wl500gP_Luup-1.0.994.trx
Many bugs against the UI2 firmware are still open (see http://bugs.micasaverde.com).
At http://forum.micasaverde.com/index.php?topic=3128.msg13390#msg13390 micasaverde states that “the Luup engine was finished”.
Is micasaverde’s statement equivalent to “no more bugfixes to firmware 1.0.x/UI2”?
Do NOT load 997, it will hose your Vera.
I did that by mistake once (a typo for 994) and it took me ages to recover it.
Changed the link becaused guessed is correct! Been there done that!
Yah, I made the same typo - entered 997 instead of 979 and had to reflash…
So, I wonder how many people are deciding to stay with 1.0.x/UI2 for now…
On the other hand, I think Vera2 users will be forced to take UI3.
I was also in the hosed in 997 club but that was my fault cos i was trying my luck to which was the latest version 
Yeah, I’ve downgraded after wasting time with UI3.
I’ve had my Vera since just before christmas - have been pretty happy with it, BUT I think the move to UI3 is a massive mistake. Ok so it’s a beta and you expect a few rough edges and a few things to be broken. What I didn’t expect was an amateurish attempt at interface design with no consistency, and apparently no though given to aesthetics, colour choices, icon size/design/functionality. Confusing terms - for example, no amount of explanation can persuade me that a scene should be described as an device, and to top it all sloooooow.
I’m normally just a lurker on this forum, looking for tips and advice, but UI3 has forced me to register and leave my opinion.
MCV, please Kill this off, it’s a false turn.
This is my second post on the subject, I was far too polite the first time, I didn’t want to hurt anyones feeling, after they’d worked hard on UI3, but you know sometimes honesty is the best policy, this really is probably the worst interface I’ve ever had the misfortune to use. These sorts of product are sold on personal recommendations and opinions on forums, people don’t just pick them of the shelf, and the sort of feedback you’re getting over UI3, in my opinion will hurt sales.
If Vera 2 is shipping with UI3, (which I hope it isn’t) then brace yourself for returned units and major support issues.
I really like the fact it uses flash now. But to a certain extent I agree. The interface has made Vera harder to use. I cannot get all my rooms to fit on the screen anymore, it seems hard to scroll around the “map”, and to do a simple task now takes more clicks.
That being said, U3 is definitely not something to be abandoned, but it does need some significant tweaks to increase the user friendliness.
I’m glad to see MCV continuing to work on Vera. Making the GUI into an open platform is a great idea.
I hate the user interface for findvera.com. While I still have to use it for setting up devices and scenes,I use a mobile interfaces on my computer to operate my scenes. I use the smart phone interface for simple operations and the other plane Jane mobile interface for voice commands with Dragon NaturallySpeaking. No more double scrolls unless I’m writing scenes or doing some other type of maintenance.
Can’t you use the local Web interface instead of accessing it through findvera.com?
Like the others, I upgraded. played around, got frustrated, downgraded. I’m an Apple user, and would love to eventually use an iPad for some of the home control, but since “flash” isn’t supported, the new UI is out and I’d have to rely on a third party app for control.
As far as the set-up, I think the room metaphor is a nice idea, but personally I’ve moved away from it. All my scenes are now global, as most control lights in multiple rooms. In fact, all of my scenes control multiple rooms, otherwise I’d just use the switch on the wall.
There are lots of things wrong with the current UI from a usability standpoint, and from what I could see in the new UI, they only get worse. Please stop working on the new UI MCV, and tweak the current UI to make it more usable.
Your UI needs to do two basic things: 1) set-up/maintenance, and 2) daily operations. these will never be done at the same time, so don’t try and force them. Set-up occurs infrequently (adding a new device/scene), but operations happen all the time.
For operations, the dashboard is all we need, but you have way too much whitespace/dead space in the layout.
For set-up, you need to expose more without making me expand things. I’d love a simple spreadsheet view with each device being a row and all the attributes being columns. I could hide/show the columns as needed, but I can manipulate multiple devices and attributes at once without all the jumping around on the screen.
From various recent posts from MCV - it appears like the luup engine and the UI are 2 different things. Square connect apparently has gotten them to continue to develop UI2 to work with their plugin. Also apparently the “vera2” hardware apparently now also has a UI 2 version for people that prefer it.
So if I’m following correctly - BIG IF- then they will continue to be supporting UI2 with new luup engine updates that add features and devices. Is that the way everyone else is reading this?
I would like to read it that way… I.e. get new bugfixes and features into Luup engine, but keep UI2, if possible. Until UI3 is rock-solid
So I had the same concern, because I’m completely happy with my current UI and running version .979. I therefore posted a support case yesterday, and got a response last night as follows…
Hi Sig,
Thank you for supporting our efforts. Yes, we will continue to support UI2 as well. In fact, we done a new firmware for UI2 and test it and we will probably release it this weekend or Monday. UI2 won’t die with the new UI and we realized that customers need this version of software as well.
Looks like new UI2-based firmware is out - 1.0.985!
Square connect apparently has gotten them to continue to develop UI2 to work with their plugin.
The only thing SC needed that wasn’t in .979 was that the Luup API reports the serial number of the box so they can target multiple boxes. It was 1 line of code. We added it to the engine in January, so subsequent builds (ie UI3 builds) had it, but UI2 didn’t. As you pointed out, the engine is the same. So today we released a UI2 build with this update to the engine.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules