Thanks, Chuck! I'll wait for the latest and greatest version from you.
I've been tinkering with openHAB. It's written in Java and runs on Windows/MacOS/Linux. It shares Premise's concept of binding virtual objects to real devices. However, its vitual objects are less complex. It's like if in Premise you were to bind properties individually (temperature, arming status, etc) and not whole objects (Thermostat, SecuritySystem, etc) It's both an advantage (granularity, flexibility) and disadvantage (a
mountain of setup work).
Whereas Premise's UI is auto-generated from Home objects, you manually declare what will appear in openHAB's UI. However, you can define a bunch of different UI's (one for you, one for the kids, another for guests, etc) and invoke the one you want in the URL. openHAB has a pure browser interface (looks like an iPhone; for webkit-based browsers only) as well as clients for iPhone and Android.
Big roadblock for me is the lack of UPB support and an ELK M1 driver (a DSC driver is available ... as a starting point to write a new ELK M1 driver). Nor does it have a driver for an X10 CM11A (I still use X10 for a few things) but there are some workarounds. Someone is working on a UPB driver but it is still in beta (maybe alpha). There's a steep learning curve for developing a new driver (Java, the Eclipse IDE, openHAB's driver architecture, GitHub, etc).
Compared to Premise, some things in openHAB are incredibly easy (acquiring and consuming XML or JSON data is oh so much easier than in Premise) and others are jaw-droppingly hard (No scenes. No calendar-like scheduler. A driver can't update the list of devices discovered, etc).
Rules are written in a Java-like language but, with a few tweaks, it also supports Python (specifically, Jython). FWIW, it's based on open standards (Eclipse SmartHome, Maven, Karaf, etc) and has a very active community.
https://community.openhab.org/
Perhaps of some interest to you might be
Project Rotini. This is one person's attempt to create a completely new Android interface. I like its aethetics and the ease of defining UI's.
https://github.com/igorgladkov/rotini/wiki
For example, here is how you'd display an on/off fan control using a
Switch widget:
Frame label="Bedroom Fan {widget:switch,icon:fan}" {
Switch item=Fan_Bedroom
}
Cocoontech seems to dislike displaying PNG files so you'll have to click to see it:
https://github.com/igorgladkov/rotini/wiki/images/widget-switch.png
"Fan_Bedroom" is defined in a separate openHAB file (it defines the binding between "Fan_Bedroom" and the physical device). Far easier than anything in AutomationBrowser or MiniBrowser!
Another example using the
Gauge widget:
Frame label="Humidity {widget:gauge}" {
Text item=Sensor_Bathroom_Humidity label="{unit:%,icon:water}"
}
https://github.com/igorgladkov/rotini/wiki/images/widget-gauge-1.png
There's a long thread on the openHAB forum for Project Rotini.
https://community.openhab.org/t/different-take-on-client-ui-android-for-now/3561
Here are a few screenshots of a sample "Rotini" UI. Crisp, clean, informative, easy to understand and navigate.