AP15e -
It is a damn shame that you feel you need to move on to get the functionality you need. Unfortunately, it is also understandable.
I have only been involved with the Vera for a bit over 5 months, so I can only speak with my short amount of experience. Before I purchased my Vera 3, I did some research. During the research I found that there were 5 different UIs that had existed on the Vera. As a developer, this said to me that the underlying engine must be rock solid, otherwise developer time would be focused on that over making a new UI. Over the months, I have found that my assessment is incorrect.
When you look at successful products out there, the UI doesn’t change much. If you look closely at Windows and Mac OS X you will see that the underlying UI has been the same for a long time. Things get added on and tweaked to make the UI better, but at a fundamental level, windows are drawn on the screen the same way and UI elements are just made to look a little different as version progress.
For HA systems, it seems that the UI is only marginally important. It can be the most beautiful UI in the world, but if the underlying system doesn’t work how users expect, the UI is worthless.
In my opinion, there are four places that could be improved that would make the entire experience better.
-
Basic logic in scenes. (if/then/and/or/not) I realize that LUA is supposed to be the answer for this, but most people see code and run away.
-
Developer documentation. I agree with those that say that having a full LUA tutorial isn’t something that MCV should take on. There are plenty of sites out on the net that have good LUA documentation. Instead, if someone went through each of the XML files that ship on the Vera and asked themselves, “Is there documentation on how to do this?” An example would be the “Get” actions that are in almost every device’s XML, nobody seems to know how to do this in LUA. Good documentation of the XML and JSON files would also be great. Along with a fairly simple example, and a fairly complex one.
-
Full support for features. The most obvious one (for me) is Insteon, though there are plenty of others. The documentation claims that Insteon is supported, but the implementation seems half-assed at best. And when people post on the forum that “MCV is focused primarily on Z-wave” it is only rubbing salt in the wounds. If MCV wants to focus on Z-wave, that is fine. Take all Insteon support out and don’t claim that it is supported. (When you tell a customer that something is ‘supported’ they expect that it will perform comparably to other devices that claim to support the technology.)
-
Debug-ability. Getting an error in the logs that says something is wrong with your LUA code on line 856 is useless if you can’t figure out what line 856 is. I have spent an insane amount of time adding logging to my code to try to narrow down where an error is. It is worse when you are trying to help someone through a problem and they give you a similar log line.
I’m not trying to be a negative Nancy here, I have enjoyed playing with my Vera 3 and hacking stuff up on it. And I plan to continue to do so. But, as my friends like to remind me, I am not normal. I also understand the realities of product management and development, as I work for a small company myself. But I also know how important it is to have prompt bug fixes to keep your customers happy.
Again, it is a damn shame to lose someone like AP15e. Whoever is behind that alias has provided an insane amount of help for people on this forum. We will miss you. ← Never thought I would get to use that one!